155API

Operator API

Endpoints you must implement for 155.io integration


These are the endpoints you must implement on your side. 155.io will call these endpoints to manage player balances and transactions.

Required Endpoints

Security Requirements

Required

Your API must validate all incoming requests and sign all outgoing responses.

  1. Validate incoming requests using the X-Marbles-Signature header
  2. Sign outgoing responses with your private key in the X-Marbles-Signature header

See Security for implementation details.

Idempotency

All endpoints must be idempotent. If a request is executed multiple times, it should return the same response (even if the request ID differs).

If the same transactionId is received with a different payload, return DUPLICATE_TRANSACTION_ERROR.

Response Format

All responses must include:

{
  "status": "SUCCESS",
  "requestId": "original-request-id",
  "clientPlayerId": "player-id",
  "currency": "USD",
  "balance": 1000000
}

Balance values use 5-digit precision: $10.00 = 1000000

On this page