Send lab results

jq -n --arg sha "$COMMIT_SHA" --arg ref "$BRANCH" --rawfile junit junit.xml \
  '{commitSha: $sha, gitRef: $ref, rootDir: ".",
    context: {cameraModel: "CD62", firmwareVersion: "v2026.10.27.2"},
    junit: $junit}' > lab-results.json

curl --fail-with-body -sS -X POST --data-binary @lab-results.json \
  -H "Authorization: Bearer $PEEPS_API_KEY" \
  -H "Content-Type: application/json" \
  "https://app.peepsai.com/api/v1/projects/LAB/ci-results"

{
  "batchNumber": 42,
  "filed": 18,
  "unmatched": [
    { "path": "tests/device/test_new_mode.py", "titlePath": "test_night_mode" }
  ]
}

{
  "batchNumber": 43,
  "filed": 1,
  "unmatched": [],
  "verification": { "pullRequest": 128, "state": "ready_for_review" }
}

{
  "error": {
    "code": "unknown_commit",
    "message": "0f1e2d3c4b5a69788796a5b4c3d2e1f00f1e2d3c is not a commit on main in acme/camera-tests. Send the full 40-character commit the tests were built from."
  }
}

Sends one lab run of a pytest suite that never runs in your CI, such as device tests on lab hardware. Peeps files it as a CI run of the project’s repository, at the commit and branch you send, and analyzes its failures. An upload of a fix’s peeps/… branch can also settle that fix’s pull request. For the setup and an example workflow, see Send results from your lab. The project must be backed by a repository, and the key must name it under Only these projects. A key for all web projects can’t send lab results, and gets 404. Sending again files a second batch: Peeps doesn’t recognize a resend. Lab runs count toward the same minute limits as report files. See Rate limits.

Errors

Besides 401, 429, 503 and 500 from the errors table, sending lab results can return:

Status	Code	When	What to do
`400`	`invalid_request`	`Content-Length` isn’t a number, the body is empty or isn’t the size `Content-Length` says, the body isn’t JSON, or a field is missing or invalid. The message names the field.	Fix the request and send it again.
`404`	`not_found_or_no_access`	No project has that acronym or ID in your organization, or the key doesn’t name it under Only these projects.	Check the project and the key’s projects.
`408`	`body_timeout`	The body didn’t arrive within 120 seconds.	Send it again.
`411`	`length_required`	The request has no `Content-Length` header.	Send the body with its size, as `curl --data-binary` does.
`413`	`too_large`	The body is over 50 MiB.	Send a smaller report.
`413`	`too_many_tests`	The JUnit reports more than 2,000 tests.	Split the run into several uploads.
`422`	`platform_not_supported`	The project isn’t backed by a repository.	Send lab results to a project backed by a repository, or send a report file instead.
`422`	`not_connected`	The project is no longer connected to a repository.	Connect the repository again.
`422`	`branch_not_followed`	Peeps doesn’t follow `gitRef`, or it’s a fix’s branch and `commitSha` isn’t the commit Peeps pushed there. The message names the branches or the commit to send.	Send results for the headline branch or a tracked branch, or for the fix’s commit.
`422`	`unknown_commit`	`commitSha` isn’t a commit on `gitRef`.	Send the full 40-character commit the tests were built from.
`422`	`malformed_report`	Peeps couldn’t read `junit` as a JUnit report.	Send the XML that pytest’s `--junitxml` option wrote.
`422`	`test_not_reported`	`gitRef` is a fix’s branch, and the JUnit doesn’t report the test the fix is for. Nothing is filed.	Run that test. If pytest’s rootdir isn’t the repository root, send it as `rootDir`.

jq -n --arg sha "$COMMIT_SHA" --arg ref "$BRANCH" --rawfile junit junit.xml \
  '{commitSha: $sha, gitRef: $ref, rootDir: ".",
    context: {cameraModel: "CD62", firmwareVersion: "v2026.10.27.2"},
    junit: $junit}' > lab-results.json

