Every product with its variants and their newest releases
const url = 'https://example.com/v1/orgs/example/catalog/overview?releases=6';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/catalog/overview?releases=6' \ --header 'Authorization: Bearer <token>'Products by name, each with its variants by name. A variant lists its newest releases releases,
newest version first (see ProductReleasePage for the order), each with its finding groups counted as
in /exposure/summary; release_count is all of its releases, and older_open and older_open_kev
count the releases left out that have an open finding group, and an open known-exploited one.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
Query Parameters
Section titled “Query Parameters”Releases per variant
Responses
Section titled “Responses”Overview
object
By name
object
The product key firmware reports as PRODUCT=
Last day of security updates; null when not set
By name
object
All of the variant’s releases
The newest, newest version first
A release with its variant and its finding groups, counted as in ReleaseExposure
object
The variant’s name
SBOMs signed by a trusted publisher
CVEs (finding groups) in this release not resolved by VEX
Open known-exploited CVEs (finding groups)
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
Releases not in releases with an open finding group
Releases not in releases with an open known-exploited finding group
Example generated
{ "products": [ { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "name": "example", "description": "example", "key": "example", "support_ends": "2026-04-15", "created_at": "2026-04-15T12:00:00Z", "variants": [ { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "product_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "name": "example", "created_at": "2026-04-15T12:00:00Z", "release_count": 1, "releases": [ { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "variant_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "variant": "example", "version": "example", "released_at": "2026-04-15T12:00:00Z", "created_at": "2026-04-15T12:00:00Z", "sboms": 1, "verified_sboms": 1, "open": 1, "open_kev": 1, "open_affected": 1, "resolved": 1 } ], "older_open": 1, "older_open_kev": 1 } ] } ]}Request.invalid (params.field releases)
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