Skip to main content
Use REST when you want a direct integration with predictable request and response behavior.

Base URL

https://partners.centaur.io

Auth

Send your partner API key in the x-api-key header.

First successful request

curl -s 'https://partners.centaur.io/api/v1/events?limit=10' \
  -H 'x-api-key: <partner-api-key>'

What REST gives you

  • Scope-gated reads across events, messages, positions, discovery, and stats
  • Forward-only cursor pagination on list endpoints
  • Response envelopes with stable request IDs and echoed applied bounds where relevant
  • A generated OpenAPI reference with endpoint, parameter, and schema details
  • A secondary Swagger UI if you want a quick interactive view

Current endpoint families

  • GET /api/v1/traders
  • GET /api/v1/assets
  • GET /api/v1/events
  • GET /api/v1/messages
  • GET /api/v1/positions/closed/valid
  • GET /api/v1/positions/open
  • GET /api/v1/traders/{traderId}/stats
  • GET /api/v1/assets/{assetId}/stats
  • GET /api/v1/openapi.json

Operational endpoint

  • GET /healthz

Pagination essentials

  • limit accepts up to 100
  • meta.nextCursor advances forward from the current page
  • cursors remain usable if matching events disappear between requests
  • pagination reflects the current eligible set and is not a frozen snapshot
  • historical list reads may default to a bounded time window when startTime and endTime are omitted
  • historical list reads echo the applied bounds in data.meta.appliedTimeRange

Technical references

Last modified on April 17, 2026