ScatterKings

iGaming RGS provider: list games, launch sessions, issue/cancel free rounds, and pull round history. Requests signed with an HMAC-SHA256 SK-Signature header; inbound bet/win/rollback/balance callbacks delivered as webhooks.

Detail	Value
Category	iGaming
Base URL	https://{environment}/integrationservice/api/sk/v1/{operator_id}
Authentication	HMAC-SHA256
Endpoints	8
Connector key	scatter-kings

Using ScatterKings in a workflow

1. Go to Connections and click New Connection.
2. Pick ScatterKings from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /games	List available games
GET /games/{gameID}	Get details for a specific game
POST /play/start	Launch a remote gaming session
POST /freerounds/issue	Issue free rounds to a player
GET /freerounds/get	Retrieve details of an issued set of free rounds
POST /freerounds/issuecustombet	Issue custom-bet free rounds (Buy Bonus / Extra Bet)
POST /freerounds/cancel	Cancel a previously issued set of free rounds
GET /rounds/{roundID}	Get the financial summary and replay link for a round

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /games

List available games

Detail	Value
Operation ID	listGames
Method	GET
Path	/games

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ScatterKings connection from the Connection dropdown.
3. In the Operation dropdown, select listGames.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ScatterKings API reference.

GET /games/{gameID}

Get details for a specific game

Detail	Value
Operation ID	getGameDetails
Method	GET
Path	/games/{gameID}

Parameters

Name	Location	Type	Required
gameID	path	string	Yes
currencies	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ScatterKings connection from the Connection dropdown.
3. In the Operation dropdown, select getGameDetails.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ScatterKings API reference.

POST /play/start

Launch a remote gaming session

Detail	Value
Operation ID	startSession
Method	POST
Path	/play/start

Parameters

No parameters.

Request Body

Field	Type
GameID	string
Mode	string
Currency	string
Language	string
PlayerID	string
ClientType	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ScatterKings connection from the Connection dropdown.
3. In the Operation dropdown, select startSession.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ScatterKings API reference.

POST /freerounds/issue

Issue free rounds to a player

Detail	Value
Operation ID	issueFreeRounds
Method	POST
Path	/freerounds/issue

Parameters

No parameters.

Request Body

Field	Type
OperatorFreeRoundsIssueID	string
PlayerID	string
GameIDs	array
NumFreeRounds	integer
FreeRoundValue	number
FreeRoundCurrency	string
ValidUntil	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ScatterKings connection from the Connection dropdown.
3. In the Operation dropdown, select issueFreeRounds.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ScatterKings API reference.

GET /freerounds/get

Retrieve details of an issued set of free rounds

Detail	Value
Operation ID	getFreeRounds
Method	GET
Path	/freerounds/get

Parameters

Name	Location	Type	Required
FreeRoundsIssueID	query	string	No
OperatorFreeRoundsIssueID	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ScatterKings connection from the Connection dropdown.
3. In the Operation dropdown, select getFreeRounds.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ScatterKings API reference.

POST /freerounds/issuecustombet

Issue custom-bet free rounds (Buy Bonus / Extra Bet)

Detail	Value
Operation ID	issueCustomBetFreeRounds
Method	POST
Path	/freerounds/issuecustombet

Parameters

No parameters.

Request Body

Field	Type
OperatorFreeRoundsIssueID	string
PlayerID	string
GameID	string
NumFreeRounds	integer
FreeRoundValue	number
FreeRoundCurrency	string
ValidUntil	string
BetModeName	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ScatterKings connection from the Connection dropdown.
3. In the Operation dropdown, select issueCustomBetFreeRounds.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ScatterKings API reference.

POST /freerounds/cancel

Cancel a previously issued set of free rounds

Detail	Value
Operation ID	cancelFreeRounds
Method	POST
Path	/freerounds/cancel

Parameters

No parameters.

Request Body

Field	Type
FreeRoundsIssueID	string
OperatorFreeRoundsIssueID	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ScatterKings connection from the Connection dropdown.
3. In the Operation dropdown, select cancelFreeRounds.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ScatterKings API reference.

GET /rounds/{roundID}

Get the financial summary and replay link for a round

Detail	Value
Operation ID	getRoundHistory
Method	GET
Path	/rounds/{roundID}

Parameters

Name	Location	Type	Required
roundID	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your ScatterKings connection from the Connection dropdown.
3. In the Operation dropdown, select getRoundHistory.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream ScatterKings API reference.