Upload one suite report onto a started conformance run
How conformance runs executed OUTSIDE the platform (local CLI, GitHub Actions) reach the Conformance history. Authenticate like any other /api/v1 route (typically an sk_ key). The {projectId} segment always wins over any projectId in the body. The literal default resolves to the key org's Default project. STATUS AND BODY PASS THROUGH VERBATIM.
One requested suite per call. Content-hash conflicts 409.
Path parameters
Project id, or the literal default for the key org's Default project.
Request body
Forwarded VERBATIM to the backend's conformance-ingestion surface, which owns the schema. The projectId path segment always wins.
Response
The backend's response, passed through.
The backend's response, passed through verbatim along with its status code. Success shapes are { ok: true, ... } envelopes the SDK reporter parses. Errors are canonical v1 { code, message }.