RIP.BET Docs

Support

If an integration fails, collect:

  • Environment and base URL.
  • Endpoint, method, and timestamp.
  • Request id, if the response includes one.
  • HTTP status.
  • Problem type, title, and detail.
  • Wallet address involved, if relevant.
  • Market family and asset or outcome id.

Do not send private keys, seed phrases, raw long-lived tokens, or full JWTs.

Useful checks

Before opening a support request:

  1. Call /v1/runtime-config.
  2. Confirm the market family is enabled.
  3. Confirm the user has access with /v1/access/self.
  4. Refresh the relevant market metadata endpoint.
  5. Retry transient 503 responses with backoff.

Public docs scope

These docs do not include admin routes, operator controls, service deployment, database access, cache keys, monitoring dashboards, or payout operations.

On this page