Admaxxer Pixel API — Rate Limits

The Admaxxer Pixel API enforces a token-bucket-equivalent fixed window to protect every workspace from noisy neighbors and accidental runaway loops.

Limits

60 requests / minute / workspace across all /api/v1/* endpoints, including /me.
~3,600 req/hour sustained; 86,400 req/day sustained.
Separate limits apply to browser pixel traffic (not this API).

If you need a higher ceiling for a large warehouse backfill, email support@admaxxer.com with the workspace ID and target QPS — we can raise the limit per workspace.

Response Headers

Every successful response includes:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 57
X-RateLimit-Reset: 1713360000

X-RateLimit-Reset is a Unix timestamp (seconds) at which the window resets.

HTTP 429 Response

HTTP/1.1 429 Too Many Requests
Retry-After: 42

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Rate limit exceeded. Try again in 42 seconds.",
    "details": { "limit": 60, "window": "1 minute" }
  },
  "meta": { "request_id": "req_…" }
}

Client Guidance

Read the headers. Prefer X-RateLimit-Remaining as a steady signal. If it drops to 0, wait until X-RateLimit-Reset.
On 429, obey Retry-After. Add up to 10% jitter to avoid thundering-herd re-sync when many workers share a workspace.
Batch where possible. For server-to-server event ingest, the dashboard-side pipeline is designed around Tinybird batch flushes — prefer one event per meaningful user action over one event per UI click. Most integrations comfortably fit well under 60/min.
Separate read and write keys. Spiky write workloads should not starve steady read dashboards.

Bulk Ingest Patterns

The v1 POST /pixel/events endpoint accepts one event per call. For bulk historical backfills:

Ask support to provision a Tinybird direct-append token — this bypasses the public API entirely and lets you ship millions of rows in minutes.
Or spread the backfill across multiple API keys, each scoped to the same workspace, so you parallelize up to the per-workspace cap.
Array bodies and bulk endpoints would otherwise be capped at 1,000 items per request (GL#83) to keep failure blast radius small.

Tinybird JWT Pipes

The GET /pixel/metrics/{pipe} endpoint mints a JWT and returns it. The JWT has its own downstream rate limit enforced by Tinybird (typically generous). Our API call to mint counts as one request against the 60/min budget; your subsequent direct calls to Tinybird do not.

Monitoring

We emit structured log lines per rate-limit rejection. If you see unexpected 429s, check Settings › API Keys — the usage meter shows requests in the last hour per key.

Overview · Auth · Endpoints · Errors