Operator endpoints

Requests are made to operator platforms through POST endpoints using JSON messages.

TechnoBin-Bridge requests contain an unique requestID that must be used by the operator for tracking and idempotency purposes. Additionally, the access token configured in the TechnoBin management panel is sent in the header. All requests include the following headers:

Header	Description
Content-Type	application/json
Authorization	Bearer [Access Token]

It is advised to keep response times lower than 500 ms in order to avoid timeouts and ensure a good user experience.

Endpoints

Auth

The /auth endpoint is used to authenticate a player when accessing a game via the URL provided through game launch. Sessions may be expired after a period of inactivity, TechnoBin recommends an expiration time of 24 hours.

Field	Type	Description	Required
requestID	string	Unique request ID in UUIDv4 format	Yes
gameID	string	Game ID	Yes
player.id	string	Player’s public ID	Yes
player.session	string	Player’s session token	Yes

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75",
  "gameID": "some_game",
  "player": {
    "id": "player1",
    "session": "session123"
  }
}

Response Contents

fields
Example

Field	Type	Description	Required
requestID	string	Echoes the `requestID` sent	Yes
authenticated	bool	Confirmation of a player authentication state	Yes

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75",
  "authenticated": true
}

Wallet

/wallet is used to get player wallet information to show relevant information on the game UI. It may also be used as authentication check in certain games.

Request Contents

Fields
Example

Field	Type	Description	Required
requestID	string	Unique request ID in UUIDv4 format	Yes
gameID	string	Game ID	Yes
player.id	string	Player’s public ID	Yes
player.session	string	Player’s session token	Yes

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75",
  "gameID": "some_game",
  "player": {
    "id": "player1",
    "session": "session123"
  }
}

Response Contents

Fields
Example

Field	Type	Description	Required
requestID	string	Echoes the `requestID` sent	Yes
player.id	string	Player’s public ID	Yes
player.session	string	Player’s session token	Yes
player.nickname	string		Yes
balance.currency	string	Player account currency	Yes
balance.amount	number	Player account balance	Yes

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75",
  "player": {
    "id": "player1",
    "session": "session123",
    "nickname": "John Doe",
  },
  "balance": {
    "currency": "USD",
    "amount": 123.45
  }
}

Bet

This endpoint is used when a player wants to make a bet on a game. The operator platform is responsible for ensuring the player has sufficient funds to complete the transaction and for debiting the amount using an atomic operation.

Request Contents

Fields
Example

Field	Type	Description	Required
requestID	string	Unique request ID in UUIDv4 format	Yes
gameID	string	Game ID	Yes
roundID	string	Round ID	Yes
player.id	string	Player’s public ID	Yes
player.session	string	Player’s session token	Yes
bet.currency	string	Player account currency	Yes
bet.amount	number	Bet amount	Yes
metadata	object	Additional information depending on game	*

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75",
  "gameID": "some_game",
  "roundID": "round123",
  "player": {
    "id": "player1",
    "session": "session123"
  },
  "bet": {
    "currency": "USD",
    "amount": 123.45
  },
  "metadata": {
    "channel": "my-channel",
    "ticketIDs": ["ticket123", "ticket456"]
  }
}

Response Contents

Fields
Example

Field	Type	Description	Required
requestID	string	Echoes the `requestID` sent	Yes
player.id	string	Player’s public ID	Yes
player.session	string	Player’s session token	Yes
balance.currency	string	Player account currency	Yes
balance.amount	number	Player account balance	Yes

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75",
  "player": {
    "id": "player1",
    "session": "session123"
  },
  "balance": {
    "currency": "USD",
    "amount": 123.45
  }
}

Win

This endpoint is used to credit player wins.

Request Contents

Fields
Example

Field	Type	Description	Required
requestID	string	Unique request ID in UUIDv4 format	Yes
gameID	string	Game ID	Yes
roundID	string	Round ID	Yes
player.id	string	Player’s public ID	Yes
win.amount	number	Credit amount	Yes
metadata	object	Additional information depending on game	*

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75",
  "gameID": "some_game",
  "roundID": "round123",
  "player": {
    "id": "player1"
  },
  "win": {
    "amount": 123.45
  },
  "metadata": {
    "channel": "my-channel",
    "round": "round123",
    "ticketID": "ticket123"
  }
}

Response Contents

Fields
Example

Field	Type	Description	Required
requestID	string	Echoes the `requestID` sent	Yes

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75"
}

Refund

This endpoint is used in critical failures, multi-player game cancellations and other technical issues to refund player bets.

Request Contents

Fields
Example

Field	Type	Description	Required
requestID	string	Unique request ID in UUIDv4 format	Yes
gameID	string	Game ID	Yes
roundID	string	Round ID	Yes
refunds	object[]	Refunds to be made	Yes
refunds.requestBetID	string	Bet request ID to be refunded	Yes
refunds.player.id	string	Player’s public ID	Yes
refunds.refund.amount	number	Refund amount	Yes
metadata	object	Additional information depending on game	*

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75",
  "gameID": "some_game",
  "roundID": "round123",
  "refunds": [
    {
      "requestBetID": "9ae4ba77-8bba-4a0b-8adc-c4cd9544de66",
      "player": {
        "id": "player1"
      },
      "refund": {
        "amount": 123.45
      }
    }
  ],
  "metadata": {
    "reason": "round-cancelled"
  }
}

Response Contents

Fields
Example

Field	Type	Description	Required
requestID	string	Echoes the `requestID` sent	Yes

{
  "requestID": "c6ea5494-7972-4adc-88c9-e0e3a1f4bd75",
}

Resources

Parameters Fields available for currency and other parameters.