Ask to excuse one trace ID in one code repo. It never goes in the doc's sidecar.
const url = 'https://example.com/api/v1/docs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/verification-waivers';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"trace_id":"example","repo":"example","reason":"example","run_id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/api/v1/docs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/verification-waivers \ --header 'Content-Type: application/json' \ --data '{ "trace_id": "example", "repo": "example", "reason": "example", "run_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" }'Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”The ID of one spec doc.
Request Bodyrequired
Section titled “Request Bodyrequired”object
The code repo, or the folder, this excuse applies to.
The verification run the request comes from, in the same repo. The inbox link to the request opens it.
Examplegenerated
{ "trace_id": "example", "repo": "example", "reason": "example", "run_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"}Responses
Section titled “ Responses ”The waiver.
object
Withdrawn is an approved Acknowledgement that a person took out of the sidecar.
The waiver policy (§9.1).
The approvals the policy needs.
Whether the caller can approve or reject it now.
Why the waiver is rejected. Only a rejected waiver has one.
The byte range of the waiver’s section in the current main doc. Absent when the section is gone.
object
An Acknowledgement of one upstream trace ID. On approval it goes in the sidecar under trace.
object
One conflict between a doc and a linked doc, as a coherence.contradiction finding names it. A waiver of that check binds to it, and excuses no other conflict in the section. On a coherence.downstream-request finding, it is the conflict as the downstream doc names it.
object
The slug of the linked doc.
The text of this doc that conflicts.
The text of the linked doc that it conflicts with.
What a verification waiver excuses. It never goes in the sidecar.
object
The code repo, or the folder, as the verification run names it.
The verification run the request came from. Empty for a request that named no run.
True for a standalone Acknowledgement. On approval it goes in the sidecar under standalone.
True for an upstream request, the answer “The linked doc must change”. On approval it goes in the sidecar under upstream_changes.
True for a send-back, the answer “The downstream doc must change” to a coherence.downstream-request finding.
True for the answer “Not needed” to one finding. The author gives it, and it needs no approval.
For a send-back, or a waiver of a coherence.downstream-request finding: the downstream doc. The approval writes to its sidecar, because Speccy writes nothing into the linked doc’s sidecar.
object
The bundle that holds the spec doc.
Who withdrew the Acknowledgement. Only a withdrawn one has it.
Why an ended waiver ended: an edit changed its section, a full review passed its whole-doc check, or the profile changed what the check asks. An upstream request ends when the linked doc sends it back, or when an edit removes a quote of its conflict.
True for a waiver of a whole-doc check. An edit does not end it. It ends when a full review passes the check, or when the profile changes what the check asks.
Example
{ "status": "requested", "trace": { "status": "out_of_scope" }, "ended_because": "section_changed"}default
Section titled “default”An error.
RFC 9457 problem details with a stable code.
object
A stable machine-readable error code.
Examplegenerated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example", "code": "example"}