API reference
Base URLs, authentication and conventions, and every endpoint.
Base URLs
https://api.sekaibeyond.com (works from mainland China; see the relay)
https://sekaibeyond.com/api (everywhere else)Both take the same paths and answer the same way. See Calling from mainland China for the relay.
Authentication
Every request carries the key:
Authorization: Bearer sbk_…
Content-Type: application/json (POST only)Keys are made by core-staff in the admin panel. See API keys.
Conventions
- JSON in and out, in UTF-8.
- Timestamps are ISO 8601 in UTC, such as
2026-11-14T18:00:00.000Z, ornullwhen not set. - Text fields are
""when not set, nevernull. Each Chinese field (ending inCn) may be""; the site then shows the English one. - Fields may be added over time, so ignore any you don't know.
Endpoints
| Endpoint | Scope | What it does |
|---|---|---|
GET /v1/events | events:read | List every event, archived ones included |
GET /v1/events/{eventId} | events:read | Get one event, such as to check it just before taking payment |
POST /v1/events/{eventId}/orders | tickets:write | Issue an order's tickets once it's paid |
GET /v1/events/{eventId}/orders/{orderId} | tickets:read | Get an order, with whether each ticket has been used |
What they return:
- The Event object: both kinds of event the site has, unarchived and archived, and their fields
- The Order object: an order and its tickets
Prices stay in the seller's app, since events don't store them.