Make a VEX statement (member; member API keys may)
const url = 'https://example.com/v1/orgs/example/releases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/vex';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"vulnerability":"example","status":"not_affected","justification":"component_not_present","impact_statement":"example","action_statement":"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/releases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/vex \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "vulnerability": "example", "status": "not_affected", "justification": "component_not_present", "impact_statement": "example", "action_statement": "example" }'Statements are append-only: a new one for the same vulnerability replaces the current one, and the old one stays in the history. A statement on an advisory decides for it; statements on CVEs decide for every advisory that carries them (any affected keeps it open; all CVEs assessed resolves it). OpenVEX rules apply: not_affected needs a justification or an impact statement, affected needs an action statement, only not_affected takes a justification.
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
CVE, advisory or GHSA ID, e.g. “CVE-2023-0286”, “DSA-5343-1”
Responses
Section titled “Responses”Recorded
object
User ID
The agent proposal whose acceptance wrote the statement
Example
{ "status": "not_affected", "justification": "component_not_present"}Breaks a rule above; the message says which
Role below member
No such object in this organization, no such organization, or the caller does not belong to it
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