curl --fail-with-body -sS -X POST --data-binary @lab-results.json \
  -H "Authorization: Bearer $PEEPS_API_KEY" \
  -H "Content-Type: application/json" \
  "https://app.peepsai.com/api/v1/projects/LAB/ci-results"

{
  "batchNumber": 42,
  "filed": 18,
  "unmatched": [
    { "path": "tests/device/test_new_mode.py", "titlePath": "test_night_mode" }
  ]
}

{
  "batchNumber": 43,
  "filed": 1,
  "unmatched": [],
  "verification": { "pullRequest": 128, "state": "ready_for_review" }
}

{
  "error": {
    "code": "unknown_commit",
    "message": "0f1e2d3c4b5a69788796a5b4c3d2e1f00f1e2d3c is not a commit on main in acme/camera-tests. Send the full 40-character commit the tests were built from."
  }
}

Authorizations

Authorization

string

header

required

Bearer followed by your API key.

Path Parameters

project

string

required

The project's acronym, in any case, such as LAB, or its ID. The project must be backed by a repository, and the key must name it under Only these projects.

Body

application/json

The lab run as JSON, up to 50 MiB. Send its size in bytes as Content-Length; curl --data-binary @file sends it for you. The whole body must arrive within 120 seconds.

commitSha

string

required

The full 40-character commit the tests were built from. It must be on gitRef: its latest commit or an earlier one.

Pattern: ^[0-9a-fA-F]{40}$

gitRef

string

required

The branch the commit is on: the headline branch, a branch listed under Tracked branches, or the peeps/… branch of a fix waiting for the lab, at the commit Peeps pushed.

Required string length: 1 - 200

junit

string

required

The JUnit XML that pytest's --junitxml option wrote, as text.

Minimum string length: 1

rootDir

string

default:.

pytest's rootdir, relative to the repository root, with no . or .. segment. Leave it out, or send ., when pytest runs from the repository root.

Maximum string length: 500

jobUrl

string<uri> | null

A link to the lab run. Peeps shows it as Lab run: in the comment it leaves on a fix the upload settles.

Maximum string length: 2000

context

object

What the lab knows about the run. Peeps shows it first on each result, and names the batch after the camera model and firmware. Any other field is refused.

Show child attributes

Response

Peeps filed the run.

batchNumber

integer

The number of the batch Peeps filed the runs in.

filed

integer

How many tests Peeps filed.

unmatched

object[]

Tests in the JUnit that the project has no test case for. An upload never creates a test case, so these aren't filed.

Show child attributes

verification

object

Only for an upload of a fix's peeps/… branch: what the upload did to the fix's pull request.

Show child attributes

jq -n --arg sha "$COMMIT_SHA" --arg ref "$BRANCH" --rawfile junit junit.xml \
  '{commitSha: $sha, gitRef: $ref, rootDir: ".",
    context: {cameraModel: "CD62", firmwareVersion: "v2026.10.27.2"},
    junit: $junit}' > lab-results.json

curl --fail-with-body -sS -X POST --data-binary @lab-results.json \
  -H "Authorization: Bearer $PEEPS_API_KEY" \
  -H "Content-Type: application/json" \
  "https://app.peepsai.com/api/v1/projects/LAB/ci-results"

{
  "batchNumber": 42,
  "filed": 18,
  "unmatched": [
    { "path": "tests/device/test_new_mode.py", "titlePath": "test_night_mode" }
  ]
}

{
  "batchNumber": 43,
  "filed": 1,
  "unmatched": [],
  "verification": { "pullRequest": 128, "state": "ready_for_review" }
}

{
  "error": {
    "code": "unknown_commit",
    "message": "0f1e2d3c4b5a69788796a5b4c3d2e1f00f1e2d3c is not a commit on main in acme/camera-tests. Send the full 40-character commit the tests were built from."
  }
}

Get started

Results

API keys

Send lab results

Errors

Authorizations

Path Parameters

Body

Response

​Errors

Authorizations

Path Parameters

Body

Response

Errors