Index
What is this integration?
Tagmarshal is an external pace-of-play control and GPS tracking system for the groups on the course. It uses GPS technology and real-time analytics to improve operational efficiency, the player experience and the course's revenue.
Golfmanager does not have a specific Tagmarshal module, but it offers a public API that Tagmarshal can use to read your club's tee times and bookings (the tee sheet) to know who is playing and at what time.
In other words, the integration is built by connecting Tagmarshal to the Golfmanager API, with the help of the Golfmanager team (which enables the access) and of Tagmarshal.
An API is a controlled "gateway" for two programs to communicate. The Golfmanager API lets Tagmarshal query the course's bookings without directly accessing the database.
What problem does it solve?
Tagmarshal knows who is playing and when without typing it in: it takes the tee times from Golfmanager.
Better pace-of-play control: it links the on-course tracking with the real bookings.
Avoids double management of the tee sheet.
Always up-to-date data through the API.
Which systems does it connect and in which direction does the data travel?
It connects Golfmanager with Tagmarshal. The usual direction is from Golfmanager to Tagmarshal:
Tagmarshal queries the API for the course's tee times and bookings and brings them in.
It is not an "out-of-the-box" automatic sync: it is a connection that is configured once and then works on its own.
The on-course tracking (positions, pace) is managed in Tagmarshal.
What information is shared?
Data | What Tagmarshal uses it for |
Bookings / tee times (tee sheet) | To know which groups go out and at what time |
Players / customers | To identify the groups in the tracking |
You decide, with Tagmarshal, what data is queried and how often.
Prerequisites (before you start)
Have Tagmarshal contracted and operating on the course.
Access to the Golfmanager API enabled for Tagmarshal (the Golfmanager team activates it; see below).
The Tagmarshal team or your IT to configure the reading of the tee times.
Administration permissions to create the Tagmarshal user and customer in your club.
Authorization form
To authorize the integration between your company and Tagmarshal through the API, you normally need to send Golfmanager a document filled in and signed by both parties before you start. Your implementation team will tell you the specific form and how to submit it.
How to set it up (step by step)
The setup has one part done by the club and another done by the Golfmanager team.
Club's part
Step 1 — Create the Tagmarshal user:
Go to Settings Menu > System > Users.
Create a new user.
Use as email
info@tagmarshal.com.Save the changes.
Step 2 — Create the Tagmarshal customer:
Go to Main Menu > Customers.
Create a new customer.
Use as email
info1@tagmarshall.com.Save the changes.
Golfmanager team's part
This step is done by our team (not the club). It is done from Superadmin > Multitenants Api:
In the "Tagmarshal User" API > Tenants tab, a new entry is created, the club's tenant is searched for and saved; the API code is copied and pasted into the user created in Step 1.
In the "Tagmarshal Customer" API > Tenants tab, it is repeated: the tenant is added, the code is copied and pasted into the customer created in Step 2.
Final step — Provide the data to Tagmarshal: once access is enabled, Tagmarshal is given what it needs to query the tee times (API key and club identifier). Afterwards it is advisable to test with a day of tee times and validate that it receives them.
🛠️ Technical note (for IT): the Golfmanager API (version 3) exposes the data via addresses like "api / model / model-name" (for example, bookings). Authentication uses two headers: the API key (key header) and the club identifier (tenant header). It allows filtering by dates, selecting fields and paginating. There is documentation and a test environment ("playground") in the API documentation routes.
The connection elements in detail
This integration does not have its own "configuration fields" screen; it is based on creating a few elements and on API access. They are explained below.
1) Tagmarshal user
• Field name: User (Settings > System > Users), with email info@tagmarshal.com
• Description: The Golfmanager user under which Tagmarshal accesses the API. Its permissions define what it can read.
• Impact on the system: The API key inherits this user's permissions; only what they can see is accessible.
• Usage example: you create it with the indicated Tagmarshal email.
What happens when it is used: the Golfmanager team associates the "Tagmarshal User" API code with it.
System behavior: without this user, there is no credential for Tagmarshal to query the API with.
2) Tagmarshal customer
• Field name: Customer (Main Menu > Customers), with email info1@tagmarshall.com
• Description: The customer associated with the "Tagmarshal Customer" API.
• Impact on the system: It complements the integration's access on the customer side.
• Usage example: you create it with the indicated email for Tagmarshal.
What happens when it is used: the Golfmanager team pastes the corresponding API code into it.
System behavior: it lets the connection work fully (user + customer).
3) API code / key
• Field name: API code (Superadmin > Multitenants Api)
• Description: The code that authenticates Tagmarshal's requests. It is generated and associated by the Golfmanager team to the user and the customer.
• Impact on the system: It is the access "key": it identifies Tagmarshal to the API.
• Usage example: the Golfmanager team copies the tenant's code and pastes it into the user/customer.
What happens when it is used: Tagmarshal sends it in every query and the API responds with the tee times.
System behavior: if the code is incorrect, the API rejects the request.
4) Club identifier (tenant)
• Field name: Tenant (club identifier)
• Description: Your club's name/identifier in Golfmanager, which travels alongside the API key.
• Impact on the system: It indicates which club the queried tee times belong to.
• Usage example: it is provided to Tagmarshal together with the API key.
What happens when it is used: the queries are directed to your club's data.
System behavior: a wrong tenant means the tee times are not found.
ℹ️ Note: technically, the API key (key header) and the club identifier (tenant header) are the two headers Tagmarshal sends in every request. The exact menu names may vary slightly depending on your version.
How the connection works
Tagmarshal queries the tee times in Golfmanager (for example, the day's) through the API.
With that information, it associates each group on the course with its booking and controls its pace of play.
Security: each query is signed with the API key and respects the permissions of the associated user.
Usage limits: the API may have a maximum number of requests per minute/hour to protect the service.
Limitations to keep in mind
It is not a "ready-to-use" connector: it requires configuring the reading on the Tagmarshal side and the access being enabled by the Golfmanager team.
The tracking and pace of play live in Tagmarshal; Golfmanager provides the tee times.
It respects permissions and usage limits: the API key only accesses what its user can see.
The update frequency is defined by the Tagmarshal configuration.
Frequently asked questions
Is there a Tagmarshal module in Golfmanager?
No. The integration is done through Golfmanager's public API: Tagmarshal queries your tee times via that API. There is no module or dedicated Tagmarshal configuration screen in Golfmanager.
What do I (the club) have to do to enable it?
Create the user (email info@tagmarshal.com) and the customer (email info1@tagmarshall.com) in Golfmanager, and sign the authorization form. The Golfmanager team enables the API access and generates the codes.
Who generates the API key?
It is generated by the Golfmanager team from Superadmin and associated with the user and customer you created. It is then provided to Tagmarshal.
Tagmarshal does not receive the tee times.
It is usually due to an incorrect API key or club identifier. Check with support the key and the club name provided to Tagmarshal.
Data from some bookings is missing.
The API user does not have permission over that data. Review the permissions of the user associated with the key.
A too-many-requests warning appears.
The queries are too frequent and the API's usage limit is reached. Reduce the query frequency in Tagmarshal.
The groups do not match the tee times.
It is usually a lag between the query and last-minute changes in the tee sheet. Adjust the update frequency with Tagmarshal.
What data does Tagmarshal see?
The tee times/bookings (who plays and at what time) and the players/customers needed to identify the groups, always within what the user's permissions allow.
Does the integration send data back to Golfmanager?
The usual use is read-only: Tagmarshal queries the tee times. The tracking and pace of play are managed in Tagmarshal.
How often are the tee times updated in Tagmarshal?
It is defined by the Tagmarshal configuration (how often it queries the API), respecting the usage limits.
Recommended best practices
Use a dedicated user for Tagmarshal, with just the right permissions to read the tee times.
Test with a day of tee times before operating live.
Agree on the update frequency with Tagmarshal so as not to exceed the API limits.
Document the connection (what is queried and how often) for its maintenance.
Need help?
To create the user and the customer, sign the authorization or enable the API access, write to us through the blue bubble in your management software: the Golfmanager team handles the Superadmin part. For the tracking configuration and the reading of the tee times in their system, also contact the Tagmarshal team.