API & webhooks
REST API basics (Pro)
Authenticate, query, and mutate every Qubed resource over HTTPS.
API access is a Pro and Elite feature. Generate a token from /dashboard/settings/api-keys. Tokens are scoped to your account, prefixed with onl_live_, and never shown again after creation — store them in a secret manager, not in your repo.
Authenticate every request with a bearer header: Authorization: Bearer onl_live_<token>. The base URL is https://qubed.xyz/api/v1. All responses are JSON; errors follow the standard { error: { code, message } } shape with HTTP status codes that match (401 for bad auth, 404 for missing resources, 429 for rate-limited).
Core resources mirror the database: pages, subscribers, events. Standard REST verbs work as you'd expect — GET /pages, POST /pages, PATCH /pages/:id, DELETE /pages/:id. Pagination uses ?cursor= and ?limit= (default 50, max 200).
Every successful mutation returns the full updated resource, so you don't need a follow-up GET. For high-volume writes (importing existing waitlists), prefer the bulk endpoints under /v1/pages/:id/subscribers/bulk — they accept up to 1,000 rows per request and skip the per-row rate limit.