Documentation/Batch and pagination

Batch and pagination

Use batch endpoints when you already have a CVE list. Use filtered list endpoints when you are exploring the corpus.

Batch lookups

POST /api/v1/cve/batch accepts up to 1000 CVE IDs. It returns found records and a separate not_found_cves list.

See API Reference: POST /api/v1/cve/batch.

Prioritization batches

POST /api/v1/prioritize accepts a CVE list and returns a ranked order. This is the best endpoint for scanner output, SBOM findings, and backlog triage.

See API Reference: POST /api/v1/prioritize.

Pagination

For CWE searches, use limit and offset style pagination where available. Keep pages small enough that a retry is cheap.

Operational tips

  • De-duplicate CVEs before sending them.
  • Keep the original scanner finding ID in your own system and join on cve_id.
  • Treat partial success as normal for newly assigned CVEs.
  • Cache stable enrichment results and refresh based on /api/v1/status freshness.