Introduction

The Global Racing Network (GRN) Reporting API provides a facility for wagering operators to upload bet data into the GRN Reporting system to make it available for reporting by the wagering operator, track owners, racing authorities and regulators. Bets are uploaded by meeting and race in batches of up to 1,000.

The data upload is made via an RPC JSON API to an HTTPS encrypted endpoint, which is secured using OAUTH2. Each GRN Wagering operator will be issued a client_id and a client_secret. See below for details on how the wagering operator's application should obtain an access_token to use with the API.

Upload application steps

After each race has finalised, but before the deadline (within 24 hours of the last race of the day in which the race took place according to the local timezone of the wagering operator), the race report must be uploaded according to the following steps:

If the application has an unexpired access_token then it may skip the next step of acquiring a token
The application must acquire an access_token from the oauth2_endpoint (see OAUTH2 below)
The application must submit the data as an HTTP POST to the api_endpoint with an HTTP header Authorization: with a value of Bearer <your_access_token> and a body containing the payload as defined below in Field Definitions.

Limitations

Each request must only be for a single meeting and race.
Each request must have an Authorization header with a valid token.
A maximum of 1,000 bets can be included in a single request (that is, the bets array can have a maximum of 1,000 elements).
All bets in a batch must be valid or the entire batch will be rejected.

Example request

V1

curl --location --request POST 'https://<grn_api_endpoint>/public/uploadRace' \
--header 'Authorization: Bearer <your_access_token>' \
--header 'Content-Type: application/json' \
--data-raw '{
"meeting_id":"191838",
        "race_number":2,
        "bets":[
   {
      "id":12345,
      "time":"2021-07-07T17:28:02+10:00",
      "info_type":"Fixed Odds",
      "medium":"Internet",
      "user_id":"789",
      "user_name":"JohnSmith",
      "user_state":"VIC",
      "terminal_id":"cash",
      "type":"win",
      "runner_number":2,
      "resulted":true,
      "status":"Paid",
      "amount":100,
      "price":10,
      "payout":0,
      "net_result":100
   }
]
}'

V2

curl --location --request POST 'https://<grn_api_endpoint>/public/uploadRaceV2' \
--header 'Authorization: Bearer <your_access_token>' \
--header 'Content-Type: application/json' \
--data-raw '{
   "meeting_id":"191838",
   "race_number":2,
   "bets":[
      {
         "id":"c3f3b0ca-e1f8-405b-81c7-6c319cf3a1ee",
         "time":"2021-07-07T17:28:02+10:00",
         "info_type":"Fixed Odds",
         "medium":"Internet",
         "user_id":"789",
         "user_name":"JohnSmith",
         "user_state":"VIC",
         "terminal_id":"cash",
         "type":"win",
         "runner_number":2,
         "resulted":true,
         "status":"Paid",
         "amount":100,
         "price":10,
         "payout":0,
         "net_result":100
      }
  ]
}'

Field definitions

For more details on how each field should be used for each bet type please see GRN Reporting Bet Descriptions, and for examples of payloads of each major category of bets see Example Payloads.

Field Name	Type	Additional Info
meeting_id	Integer	The GBS Meeting ID
race_number	Integer	The race number within the meeting
bets	Array	An array of bet objects
<bet> source	String	Code for the betting agency (optional if the `client_id` is for a single agency, required if the `client_id` is used for multiple agencies)
<bet> id (V1)	Integer	Bet identifier. Must uniquely identify the bet for the source.
<bet> id (V2)	String	Bet identifier. Must uniquely identify the bet for the source.
<bet> leg	Integer	(Optional, defaults to 1)
<bet> time	Datetime	Date-time that the bet was placed
<bet> type	String	Type of bet: `win`, `place`, `multi`, `exacta`, `trifecta`, `quaddie`, `firstfour`, `quinella`, `dailydouble`
<bet> runner_number	Integer	(Omit if `exotics_selection` is specified)
<bet> exotics_selection	String	Each runner separated by ",", and each position/leg separated by "/". Can included a postfix of "(BOXED)" for boxed bets. (Omit if `runner_number` is specified)
<bet> user_id	String	User id or client id in the source betting system. If a terminal is being used this must be one of `cash`, `anon`, or `anonymous`
<bet> user_name	String	Name or pseudonym of the user
<bet> user_state	String	State that the user is in when placing the bet (e.g. `NSW`)
<bet> terminal_id	String	The id of the betting terminal the bet is being placed on. Must be provided if `user_id` is one of `cash`, `anon`, or `anonymous`
<bet> info_type	String	The betting product, e.g. `Fixed Odds`
<bet> medium	String	Medium the bet was placed using, e.g. `internet`, `NativeApp`, `Phone`
<bet> resulted	Boolean	If the race has been resulted
<bet> status	String	One of: `Paid`, `Cancelled`, `FullRefund`, `Unresulted`, `Pending`, `PartialRefund`
<bet> bonus	Boolean	Is bet bonus. Optional (defaults to false)
<bet> back_indicator	Boolean	(Optional, Defaults to false)
<bet> bet_back_id	Integer	Bet ID of bet back
<bet> bet_back_agency	String	Bookmaker that the bet back has been placed with
<bet> bet_back_amount	Float	Stake amount of bet back. Dollar amount, 2 decimal places
<bet> bet_back_revenue	Float	Payout on bet back
<bet> bet_back_date	Datetime	Date/time of bet back placed
<bet> amount	Float	Dollar amount, 2 decimal places
<bet> price	Float	Dollar amount, 2 decimal places
<bet> payout	Float	Total payout
<bet> net_result	Float
<bet> currency	String	An ISO 4217 currency code (optional, defaults to configured currency for client_id and source)

OAUTH2

An app makes an HTTP POST request to oauth2_endpoint, and specifies the following parameters:
- grant_type – Set to client_credentials for this grant type.
- client_id – The client ID issued to the betting provider
In order to indicate that the app is authorised to make the request, the Authorization header for this request is set as “Basic BASE64(CLIENT_ID:CLIENT_SECRET)“, where BASE64(CLIENT_ID:CLIENT_SECRET) is the base64 representation of the client_id and the client_secret, concatenated with a colon.
Example
```
curl --location --request POST 'https://<oath2_endpoint>/token' \
--header 'Authorization: Basic BASE64(<client_id>:<client_secret>)' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=<client_id>'
```
The authorisation server returns a JSON object with the following keys:
- access_token – A valid access_token.
- expires_in – The length of time (in seconds) that the provided access token is valid for.
- token_type – Set to Bearer.

Parameters required from BetMakers for GRN Reporting API access

client_id - the OAUTH2 client identifier for the wagering operators upload application
client_secret - the OAUTH2 shared secret for the wagering operators upload application
oauth2_endpoint - the URL that the upload application should use to exchange the client authentication details for an access_token
grn_api_endpoint - the URL that the upload application should use to upload each race report