REST Overview

​

Base URL

https://partners.centaur.io

​

Auth

​

First request

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

​

What REST gives you

• Scope-gated reads across the partner feed, discovery, events, messages, generated summaries, positions, 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/feed
• GET /api/v1/channel-summaries
• GET /api/v1/aggregate-summaries
• GET /api/v1/positions
• GET /api/v1/positions/open
• GET /api/v1/traders/stats
• GET /api/v1/assets/stats
• GET /api/v1/traders/rankings
• GET /api/v1/activity-summaries
• GET /api/v1/openapi.json

​

Operational endpoint

• GET /healthz

​

Pagination essentials

• limit accepts up to 200 on general list reads and up to 100 source-message groups on the partner feed
• meta.nextCursor advances forward from the current page
• cursors remain usable if matching rows 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

• Available data reads
• Partner Feed guide
• Events documentation
• Contract limits
• API reference overview
• https://partners.centaur.io/api/v1/docs
• https://partners.centaur.io/api/v1/openapi.json