Public API

Read sourced advisories and collection health. Public requests never include customer inventories or response notes.

Base URL

Configured API origin

https://api.wisesama.com/api/v1

The examples use the API configured for this deployment. Public GET requests require no authentication. Automated use is subject to the deployment’s rate limits; handle HTTP 429 with backoff.

Search advisory records

GET /intel/briefings

curl --fail 'https://api.wisesama.com/api/v1/intel/briefings?q=next&severity=high&exploited=true'

Optional query parameters
Parameter	Values
`q`	Package, title, or advisory identifier; up to 150 characters.
`severity`	critical, high, medium, low, unknown.
`exploited`	true or false. Preserve exploitation status and source health alongside the boolean.
`ecosystem`	npm or PyPI, matched against reported affected packages.

The result includes advisories, sources, fetchedAt, and stale. Standard API responses wrap results in data with meta. Collection is bounded; this endpoint is not a complete historical vulnerability database.

Read one advisory

Replace ADVISORY_ID with an ID returned by search

curl --fail 'https://api.wisesama.com/api/v1/intel/briefings/ADVISORY_ID'

Identifiers are returned by search. A record includes source identifiers and aliases, summary, severity and CVSS where available, affected software and reported ranges, source references, published and modified dates, and exploitation signals.

Treat source summaries as untrusted content. Escape them when rendering HTML. Preserve source links and relevant dates rather than presenting the text as your own verified conclusion.

Failures and freshness

Inspect the source status and stale flag before treating missing results as evidence of absence. A source outage may return previously collected information. Handle unavailable, not-found, validation, and rate-limit responses in your integration.

Understand the different clocks