Index
What is this integration?
The Golf Directo integration connects Golfmanager with the Golf Directo tournament management platform, which specializes in organizing and administering golf competitions and is integrated with the RFEG (Royal Spanish Golf Federation). Golf Directo covers the complete tournament workflow (sign-ups, categories, handicaps, pairings, results calculation, federation licenses and statistics), and the integration brings that whole flow into Golfmanager. It allows you to:
Show and sign up for tournaments from the customer portal (using their federation license), charging the entry fee in Golfmanager.
Import and sync tournaments into Golfmanager's tournaments module: tournament data, registrants, tee times and results.
It is a two-way connection: Golf Directo reads from and sends information to Golfmanager, and Golfmanager does the same towards Golf Directo. Thanks to this, a player can sign up for the same tournament both from the Golf Directo website and from the Golfmanager portal/app, and the sign-up is reflected in both systems.
The RFEG license is the player's federation number. The integration uses it to register each player in the Golf Directo tournament, so the customer must have it saved in their profile. Without a license, the player will not be able to sign up or see the federated tournaments section.
What problem does it solve?
Tournament sign-up from the portal: the member signs up and pays online, without going through reception.
Avoids double work: registrants, tee times and results are brought into Golfmanager without typing them in by hand.
Centralizes the charge: the entry fee is invoiced in Golfmanager with its product and payment method, and appears in the sales and payments list like any other sale.
Keeps tournaments up to date between Golf Directo and Golfmanager, with a sync status and the date of the last sync always visible.
Which systems does it connect and in which direction does the data flow?
It connects Golfmanager with Golf Directo through its API, in both directions:
Golf Directo → Golfmanager: tournaments are shown in the portal and, when they are imported or synced, their registrants, tee times and results enter Golfmanager.
Golfmanager → Golf Directo: when a player signs up (or cancels) in the portal, the sign-up is sent to Golf Directo. You can also push to Golf Directo the sign-ups you have created in Golfmanager.
What information is exchanged?
Information | Direction | Purpose |
Available tournaments (name, dates, format, description, sign-up windows) | Golf Directo → Golfmanager | Show them in the portal and be able to import them |
Player sign-up (customer, email, RFEG license) | Golfmanager → Golf Directo | Register (or cancel) the player in the tournament |
Registrants, tee times and results (scorecards: gross, net, stableford, position) | Golf Directo → Golfmanager | Sync the tournament in Golfmanager |
Confirmation of the entry fee payment | Golfmanager ↔ Golf Directo | Confirm the booking in Golf Directo when the entry fee is charged |
Authorization form
To authorize the integration between your club and Golf Directo through the API, before you start you must send Golfmanager the authorization document filled in and signed by both parties. You will find the document and the procedure at this link.
Prerequisites (before activating the integration)
Have a Golf Directo account and its API key (provided by Golf Directo, one per club).
Have the Golf Directo module installed (installed by the Golfmanager team), together with the tournaments, federation licenses, billing and customer portal modules.
The club's RFEG code and its RFEG password.
Having sent the authorization form signed by both parties.
That customers have their RFEG license in their profile so they can sign up.
Booking/tournament management permissions to configure and administer the integration.
How to set it up (step by step)
Getting started has three blocks: (A) configure the module inside Golfmanager, (B) prepare the connection from Golf Directo to Golfmanager, and (C) set up the access link to tournaments on the Booking website. Further down, in "Explanation of each field", you have the detail of what each field does.
A) Configure the module in Golfmanager (Golfmanager → Golf Directo)
Go to Settings > Golf Directo > Configuration.
Enter the API key that Golf Directo provided you.
Select the Environment: Production (golfdirecto.com) to operate for real, or Test (test.golfdirecto.com) to test without charging.
Select the Product with which the entry fee will be charged in Golfmanager.
Select the Payment method with which the entry fee payment will be recorded.
Enable Load iframe if you want the Golf Directo form to be shown embedded inside the portal during sign-up.
Enable Show tournaments on the portal home if you want the tournaments carousel to appear on the customer portal home page.
Enter the Club's RFEG code and the RFEG password.
Save the changes. When you save the RFEG code and password, the club is registered automatically in Golf Directo and the system receives and stores the Golf Directo password (an automatic, read-only field).
⚠️ Without the API key and the Product configured, sign-ups cannot be made and the system will show the notice "The module is not configured".
B) Prepare the connection from Golf Directo to Golfmanager (Golf Directo → Golfmanager)
So that the sign-ups, sales lines and payments made from the Golf Directo website reach Golfmanager automatically, we recommend contracting Golf Directo's full plan. Golf Directo connects with an admin API key that the Golfmanager team activates (the same key works for all clubs). Steps:
In Golfmanager, go to Settings > System > Users and create a new user:
Name: Golfdirecto
Email: info@golfdirecto.com
Type: Administrator
Go to Settings > Billing > Payment methods and create a payment method exclusively for Golf Directo with these values:
Name: "Golfdirecto" or "Golfdirecto Tournaments".
Type: Bank transfer.
Available online: Disabled.
Refund at POS: Enabled.
Allow change: Enabled.
Valid in API: Enabled.
Go to Golf Directo > Settings > Options > Golfmanager tab and fill in:
Associated payment method: the payment method you have just created for them.
Associated cash register: an existing cash register in Golfmanager or a new one specifically for Golf Directo.
Associated product: the default product that will be used if no other product is set when configuring a new tournament.
Save the changes on both platforms.
Important note about the payment gateway. It is not possible to reuse the same payment gateway (Redsys, Stripe…) that you have configured in Golfmanager, because on the gateway's website you can only register the merchant URL of Golfmanager's booking consumer. That is why the entry fee charged from Golf Directo is recorded using the dedicated payment method you created.
Explanation of each configuration field
These are the module fields in Settings > Golf Directo > Configuration. For each one we indicate what it is, its impact, an example and how the system behaves.
1. API key
Field name: API key.
Description: authentication key that identifies your club to the Golf Directo API. It is provided by Golf Directo and stored encrypted.
Impact on the system: it is the main credential; without it, no operation with Golf Directo works.
Usage example: you paste the key that Golf Directo sends you (for example, a long string of letters and numbers) and save.
What happens when it is used: Golfmanager sends it on every call to list tournaments, sign up, sync or cancel.
System behavior: if it is missing or incorrect, the system responds "The module is not configured" and no tournaments are shown or managed.
2. Environment
Field name: Environment.
Description: indicates which Golf Directo server the integration works against: Production (golfdirecto.com) or Test (test.golfdirecto.com).
Impact on the system: determines whether sign-ups and charges are real or test ones.
Usage example: during setup you choose "Test" to validate the flow; once everything works, you switch to "Production".
What happens when it is used: all calls are directed to the server of the selected environment.
System behavior: in "Test" no real operations are generated; remember to switch back to "Production" before opening sign-ups to the public.
3. Product
Field name: Product.
Description: the Golfmanager product used to charge and invoice the tournament entry fee.
Impact on the system: it defines the amount, the taxes and the accounting of the entry fee. It is required in order to sign up.
Usage example: you create or select a "Tournament entry" product with its price (and, if you want, prices per customer type) and assign it here.
What happens when it is used: when a player signs up, Golfmanager generates a sale of that product for the entry fee amount.
System behavior: if no product is configured, the sync and the sign-up warn that "Golf Directo is not configured" and the charge cannot be made.
4. Payment method
Field name: Payment method.
Description: the Golfmanager payment method with which the entry fee payment is recorded.
Impact on the system: determines on which method/cash register the entry fee payment is recorded.
Usage example: you select the payment method dedicated to Golf Directo (the one you created in step B) or the one you use for online charging.
What happens when it is used: when the entry fee payment is confirmed, the payment is posted with this payment method.
System behavior: the payment appears in the payments and itemized payments list, linked to the sale of the sign-up.
5. Load iframe
Field name: Load iframe.
Description: checkbox that decides whether the Golf Directo sign-up form is shown embedded inside the portal (iframe) or whether, instead, the customer is taken directly to the Golfmanager payment process.
Impact on the system: it changes the player's sign-up experience.
Usage example: you enable it if you want the player to complete the Golf Directo form without leaving the portal.
What happens when it is used: with the iframe enabled, after creating the booking the embedded form is shown and the portal periodically checks whether the player has completed it.
System behavior: if it is disabled, the player is redirected to the Golfmanager payment process (checkout).
6. Show tournaments on the portal home
Field name: Show tournaments on the portal home.
Description: checkbox that shows a tournaments carousel on the customer portal home page.
Impact on the system: improves tournament visibility for the player.
Usage example: you enable it when you want to promote open tournaments directly on the portal home page.
What happens when it is used: a carousel with the upcoming tournaments appears below the portal home menu.
System behavior: if it is disabled, tournaments are still accessible from the "Tournaments" link, but they are not shown on the home page.
7. Club's RFEG code
Field name: Club's RFEG code.
Description: federation code that identifies your club to the RFEG. A required field filled in by the club.
Impact on the system: together with the RFEG password, it registers your club in Golf Directo.
Usage example: you enter the code assigned to you by the RFEG.
What happens when it is used: when you save it together with the RFEG password, Golfmanager requests the club registration from Golf Directo.
System behavior: if the registration succeeds, Golf Directo returns the "Golf Directo password"; if it fails, the system reports an error registering the club.
8. RFEG password
Field name: RFEG password.
Description: the club's federation password. A required field filled in by the club and stored encrypted.
Impact on the system: it is required, together with the RFEG code, to register the club in Golf Directo.
Usage example: you enter the club's federation password and save.
What happens when it is used: when you save it, the club registration in Golf Directo is triggered.
System behavior: after a successful registration, the system receives and stores the Golf Directo internal password.
9. Golf Directo password (automatic)
Field name: Golf Directo password.
Description: password that Golf Directo generates and returns when the club is registered. It is read-only and must not be edited by hand.
Impact on the system: Golfmanager uses it internally to authenticate with Golf Directo.
Usage example: it is not filled in: it is completed on its own after saving the RFEG code and password.
What happens when it is used: the system uses it transparently in communications with Golf Directo.
System behavior: if it is empty, it usually means the club registration has not yet completed correctly; check the RFEG code and password and save again.
C) Access link to sign-ups on the Booking website
Once the Golf Directo module has been installed by the Golfmanager team, an access point is created automatically in the main menu of the Booking website that leads to all the tournaments published in Golf Directo. In addition, you can add a featured access point through a card on the home page:
Go to General Settings > CRM > Home cards.
Create a new card and enter the tournaments route in the URL: //consumer/golfdirecto/tournaments
Assign a priority to place the card in the desired position on the home page.
Save the changes.
Useful portal routes: //consumer/golfdirecto/tournaments (tournaments list) and //consumer/golfdirecto/mytournaments ("My sign-ups", where the player with an RFEG license sees the tournaments they are registered in).
How it is used day to day
Player sign-up (portal)
The player enters the portal and opens the Tournaments section.
They choose a tournament and click sign up. They need to have their RFEG license in their profile; if they don't, the system will ask for it.
They are charged the entry fee with the configured product and price (prices per customer type may apply). The payment is made in Golfmanager or, if the tournament has it enabled, in Golf Directo.
When the payment is confirmed, the sign-up is confirmed in Golf Directo and recorded in both systems.
If the sign-up is cancelled, Golfmanager also cancels it in Golf Directo.
Import and sync tournaments (administration)
From the tournaments list, click Import from Golf Directo: the system shows the tournaments available in Golf Directo.
Select the tournament to import. The tournament is created in Golfmanager linked to Golf Directo and marked as synced.
From the tournament detail, click Sync with Golf Directo and choose what to bring in/send:
Tournament data (name, dates, scoring format).
Registrants only (without tee times) or Tee times, which create registrants and bookings. These two options are mutually exclusive.
Results (scorecards with gross, net, stableford and position).
Send to Golf Directo the sign-ups made in Golfmanager that are not yet on the platform.
Confirm the sync. When it finishes you will see how many registrants, tee times, results and sent sign-ups have been processed.
The tournament detail shows the sync status (synced, with error or not synced) and the date of the last sync, so you always know whether the data is up to date.
Checking transactions, sales and payments
You have three places to review what the integration generates:
Golf Directo > Transactions: the record of sign-ups managed with Golf Directo. For each sign-up you will see the customer, the Golf Directo identifier, the status (draft, form completed, confirmed or cancelled), the linked sale, and, if there was one, the error. It is the first screen to check when a sign-up does not complete.
Sales list: when a player signs up, a sale of the sign-up product is generated, visible like any other sale.
Payments / itemized payments: if the sign-up requires payment, the payment is generated with the configured payment method.
Limitations to keep in mind
The player needs an RFEG license in their profile to sign up and to see the federated tournaments section.
It is aimed at federated tournaments managed with Golf Directo (RFEG / Spain scope).
The entry fee is charged with the configured product and payment method.
The payment gateway is not reused: the gateway already configured in Golfmanager is not reused for charging from the Golf Directo website (see the note in step B).
Syncing is on demand: registrants, tee times and results are brought in when the tournament is imported or synced.
It depends on the Golf Directo service: if it is unavailable, tournaments cannot be shown or signed up for at that moment.
Frequently asked questions (FAQ)
The system says "The module is not configured". What is missing?
The API key or the Product is missing in Settings > Golf Directo > Configuration. Complete both fields and save; without them, tournaments cannot be listed or signed up for.
A player cannot sign up and is told they need an RFEG license. How do I fix it?
The customer does not have the federation license saved in their profile. Add their RFEG license number to the customer's profile and they will be able to sign up. Remember that the license is also required to see the federated tournaments section.
When signing up, "License in use" appears. Why?
That license is already registered in that tournament in Golf Directo. Check whether the player was already signed up (in "My sign-ups" on the portal or in the Transactions) before trying again.
"The tournament service is not available" appears. What do I do?
Golf Directo is not responding at that moment. Try again later and check that the API key and the Environment are correct. If it persists, contact Golf Directo support.
I cannot sync a tournament. What is the reason?
The tournament is not linked to Golf Directo. Import it first from Import from Golf Directo to link it; from then on you will be able to sync it.
What is the difference between the Test and Production environments?
The Test environment (test.golfdirecto.com) is used to validate the configuration and the flow without generating real sign-ups or charges. The Production one (golfdirecto.com) operates for real. Test first in Test and switch to Production before opening sign-ups to the public.
Where do I see the payment for a sign-up?
In the sales list (the sale of the sign-up product) and in payments / itemized payments (the payment with the configured payment method). The sign-up detail is in Golf Directo > Transactions.
A sign-up has not completed. Where do I start looking?
Open Golf Directo > Transactions and find the customer's sign-up. Look at its status (draft, form completed, confirmed or cancelled) and the error field: the reason is usually there (license, payment not completed, service unavailable, etc.).
Can I use the same payment gateway (Redsys, Stripe…) I already have in Golfmanager?
Not for the charges that come from the Golf Directo website. On the gateway you can only register the merchant URL of Golfmanager's booking consumer. That is why a dedicated payment method (Bank transfer type) is created to record those charges.
Can a player sign up both from Golf Directo and from Golfmanager?
Yes. The integration is two-way: sign-ups made on either platform are reflected on the other. Those made in Golfmanager can be sent to Golf Directo, and those made in Golf Directo come in when the tournament is synced.
What exactly is brought in when a tournament is synced?
You can bring in the tournament data (name, dates, format), the registrants, the tee times and the results. The "registrants only" and "tee times" options are mutually exclusive. You can also send to Golf Directo the sign-ups created in Golfmanager.
How do I know whether a tournament is up to date?
The tournament detail shows the sync status (synced, with error or not synced) and the date of the last sync. If it shows "with error", sync again and check the message.
What happens if I cancel a sign-up in Golfmanager?
Golfmanager also cancels the corresponding booking in Golf Directo, so the player no longer appears registered in either system.
The Golf Directo form does not appear inside the portal. Why?
Check the Load iframe checkbox. If it is enabled, the form is shown embedded in the portal; if it is disabled, the player is redirected directly to the Golfmanager payment process.
Is it advisable to put emojis in the tournament name?
No. As a best practice, avoid emojis and special characters in the tournament name to prevent display or sync problems between platforms. Use plain text names.
Recommended best practices
Make sure members have their RFEG license in their profile so they can sign up.
Configure the entry fee product and price well (including prices per customer type if applicable).
Test first in the Test environment before operating in Production.
Sync the tournament before and after the event to keep registrants, tee times and results up to date.
Use simple tournament names, without emojis or special characters.
Review the Transactions whenever a sign-up does not complete.
Contact details
Juan Antonio Sánchez
28350, Madrid (Spain)
Support and contact: contacto@golfdirecto.com
Sales department: comercial@golfdirecto.com