Request IDs & logs

Every response carries an X-Request-Id. It is the fastest route from "something went wrong" to an answer, and the first thing support will ask for.

It travels in both directions. The id on a call you make to us is one half; the id we put on a call we make to your wallet is the other, and that is the half most integrations need, because most movements are raised by a player inside the launcher rather than by you.

The header#

HTTP/1.1 422 Unprocessable Entity
X-Request-Id: fa1bc6b7-bd54-480e-92c1-6ffa700d6039
Content-Type: application/json

The same value appears as request_id inside every error body, so you can log it whether or not you keep response headers.

Supplying your own#

Send X-Request-Id and we will use it instead of generating one. If you already have a trace id, passing it through means one identifier spans your logs and ours.

It must be 1–128 characters of letters, digits, dot, colon, underscore or hyphen — the shapes real tracing produces, UUIDs and hex trace ids included. Anything else is dropped and we generate our own instead.

await fetch(url, {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${token}`,
    "Content-Type": "application/json",
    // Your trace id, carried through to our logs.
    "X-Request-Id": ctx.traceId,
  },
  body: JSON.stringify(payload),
});

What to log#

• The request id, on both success and failure.
• The error code, never the message.
• Your transaction_id, so a support question can be answered from either end.
• Never the token, never the credential secret.

logger.warn({
  request_id: body.error.request_id,
  code: body.error.code,
  transaction_id: payload.transaction_id,
  status: res.status,
}, "casinoapipro rejected a movement");

The id on calls we make to you#

Every call we make to your wallet carries x-request-id. It is our id for the request that caused the movement: the same id we returned to you when you raised it through /v1/transactions/*, and our id for the player's action when the launcher raised it — in which case you never saw it, because you made no call.

Store it against your own wallet row. It is the one value that exists on both sides of the conversation, and you can quote it straight back at us:

That returns every movement we raised on a round with your wallet's response body verbatim and the request_id we sent on each. See running it from your own servers.

The API request log#

A searchable log of your recent calls — method, path, status, request id and duration — in the dashboard and over the API. It is the right first stop when an integration behaves differently in production than on your machine, because it shows what we actually received rather than what you believe you sent.