Ossprey OpenAPI Overview
Start exploring the Ossprey OpenAPI spec for SBOM submission, scan status, and findings.
You can use the Ossprey OpenAPI spec to submit SBOMs (software bills of materials), generate SBOMs from Package URLs (PURLs), track scan progress, and retrieve findings.
For a narrative walkthrough of the same flow, see the API Quickstart; for authentication, quotas, and error envelopes, see API and Development.
Start here
- Open Submit an SBOM for scanning to review the request body and response format.
- Use Get the current status of a queued/running scan after submission to track progress.
- Read Get one SBOM with all its scans, vulnerabilities and findings to inspect completed results.
- Use List all SBOMs for the API-key holder to review previously submitted SBOMs.
What you can do with the API
- Submit an SBOM for analysis.
- Generate an SBOM from a Package URL.
- Poll scan status for queued and running work.
- Retrieve SBOMs, scans, and findings.
- Delete an SBOM along with its scans and finding records.
- Consume the malware feed as threat intelligence.
- Give AI agents scan access over the Model Context Protocol.
- Ingest observed package pulls from an artifact-cache collector.
- Confirm an alert email address via a one-time token.
Additional endpoints
Browse submitted SBOMs and their latest scan status.
Remove an SBOM together with its scans and finding records.
Use the POST variant if your client submits status checks to /scans/status.
Every package flagged malicious in a window of up to 7 days.
JSON-RPC endpoint so AI agents can scan and read results.
Submit observed artifact-cache pulls. Does not consume scan quota.
Updated 19 days ago
