PlanningTrack API · Free beta

Errors and limits

Use HTTP status, a stable error code, and a request ID to handle failures.

{
  "error": {
    "code": "invalid_parameter",
    "message": "receivedFrom must not be after receivedTo.",
    "param": "receivedFrom",
    "requestId": "example-request-id"
  }
}

Status	Code	Action
400	invalid_parameter / invalid_cursor	Correct input; restart pagination if filters changed.
401	authentication_required / invalid_api_key / api_key_revoked	Supply a valid active key.
403	access_denied	Verify your account’s email.
404	not_found	Check the endpoint and returned resource ID.
405	method_not_allowed	Use GET or HEAD.
409	snapshot_unavailable	Restart document or timeline pagination.
429	rate_limit_exceeded	Wait for Retry-After, then retry.
429	quota_exceeded	Resume after the monthly reset; do not keep retrying.
503	service_unavailable	Retry with bounded exponential backoff and jitter.

Allowance headers

X-Quota-Limit, X-Quota-Remaining, and X-Quota-Reset describe the monthly allowance. X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset describe the UTC minute window. Reset values are ISO timestamps. Retry-After is a number of seconds.

X-Request-Id appears on developer responses. Include it when reporting a failed request; find accepted data requests in your dashboard. Allowance headers may be absent before account authentication succeeds.

What counts

Successful data requests count once, including empty results, HEAD requests, and each pagination page. Failed requests and /v1/me do not consume monthly allowance. In-flight requests reserve capacity, so remaining allowance can temporarily be below 500 minus completed requests. Retries after an uncertain network failure can count again if both requests succeeded.

Accounts receive 500 requests each UTC calendar month and 60 per fixed UTC minute. Network abuse limits also apply. There is no rollover or automatic overage charge. The API console shares your allowance.