Skip to Content
Pyxis Docs

Ingest API

Endpoints, authentication, limits and error codes for sending data to Pyxis.

All ingest endpoints take Authorization: Bearer pyx_live_<id>.<secret> and require the key to have the ingest scope.

Method and pathPurpose
POST /v1/metricsOTLP/HTTP JSON metrics
POST /v1/wallet-events (and OPTIONS)Wallet funnel events; CORS allows any origin
POST /v1/traces, POST /v1/logsAlways 404 signal_not_supported

POST /v1/metrics

Authentication happens before the body is read, and the response is sent only after the database commit.

AspectRuleReason code when violated
Metrichttp.server.request.duration or http.server.durationmetric_not_allowed
TypeHistogramwrong_metric_type
TemporalityDelta onlycumulative_temporality_unsupported
Units, ms, us, ns or empty (treated as ms)unsupported_unit
ServiceResource attribute service.namemissing_service_name
Statushttp.response.status_code, 100 to 599invalid_status_code
TimeNot older than 24 h, not more than 5 min in the futuretimestamp_too_old, timestamp_in_future
Histogram shapebucketCounts length equals explicitBounds length plus 1, counts non-negativemalformed_histogram
Service quota10 (service, environment) pairs per projectservice_quota_exceeded
Route cardinality200 routes per service over 7 days; extras fold into /_otherroute_cardinality_capped

Body limit is 1,000,000 bytes and 5,000 data points. A 200 can still carry a partialSuccess with dropped points.

Source histograms are re-bucketed onto fixed upper bounds in milliseconds, assigned by their upper bound so latency is never under-reported: 5, 10, 25, 50, 100, 250, 500, 1000, 2500, 5000, 10000 and +Inf.

POST /v1/wallet-events

See Wallet events.

Errors

Errors have one shape: { "code": "<machine_code>", "message": "<generic text>" }.

CodeMeaning
auth_malformed, auth_unknown, auth_bad_secretThe key is missing, unknown or wrong
auth_revoked, auth_expiredThe key was revoked or has expired
auth_project_inactiveThe project is suspended or archived
auth_scopeThe key lacks the ingest scope
payload_too_largeBody over the limit
invalid_json, unsupported_content_typeBody is not JSON
too_many_data_pointsMore than 5,000 data points
signal_not_supportedYou sent traces or logs

No rate limiting yet

The ingest endpoints are limited only by size caps. Per-key and per-IP rate limits are not implemented. See Security.

On this page