Skip to main content
This page consolidates every customer-visible limit and the exact behavior when you hit it.

​
Ingestion API

There are currently no rate limits on the Ingestion API; it does not return 429. Transient overload surfaces as 503 with "retryable": true — retry with backoff. See Reliability. Error envelope on JSON endpoints:
Unknown paths return a plain-text 404. An optional X-Request-ID header (UUID) is echoed back as requestId for correlating requests with responses.

​
Environments

Accepted environment values: development, staging, production.
  • The request-level environment field on /v1/ingest and /v1/ingest/multi must be exactly one of the three values; anything else returns 400 listing the valid values. It defaults to production.
  • Environment values carried on OTLP attributes (moda.environment span attribute, deployment.environment resource attribute) normalize common aliases — dev/develop → development, stg/stage → staging, prod → production — and unknown values fall back to production.

​
Data API

Out-of-range numeric parameters are clamped to their maximum — they do not error. Invalid enum values and over-length strings return 400. Per-endpoint limit caps:

​
Dashboard and CLI

CLI key limit. Each workspace caps the number of active CLI-created keys (named CLI - ...). The default is 10; admins and owners can set it between 1 and 100 in Settings → Ingestion keys.

​
Harness

​
Next steps