> For the complete documentation index, see [llms.txt](https://fast-track.gitbook.io/integration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fast-track.gitbook.io/integration/master.md).

# Integration Guides

Welcome to a step-by-step guide on how to successfully integrate Fast Track.

## Integration Summary

On this page, you will find basic information on **how to integrate Fast Track.** \
We have also added links to relevant pages where you can learn how to enhance your integration with various events and channels.&#x20;

### 🗝 Fast Track CRM Connects via Real-Time Data Feed

Watch the video for a quick run-through of how your system will integrate with Fast Track CRM;

{% embed url="<https://fasttrack.portal.trainn.co/share/2r1sXu9lOBFjKVafd1ofKw/>" %}

\
The Fast Track CRM system runs entirely off a real-time data feed. \
When Registrations and Logins happen in your system, these events need to be published to the integration platform so that you can trigger Activities and Actions in real-time while keeping the relevant segmentation model up to date.\
\
The real-time messages are slim and only contain the bare minimum information required; Fast Track CRM will do lookups on endpoints provided by the Operator to fetch relevant data about the user.

<figure><img src="https://357701980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MCg9QyqC6McmUsJ27o3%2Fuploads%2FuHz4oMXnHMoQ5xqDRrSq%2Fimage.png?alt=media&amp;token=4e70a475-c63a-4200-aa56-740c41554ad1" alt=""><figcaption><p>Overview of Fast Track CRM real-time data integration</p></figcaption></figure>

### 🔁 Integration Steps

Basic integration will give a sufficient start for most **Operators to go live.** This includes the ability to trigger activities in real-time and build initial player life cycles based on deposit patterns and behaviours.

| **Step** | **Item**                        | **Description**                                                                                                                                                                                 |
| -------- | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1        | Authentication and Headers      | <p>The API endpoint provided by the Operator must be protected with authentication. We support <code>X-Api-Key</code> header, OAuth (client\_credentials), and basic authentication.</p><p></p> |
| 2        | Provide GetUserDetails Endpoint | API endpoint to retrieve user details from Operator to keep Fast Track CRM database up to date.                                                                                                 |
| 3        | Provide GetConsents Endpoint    | API endpoint to retrieve marketing communication preferences from Operator to keep Fast Track CRM database up to date.                                                                          |
| 4        | Provide GetBlocks Endpoint      | API endpoint to retrieve user blocks and exclusions from Operator to keep Fast Track CRM database up to date.                                                                                   |
| 5        | Publish Registrations           | Publish message in real-time when there is a new registration                                                                                                                                   |
| 6        | Publish Logins                  | Publish message in real-time when there is a login                                                                                                                                              |
| 7        | Publish Payments                | Publish message on deposits and withdrawals                                                                                                                                                     |

## 🔚 Endpoints Needed From Operator

To support the basic integration, Operators should send certain endpoints to Fast Track CRM. You can find more information about these below.&#x20;

We go through all the relevant endpoints and how to send them in the section **Operator API:**

{% embed url="<https://www.fasttrack-solutions.com/en/resources/integration/operator-api/user-details>" %}

**The** **relevant endpoints** for Operator API consist of the following:&#x20;

* [Consents ](https://fast-track.gitbook.io/integration/operator-api/consents.md)
* [Player Blocks](https://fast-track.gitbook.io/integration/operator-api/player-blocks.md)
* [User Details](https://fast-track.gitbook.io/integration/operator-api/user-details.md)
* [Bonus Crediting](https://fast-track.gitbook.io/integration/operator-api/bonus-crediting.md)

### ✔️ Reconciliation&#x20;

In order to ensure there are no data discrepancies between your platform and Fast Track CRM, we need you to build a **reconciliation endpoint** in the operator API. \
\
You can find the endpoints we need from the operator here:&#x20;

{% embed url="<https://www.fasttrack-solutions.com/en/resources/integration/operator-api/reconciliation>" %}

## ⏱ Real-Time Events

Any real-time event should ideally be published to Fast Track CRM Integration API **within 1 second** of the event taking place in the platform. Failure to comply with this can cause poor customer experience.

Some real-time events are necessary for the Operator to send to be able to use vital functionality in Fast Track CRM. Others are optional, but always desirable where possible, as these further enhance the Operator's integration.&#x20;

{% hint style="danger" %}
If the API is not responding with 200 (OK), you will need to ensure that the event is retried until a successful response. This is to make sure that the event is not lost.
{% endhint %}

{% hint style="info" %}
**IMPORTANT**: If you intend on sending us more than 100-200 messages per second, we highly recommend using either Rabbit or Kafka instead of REST API.
{% endhint %}

Read more about which real-time events you can include and how to send them:&#x20;

{% embed url="<https://www.fasttrack-solutions.com/en/resources/integration/real-time-data/registrations>" %}

#### Real-Time Events You Need To Send

The below events must be sent on the Fast Track CRM Integration API:

* [Registrations](https://fast-track.gitbook.io/integration/real-time-data/registrations.md)&#x20;
* [Login](https://fast-track.gitbook.io/integration/real-time-data/login.md)
* [Consents](https://fast-track.gitbook.io/integration/real-time-data/consents.md)
* [Player Blocks](https://fast-track.gitbook.io/integration/real-time-data/player-blocks.md)
* [Payments](https://fast-track.gitbook.io/integration/real-time-data/payments.md)

#### Real-Time Events for Extended Integration&#x20;

The optional real-time events are covered in more detail here:&#x20;

* [Balance](https://fast-track.gitbook.io/integration/real-time-data/balances.md)
* [Casino](https://fast-track.gitbook.io/integration/real-time-data/casino.md)
* [Lottery](https://fast-track.gitbook.io/integration/real-time-data/lottery-and-scratch.md)&#x20;
* [Sportsbook](https://fast-track.gitbook.io/integration/real-time-data/bet-placement.md)

## ☎︎ Channels&#x20;

Fast Track allows Operators to manage **various engagement channels** directly from one platform. You can find the currently integrated channels and how to enable them here:&#x20;

{% embed url="<https://www.fasttrack-solutions.com/en/resources/integration/channels/email>" %}
