Developer overview
What you can build on BeeraSafe: session-authenticated APIs for investigations and repository security.
Last updated · September 2026
On this page
BeeraSafe exposes the same authenticated APIs the dashboards use: run Bolt investigations, manage Rampart organizations and scans, and read findings programmatically. Everything below assumes you have a BeeraSafe account and a signed-in session.
What is available
- Bolt investigations API. Submit analysis requests and read the streamed token, done, and error events.
- Bolt CLI tokens. Mint a long-lived terminal token at POST /api/cli/token, then call /api/generate and dashboard reads with Authorization: Bearer. See Bolt CLI.
- Rampart REST API. Organizations, repositories, scans, findings, policies, teams, and global search.
- Shared conventions. Session-cookie or Bearer auth,
{ error }failure shape, andX-RateLimit-*headers on every endpoint.
What is not available
There are no OAuth client-credentials flows in the current application. Server-to-server callers should mint a CLI token for a dedicated service account. If you need narrower scopes, contact support with your use case.
Was this page helpful?

