HTTP errors and troubleshooting

Inspect both the HTTP status and the JSON response body. Errors generally include detail; validation errors may include a list of field problems.

Status	Meaning	What to check
200–299	The operation succeeded	Read the response body and timestamps
400	The request cannot be processed	JSON syntax and request shape
401	Authentication failed	Authorization header, expiry and revocation
403	Access denied	Required scope, account plan and human-only restrictions
404	Resource not found	Path, symbol or identifier
409	Conflict with existing data	Names or other uniqueness constraints
422	Input validation failed	Field names, types, dates and required parameters
429	Request limit reached	Wait for Retry-After before trying again
500–599	Service or upstream failure	Retry reads with bounded exponential backoff

Inspect recent activity

The authenticated API console shows thirty days of request volume by HTTP status and the latest hundred requests. Only activity attributable to a resolved personal token is included. An invalid or expired credential cannot be attributed to an owner.

The register retains the operation’s route template, method, HTTP status and time to response headers. Credentials, query values and request or response bodies are not retained in this register.

Retrying safely

Use a timeout. Retry transient read failures with bounded backoff and jitter, and honor Retry-After. A timed-out write might already have succeeded: check the resource before repeating it.