The organization's events, oldest first
const url = 'https://example.com/v1/orgs/example/events?limit=50';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/events?limit=50' \ --header 'Authorization: Bearer <token>'What changed: finding.new, finding.known_exploited, finding.resolved, release.matched, proposal.filed and org.feed_subscription_changed of the last 30 days, oldest first, each as webhooks get it (the same JSON, byte for byte). For agents and scripts that poll: keep next and send it as after on the next request to get only what came since; while more is true, ask again right away. An event appears once every database transaction older than it has ended, so a poll never skips one. The MCP tool list_events reads the same feed.
Reading the feed marks the organization as listening for 30 days (at most one write an hour), so Affectra produces finding events for it even without webhooks or email.
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”The next of the previous answer. Leave it out to start at the oldest event. A cursor that doesn’t parse, or one older than 30 days, answers events.cursorInvalid; start again without it.
Only these types; repeat the parameter for several.
Responses
Section titled “Responses”A page
object
Oldest first. Each is the event JSON webhooks get (id, type, occurred_at, org, data); see the webhooks guide for each type’s data. Finding events (finding.new, finding.known_exploited, finding.resolved) are one per finding group, a CVE in a release: data.vulnerability is the advisory the event is about, and data.group is FindingEventGroup.
object
The cursor to send as after on the next request; opaque
More events are waiting after next
Example generated
{ "events": [ {} ], "next": "example", "more": true}Events.cursorInvalid, or request.invalid (params.field type or limit)
Auth.roleTooLow
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
Notifications.unavailable