Documentation

Report external checks

Send CI or agent results to the exact Change Request version they evaluated.

An external CI system or agent can report a check against a Change Request version.

Authentication

Create a workspace API token with only the upstream.checks.write scope and send it as a bearer token.

Request

POST https://coline.app/api/v1/upstream/checks
Authorization: Bearer <token>
Content-Type: application/json

{
  "repositoryId": "repository-id",
  "changeRequestNumber": 42,
  "versionNumber": 3,
  "checkKey": "ci/build-and-test",
  "displayName": "Build and test",
  "status": "running",
  "summary": "Running 184 checks",
  "detailsUrl": "https://ci.example/runs/981",
  "logsUrl": "https://ci.example/runs/981/logs",
  "externalId": "981"
}

Accepted statuses are pending, running, passed, failed, skipped, and error.

Send later states with the same repository, Change Request version, and check key. Upstream updates the same check identity so required-check gating and history remain consistent.

Always include versionNumber. Omitting it uses the current version, which is unsafe if the proposed code can change while your job is running.