/cisa/advisories

POST /api/cisa/advisories

Price: 5 credits

Get a CISA cybersecurity advisory, alert or malware analysis report by alert code or URL

How to use it

Use this to read the body of a joint CISA advisory (AA…), a malware analysis report (AR…) or a dated alert, including the ATT&CK technique and tactic ids and the CVEs named anywhere in it. Advisories and reports resolve from their alert code alone; alerts have no code, so pass either the id the search returned for them or their cisa.gov URL — both resolve.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• advisory string required — Alert code of a cybersecurity advisory or malware analysis report, the id this platform returns for an alert, or the cisa.gov page URL of any of them (examples: "aa26-237a", "AR26-113A", "alerts/2026/09/02/cisa-adds-seven-known-exploited-vulnerabilities-catalog", "https://www.cisa.gov/news-events/cybersecurity-advisories/aa26-231a"; minLength: 1)

Response

• @type string (default: "CisaAdvisory")
• id string required
• name string nullable
• web_url string nullable
• advisory_type string nullable
• release_date string nullable
• updated_date string nullable
• description string nullable
• text string nullable
• cve_ids array (default: [])
• attack_technique_ids array (default: [])
• attack_tactic_ids array (default: [])
• tags array (default: [])
  • @type string (default: "CisaAdvisoryTag")
  • name string required
  • values array (default: [])
• related_advisory_ids array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — CISA publishes no advisory at that alert code or URL. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.