Turn a vulnerability feed on or off for the organization (admin)
const url = 'https://example.com/v1/orgs/example/feeds/example';const options = { method: 'PUT', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"subscribed":true}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PUT \ --url https://example.com/v1/orgs/example/feeds/example \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "subscribed": true }'Turning a feed off hides the findings only it reports from lists, counts, exports, the graph and MCP for this organization; nothing is deleted, and they come back when it is turned on again. It sends no finding.resolved, and turning it back on sends no finding.new for findings that were there before. Each change writes an org.feed_subscription_changed event; asking for the state the feed is already in changes nothing and writes no event. The answer is the feed as GET lists it.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
The feed’s key: nvd or csaf:
Request Bodyrequired
Section titled “Request Bodyrequired”object
False turns the feed off for the organization; true turns it on again
Example generated
{ "subscribed": true}Responses
Section titled “Responses”The feed
object
Osv, nvd, csaf:
How the feed is shown, e.g. NVD, Siemens ProductCERT
Matching feeds create findings (OSV, NVD, CSAF); enrichment feeds add context to them
The organization can turn it on or off (NVD and the CSAF providers)
Its findings count for the organization; always true for a feed that isn’t subscribable
Whether it is on for an organization that never chose
A CSAF provider: a vendor’s own advisories or a coordinator’s; null for the other feeds
Last successful check; null when never checked or not synced here
When the organization last turned it on or off; null if it never did
Who did: the user’s ID, or api-key; null if nobody did
Example
{ "kind": "matching", "publisher": "vendor", "state": "ok"}Feeds.notSubscribable (params.feed: OSV and the enrichment feeds are always on), request.fieldRequired (params.field subscribed), or request.invalidJson
Caller is not an admin
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