Errors & rate limits

This page covers the Aepto Platform API (your integration calling Aepto). Monitoring someone else's API quotas is a product feature: Docs -> API Rate Limits.

Errors

401 - missing/invalid Bearer token
403 - authenticated but scope or plan does not allow the action
404 - resource not found or not in the account
422 / 400 - validation problems (check error / field messages)
429 - you exceeded Platform API rate limits; back off and retry
5xx - transient server issues; retry with jitter

Rate limits

Limits apply per key/token. When you receive 429, slow down; honor any Retry-After header if present. Do not confuse these with the in-app API Rate Limits product that watches third-party vendor quotas.

Public tech-stack peek

Unauthenticated tech-stack peeks are separately capped (per IP/domain) and may return 503 when the platform is shedding load - Connect or an API key is the reliable path for production traffic.

FAQ

Is this the same as in-app API Rate Limits?

No. This page is about your calls to Aepto’s Platform API. Watching Stripe/HubSpot/GitHub quotas is the product feature API Rate Limits.

What does 401 vs 403 mean?

401 — missing or invalid Bearer token. 403 — authenticated, but scope or plan does not allow the action.

What should I do on 429?

Back off and retry. Honor Retry-After if present. Limits apply per key/token.

Why might public tech-stack peek return 503?

Unauthenticated peeks are separately capped and may shed load. For production traffic, use Connect or an API key.