Finding groups per release and in total
const url = 'https://example.com/v1/orgs/example/exposure/summary';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/v1/orgs/example/exposure/summary \ --header 'Authorization: Bearer <token>'A finding group is one CVE (or one advisory without a CVE) in one release, however many advisories and components bring it in. open, open_kev and resolved count each CVE once: per release in by_release, and org-wide in the totals, where a CVE on several releases counts once (open when it is open on any release, resolved when it is resolved on all of them). open_releases is the number of releases with an open group.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
Responses
Section titled “Responses”Summary
object
Distinct CVEs (finding groups) open on any release: one CVE on five releases counts once, so this is not the sum of by_release
Distinct open known-exploited CVEs, counted once org-wide
Distinct open CVEs that are affected on every release where they are open, counted once org-wide
Distinct CVEs resolved by VEX on every release that has them, counted once org-wide
Releases with at least one open finding group
Most exposed first: releases of products still supported (or with no support end) before those past it (support_ended), then by open known-exploited, then open and still to assess, then open
object
The product’s last day of security updates (Product.support_ends); null when not set
True once support_ends has passed. Such releases are listed after all supported ones; their findings still count
SBOMs signed by a trusted publisher
CVEs (finding groups) in this release not resolved by VEX, each counted once however many advisories name it
Open known-exploited CVEs (finding groups): in CISA KEV, or on ENISA’s list from a source other than CISA
Open CVEs (finding groups) with an affected VEX statement; open minus open_affected is still to assess
CVEs (finding groups) VEX marked not_affected or fixed
Example generated
{ "releases": 1, "sboms": 1, "open": 1, "open_kev": 1, "open_affected": 1, "resolved": 1, "open_releases": 1, "by_release": [ { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "product": "example", "variant": "example", "version": "example", "support_ends": "2026-04-15", "support_ended": true, "sboms": 1, "verified_sboms": 1, "open": 1, "open_kev": 1, "open_affected": 1, "resolved": 1 } ]}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
The server runs without a database or object storage; the catalog is unavailable