Change a manual mark
const url = 'https://beta-api.plune.ai/v1/results/example';const options = { method: 'PATCH', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"status":"passed","errorContext":null,"steps":[{"index":0,"status":"passed"},{"index":1,"status":"passed"},{"index":2,"status":"passed"}]}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PATCH \ --url https://beta-api.plune.ai/v1/results/example \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "status": "passed", "errorContext": null, "steps": [ { "index": 0, "status": "passed" }, { "index": 1, "status": "passed" }, { "index": 2, "status": "passed" } ] }'The «To run» section of the run page (D34, api.ts → patchResult): a person who marked a case changes the mark — its status, its message, its steps — in place, while the run is open. Only a result with source: manual answers: a reporter’s result is evidence, and a run of 40 cases must not count 41 because one mark was corrected. Audited under the run. A patch never sets or changes failure; the message is sanitized like a submission’s. The sub-status (#1231) is set here too, after the status — the status button is the submit, and the sub-status follows it in a request of its own.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Request Body required
Section titled “Request Body required ”At least one key. Only a result with source: manual in an open run takes a patch — a reporter’s result is evidence and stands (404), and a closed run keeps its marks (409). outcome is recomputed from the new status.
object
null clears the message; redacted and truncated like a submission’s.
object
The step’s position in the case’s steps, from 0.
One of the sub-statuses the result’s status offers now — the built-ins, then the project’s own (GET /v1/settings/sub-statuses); any other is a 400 that names them. null clears it. A new status without one drops the old sub-status, which belonged to the old status.
The ids of files added to the case while the mark was being changed (#1234, POST /v1/runs/{id}/cases/{caseId}/files): they join the files the result already has. Only finished files of this run and this case are taken; any other id is passed over.
Example
{ "status": "passed", "errorContext": null, "steps": [ { "index": 0, "status": "passed" }, { "index": 1, "status": "passed" }, { "index": 2, "status": "passed" } ]}Responses
Section titled “ Responses ”The result as it is now
One stored result, as every reader returns it — a run’s results, a test’s history, a corrected mark.
object
The key the reporter sent (a person’s mark: manual:<caseId>). A result a retest replaced (#1767) keeps it with #retest:<id> appended, in its history.
The number of the result’s combination in its run’s combinations (#1251, ADR 0070). Absent for a result of a run without configurations.
What happened, as it happened — a muted case’s failure is still failed here, and ?status=failed finds it.
Whether the case was muted when this result counted (#1247): stamped from the case when the result is written (a reporter, plune sync, a Cairn ingest), and following the case while the run is open. A failed or broken result of a muted case is counted as muted, not as a failure; a finished run never changes (#1247).
The sub-status a person marked it with (#1231) — the NAME as it stood then: renaming or removing it under Settings → Statuses changes what is offered next, never this. A built-in is its English name (Product bug); the dashboard shows it in its own language. null for none — every reporter’s result, which never carries one.
Returned sanitized — no colour codes, no credentials — whether it was stored before the rules existed or after.
What the platform removed before storing — written whenever something was, even without text; null when nothing ever was.
object
Values replaced by a marker, in the text and in every string of failure, each once. The headline counts only when there is no text — otherwise it repeats a line of it.
Whether the TEXT was cut to 256 KB. A shortened field of failure carries its own ….
Characters the REPORTER cut before sending, as it declared in errorContextOmitted; absent when it said nothing. Not the platform’s cut (truncated).
What the reporter said about the failed attempt, or null.
object
How many steps between the outer and the inner ones were left out. Absent when none were.
object
From the repository root in posix form, the way a case’s specRef names it. A path of the machine is refused: absolute, with a drive or a scheme, from a home (~), or climbing out with ...
object
As the runner named it — screenshot, trace, error-context.
How many artifacts past the listed ones there are — all reachable through ciUrl.
The link to the result’s trace as the reporter or plune sync sent it (#2981) - absent when none was sent. Plune does not check that it opens.
The defect links on this result (#1064), oldest first - present on a run’s results list, and only when there is one. A result carries them only if it failed or broke.
A defect (#1064): the address of a ticket somebody already filed, kept beside a case or a failed result. https only, at most 2000 characters; the label is plain text, at most 200, and is shown as text, never as markup. The author is a userId; the dashboard names them from GET /v1/members. No type: Bugs (#1065) will read the same links as external tickets.
object
Where the result’s case sits in the tree (#1232) — the suites from the root down to its own; a suite filed from a spec stands for the folders above it by its file (["e2e/cart.spec.ts", "Coupons"]). Empty for a case at the root. On a run’s results list, always.
The title of the result’s case (#1705), so a page can name its rows without reading the project’s case list. On a run’s results list; kept after the case is deleted, like the rest of the evidence.
Files uploaded to this result — screenshots, text (JSON, plain text, logs) and, for a project with a bucket, any file — oldest first (ADR 0040, ADR 0041) — present on a run’s results list, and only when there is one. Only finished files: one still waiting for complete is not listed. For storage: db the bytes are GET /v1/files/{id}.
A file of a result, everything but its bytes (ADR 0040, ADR 0041). Only a finished file is ever shown: one that was announced with uploads and not yet completed is in no list.
object
The last segment of the name it was uploaded with, cleaned of credentials as a text is.
In the database (storage: db): image/png, image/jpeg, image/webp, application/json or text/plain — a log is text/plain. In the bucket (storage: bucket): the media type it was announced with, lower case and without parameters, any type.
Bytes as kept: in the database a picture at most 2 MiB and a text at most 512 KiB, counted after its credentials are cleaned, so it can differ from what was sent; in the bucket the size that was announced and found there.
db: Plune keeps the bytes in its database, GET /v1/files/{id} returns them. bucket: they are in a bucket — the project’s own, or, for a built-in file of a server that keeps those in its own bucket (#1428), Plune’s — and GET /v1/files/{id} answers 409 in_bucket (the way to read them is GET /v1/files/{id}/link). A built-in file in Plune’s bucket counts toward the budget as one in the database does.
#1444: the files of this result the built-in storage sent away to make room (ADR 0040) - their name, type, size and when, oldest first; the bytes are gone. On a run’s results list, and only when there is one.
object
Example
{ "id": "6f1c2b3a-0000-4000-8000-0000000000e1", "runId": "6f1c2b3a-0000-4000-8000-0000000000d1", "testCaseId": "6f1c2b3a-0000-4000-8000-0000000000c1", "resultKey": "manual:6f1c2b3a-0000-4000-8000-0000000000c1", "signature": "7f974c61f8f10065cd8ae6993cc069e4f85b1db1ed008b965885fb6f945a28c9", "status": "passed", "rawStatus": null, "source": "manual", "expectedStatus": "passed", "outcome": "expected", "execution": null, "durationMs": null, "caseVersion": 1, "muted": false, "errorContext": null, "errorContextMeta": null, "assertions": [], "steps": [ { "index": 0, "status": "passed" }, { "index": 1, "status": "passed" }, { "index": 2, "status": "passed" } ], "failure": null, "executedBy": null, "subStatus": null, "createdAt": "2026-09-16T09:12:04.151Z"}Invalid body, nothing to change, or a sub-status the status does not offer — the message names the ones it does
object
Example
{ "error": "'Nope' is not a sub-status of failed — it has Product bug, Environment issue"}No / invalid token or session
No such manual result in your projects — a reporter’s result reads as not found
object
Example generated
{ "error": "example"}The run is closed
object
Example
{ "error": "the run is closed — its results stand"}Rate-limited: the per-route throttle, or the per-minute request limit of the plan an API token counts by (#1442; the body names the plan, #2092). Retry-After carries the seconds until the window rolls over.
object
Example generated
{ "error": "example"}Headers
Section titled “Headers ”Seconds until the window rolls over