Upload test result file (JUnit/TestNG XML, Allure/Cypress/Playwright JSON) — POST /api/v1/ingest/file

Upload test result file (JUnit/TestNG XML, Allure/Cypress/Playwright JSON)

Upload a test result file for async parsing and ingestion.

Endpoint: POST /api/v1/ingest/file

Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.

Parameters

Name	In	Required	Type	Default	Description
X-API-Key	header	no	string or null		API key, as an alternative to the access token (see Authentication).

Request body

Content type	Body	Required
multipart/form-data	Body_ingest_file_api_v1_ingest_file_post	yes

Responses

Status	Meaning	Body
202	Successful Response	IngestResponse (application/json)
422	Validation Error	HTTPValidationError (application/json)

Errors this endpoint returns, read from its source code:

• 400
• 403, with the message “This API key is restricted to a different project”
• 422, with the message “build_number must not be empty”
• 503, with messages such as “Upload could not be queued”, “Upload storage is temporarily unavailable”

It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.

More details

• Group: Ingest
• Operation ID: ingest_file_api_v1_ingest_file_post
• Source code: backend/app/routers/ingest.py, line 287
• Specification: OpenAPI JSON