Developer Docs

Start quickly, authenticate correctly, and understand request behavior when you scale.

Quickstart

  1. 1. Create a key in your dashboard.
  2. 2. Use `Authorization: Bearer <key>`.
  3. 3. Call the API and verify response headers.
curl -X GET 'https://api.ticketdaddy.io/v1/events' \
  -H 'Authorization: Bearer sk_live_your_api_key' \
  -H 'Content-Type: application/json'

Authentication

Use secret keys (`sk_*`) on trusted servers and public keys (`pk_*`) for browser-safe access patterns.

Rate Limits

API keys are rate-limited per key. Responses expose `X-RateLimit-Limit`, `X-RateLimit-Remaining`, and `X-RateLimit-Reset` headers.

Rate-limit behavior update

If you previously saw unexpected throttling while load-testing parallel requests, that was caused by a global server limiter being hit before per-key limits. The API now prioritizes key-level limits for authenticated requests and returns clearer `429` behavior.

Inspect usage in dashboard