Accept pending carry-over VEX proposals, all or none (member, a person)
const url = 'https://example.com/v1/orgs/example/proposals/accept';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"ids":["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/v1/orgs/example/proposals/accept \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "ids": [ "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" ] }'Up to 200 IDs. Every one must be a pending carry_over vex_statement the caller may decide; otherwise nothing is accepted and the problem names the offending proposal (params.proposal).
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
Request Bodyrequired
Section titled “Request Bodyrequired”object
Example generated
{ "ids": [ "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" ]}Responses
Section titled “Responses”Accepted
object
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
{ "proposals": [ { "kind": "vex_statement", "basis": "carry_over", "status": "pending" } ]}No IDs, too many, or one is not a carry-over (proposal.notCarryOver)
Role below member, an API key, or the caller’s own proposal
No such object in this organization, no such organization, or the caller does not belong to it
One is no longer pending (proposal.notPending), or carries over a statement that is no longer current (proposal.sourceSuperseded)
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