Contents
Who this article is for: it applies to clubs that manage their handicaps with Handicap Master.
What is this integration?
The Handicap Master integration makes the club's member and competition data available to that system, so Handicap Master can sync it automatically and you don't have to enter it by hand.
Handicap Master reads the data from Golfmanager periodically: the member list, the competitions flagged for export, and the players entered in each one.
Handicap Master is handicap and competition management software. This integration provides it with the club's data; the handicaps and results are managed by Handicap Master in its own system. Golfmanager doesn't store handicaps: it only exposes member and competition data for Handicap Master to read.
What problem does it solve?
It avoids typing members and competitions twice (in Golfmanager and in Handicap Master).
It keeps the member list up to date in Handicap Master.
It shares each competition's entrants with no manual work.
It's simple: the club only enables the integration and flags the competitions.
Which systems does it connect, and which way does the data flow?
It connects Golfmanager with Handicap Master, in one direction only:
It's Handicap Master that reads Golfmanager's data when it needs it.
Golfmanager exposes that data securely (with an API key).
It's not a two-way sync: Golfmanager shares members and competitions; the handicaps and results live in Handicap Master and aren't imported back.
What information is shared?
Information | What it includes |
Members | Reference, first and last name, gender, date of birth, membership card number, address (street, city, country, postcode), email and status (active, inactive or deleted) |
Competitions | Identifier, name, date, start and end time and number of players per round |
Players in each competition | Tee time, position in the group, name and membership number |
All of this data travels from Golfmanager to Handicap Master.
Prerequisites (before turning the integration on)
Have a Handicap Master account.
Have the Handicap Master module installed in your Golfmanager.
An API key so Handicap Master can authenticate when reading the data.
System administrator permissions to configure.
How to set it up (step by step)
Step 1 — Enable the integration
Go to Settings > Handicap Master.
Turn on the "Enable integration" option.
Save your changes. If it's not enabled, Handicap Master won't be able to read the data.
Step 2 — Create the API key
Go to the API Keys section and create a new key.
Give the key to Handicap Master so it can connect. It's the "password" with which its system accesses the data.
Step 3 — Flag the competitions
On each competition (booking type) you want to export, open the Handicap Master section.
Turn on "Upload to Handicap Master".
Enter the start time and the end time of the event and the number of players per round.
Save your changes.
⚠️ Only competitions with "Upload to Handicap Master" enabled are exported. If a competition doesn't appear in Handicap Master, check this box first.
Each configuration field explained
Below, each field is explained: what it is, how it affects the system, how it behaves, and an example of use. They're grouped into the integration setting, the competition fields, and the member fields that decide whether they're exported.
Integration setting (Settings > Handicap Master)
Enable integration
Field name: Enable integration. It's a toggle (on/off, off by default).
Description: it allows Handicap Master to read the club's data.
System impact: without it on, Handicap Master's requests are rejected.
System behavior: if it's off, on querying the notice "Handicap Master integration is not enabled" appears.
Example of use / what happens: you turn it on when you're going to start using Handicap Master; you turn it off if you want to cut off access.
Competition fields (on the booking type, Handicap Master section)
Upload to Handicap Master
Field name: Upload to Handicap Master. It's a toggle.
Description: it flags the competition to be included in the export.
System impact: only competitions with this option on are shared with Handicap Master.
System behavior: if it's off, that competition doesn't appear in Handicap Master.
Example of use / what happens: you turn it on for the tournaments Handicap Master manages and leave it off for the rest.
Event start time
Field name: HM event start time.
Description: the time the competition starts.
System impact: it's sent to Handicap Master as the event start time.
System behavior: it's part of the competition data Handicap Master reads.
Example of use / what happens: you set, for example, 09:00.
Event end time
Field name: HM event end time.
Description: the time the competition ends.
System impact: it's sent to Handicap Master as the event end time.
System behavior: it's part of the competition data.
Example of use / what happens: you set, for example, 14:00.
Players per round
Field name: HM players per round.
Description: the number of players per round of the competition.
System impact: it's sent to Handicap Master as the number of players.
System behavior: it's part of the competition data.
Example of use / what happens: you set, for example, 4 (groups of four).
Member fields that decide whether they're exported (customer record)
These fields aren't exclusive to Handicap Master, but they determine whether a member is included in the shared list.
Gender
Field name: Gender (on the customer record).
Description: the member's gender (M/F).
System impact: it's required for the member to be exported; it's also sent in their data.
System behavior: if it's not set, the member isn't included in the export.
Example of use / what happens: you fill it in for each member that should appear in Handicap Master.
Email notifications
Field name: Email notifications (on the customer record).
Description: it indicates whether the member accepts receiving communications by email.
System impact: it must be on for the member to be exported (a privacy control).
System behavior: if it's off, the member isn't included.
Example of use / what happens: you make sure the members that should be exported have it on.
Membership number
Field name: Membership number (on the customer record).
Description: the number that identifies the member.
System impact: it's the value Handicap Master uses to match each player (it's sent as the card/player number).
System behavior: if a member has no number, they're still exported, but their card number will come out empty.
Example of use / what happens: make sure each member has their number so Handicap Master recognizes them.
Subscription/fee tag
Field name: Tag linked to a subscription/fee.
Description: the tag that marks the customer as a member with a current fee.
System impact: it's required (and must be current) for the member to be exported; it determines their status.
System behavior: the status is sent as active (current assignment), inactive (expired tag) or deleted (customer or tag removed).
Example of use / what happens: when a member renews their fee, their tag stays current and they're exported as active.
How it works day to day
Once configured, there's nothing to do: Handicap Master connects and reads the data on its own, periodically.
The club only has to keep the members up to date and flag the competitions it wants to export.
Administrators can preview the shared data (members, competitions and players) to check everything is correct.
How often the data is refreshed is decided by Handicap Master, which is the one reading. Golfmanager only exposes the data when asked for it.
Which members are exported
For a customer to be included in the member list Handicap Master reads, they must meet all of this:
Have gender set on their record.
Have email notifications enabled.
Have an active tag linked to a subscription/fee, with its assignment current (already started and not expired).
Not be deleted (neither the customer nor the tag).
The status sent is active (current assignment), inactive (expired tag) or deleted (customer or tag removed).
Limitations to keep in mind
It's export only (one direction): Golfmanager shares the data; the handicaps and results are managed in Handicap Master and aren't imported back.
Golfmanager doesn't store handicaps: it only exposes member and competition data.
Only the members that meet the criteria above are exported.
Only the competitions flagged with "Upload to Handicap Master" are exported.
From a competition's players, cancelled, deleted or timed-out bookings are excluded.
It's Handicap Master that decides when to read: the refresh frequency depends on its system.
It requires the integration enabled and a valid API key.
Frequently asked questions
Which way does the data flow?
One direction only: from Golfmanager to Handicap Master. It's Handicap Master that reads the data. It's not a two-way sync.
Are the handicaps imported back into Golfmanager?
No. Golfmanager doesn't store handicaps; it only shares member and competition data. The handicaps and results live in Handicap Master.
How do I enable the integration?
In Settings > Handicap Master, turn on "Enable integration" and save. Without this, Handicap Master can't read the data.
What is the API key for?
It's the "password" with which Handicap Master authenticates when reading the data. It's created in the API Keys section and given to Handicap Master.
Handicap Master can't connect. What should I check?
Check that the integration is enabled and that the API key is correct and you've provided it to Handicap Master. If the key is wrong, it won't be able to read the data.
I get "Handicap Master integration is not enabled". What do I do?
The "Enable integration" option is off. Turn it on in Settings > Handicap Master and save.
A competition doesn't appear in Handicap Master. Why?
Because it doesn't have "Upload to Handicap Master" enabled. Edit that competition's booking type, turn it on and fill in its times and players per round.
A member isn't exported. What should I check?
That they meet all the criteria: have gender, email notifications enabled and a current fee tag, and not be deleted. If any is missing, they aren't included.
What does it mean for a member to come out as "inactive" or "deleted"?
Active: their fee/tag is current. Inactive: the tag has expired. Deleted: the customer or the tag has been removed. The status is calculated automatically.
What value does Handicap Master use to match each player?
The membership number, which is sent as the card/player number. It's best for each member to have their number so Handicap Master recognizes them.
What happens if a member has no membership number?
They're still exported, but their card number will come out empty, which can make it harder for Handicap Master to match them. It's better to assign one.
What member data is shared?
Reference, first and last name, gender, date of birth, membership number, address (street, city, country, postcode), email and status.
What competition data is shared?
The identifier, the name, the date, the start and end time and the number of players per round.
Which players in a competition are shared?
Those entered in that competition, with their tee time, their position in the group, their name and their membership number. Cancelled, deleted or timed-out bookings are excluded.
How often is the data refreshed?
Handicap Master decides, as it's the one reading. Golfmanager exposes the data instantly when asked; the read frequency depends on its system.
Can I see what's going to be shared beforehand?
Yes. Administrators can preview the member, competition and player data to check everything is correct.
Do I have to do anything each day or before each tournament?
Nothing manual to send: it's enough to keep the members up to date and flag and fill in the competition data. The rest is done by Handicap Master when it reads.
Is there a scheduled automatic send (cron)?
Not from Golfmanager's side. Golfmanager doesn't send anything on its own: it only responds when Handicap Master asks for the data.
What permissions do I need to configure the integration?
System administrator permissions, which give access to the Handicap Master configuration and the data preview.
Can I cut off Handicap Master's access?
Yes: by disabling the integration or revoking the API key. From that moment, Handicap Master can no longer read the data.
Recommended best practices
Keep the member records complete (gender, email, membership number and current fee) so they export correctly.
Flag each competition and fill in its times and players per round before the event.
Use an API key dedicated to Handicap Master, so you can revoke it without affecting other integrations.
Preview the data at go-live to confirm members and competitions come out correct.