Accept a pending proposal (a person; member for VEX and unit links, admin for a mapping)
const url = 'https://example.com/v1/orgs/example/proposals/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/accept';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"payload":{},"decision_note":"example"}'};
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/v1/orgs/example/proposals/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/accept \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "payload": {}, "decision_note": "example" }'Writes the statement (author: the deciding user), the mapping, or the release alias with the units that report its text linked, pointing back to the proposal, in the same transaction. The body is optional: payload replaces the proposal’s payload in the record (validated as on filing; a VEX edit keeps the vulnerability, a unit link edit its reported text, proposal.reportedChanged, and may name another release), while the proposal keeps the original; decision_note defaults to “Edited by the reviewer before accepting.” for an edit. With four eyes on, a user can’t decide a proposal filed with their own credentials (proposal.ownProposal) nor one from an API key they created (proposal.fourEyes).
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
Request Body
Section titled “Request Body”object
The edited statement, mapping or UnitLinkPayload
object
Example generated
{ "payload": {}, "decision_note": "example"}Responses
Section titled “Responses”Accepted
object
Unit_release_link: units that report a version text run a release; accepted, it is a release alias
As filed; an edited accept leaves it unchanged
object
object
object
Node ID
An ontology relation
Node ID
As the data has them; what a client sends is ignored
object
Read tools the agent ran, by name, e.g. explain_finding, neighbours
Plain text; never render it as HTML or Markdown
Carry_over: a statement on another release with an exact path signature match; analysis: the agent’s own argument
Key:
The client’s name (OAuth client or API key name), for display only
User ID
The statement, mapping or release alias written on accept
Example
{ "kind": "vex_statement", "basis": "carry_over", "status": "pending"}An invalid edited payload
Role too low for the kind, an API key, the caller’s own proposal, or four eyes
No such object in this organization, no such organization, or the caller does not belong to it
Not pending (proposal.notPending), a carry-over whose statement is no longer current (proposal.sourceSuperseded), the mapping exists already, or the text has an alias since (alias.exists)
Over the operation’s rate-limit budget (x-affectra-budget): code request.rateLimited with params.budget. Wait Retry-After seconds before trying again.
Every error answer, Content-Type
application/problem+json. The web app and integrations translate code; detail is English,
for people reading curl output or CI logs, and may change wording at
any time. Match on code, never on detail.
object
The HTTP status
Stable error codes. A code is never renamed; new ones may be added, so
a client falls back to detail for a code it doesn’t know. Another
organization’s object answers notFound, the same as a missing one.
What went wrong
Values the code’s message needs, e.g. {“field”: “version”}. Only values the caller sent or may see. Empty when the message needs none.
object
Example
{ "code": "notFound"}Headers
Section titled “Headers”Seconds until a request would be allowed again, at least 1
The server runs without a database or object storage; the catalog is unavailable