Results ingest · Updated May 14, 2026
Results ingest API overview
Understand the public results ingest contract for publishing run data from authorized engines and test infrastructure.
What results ingest is for
Results ingest receives structured run data from authorized execution paths. It is separate from the Platform API so high-volume engine output does not share the same assumptions as console workflow automation.
What to send
Ingest payloads should identify the run, preserve ordering or idempotency where required by the contract, and send useful data: metrics, logs, runner health, and engine events. Follow the live OpenAPI reference for exact fields.
Operational guidance
Treat ingest credentials as write-only run-scoped material. Do not expose them in browser code, public docs examples, or logs. Retry carefully and avoid duplicate batches unless the contract marks them idempotent.
Reference
Use the configured live Results ingest reference for exact request and response shapes.
FAQ
Is results ingest the same as the Platform API?
No. Results ingest is the data-ingestion contract used by authorized engines and infrastructure; the Platform API is for customer workflows and console automation.