Skip to content
bucker

API reference

AI-first error monitoring — control-plane API. 652 operations across 523 paths, version 0.1.0. Every page below is generated from https://api.bucker.io/openapi.json — the same document the API serves, so a route that changed shape here changed shape there.

Base URL and authentication

The control plane is https://api.bucker.io. Requests carry a bearer token: a personal access token (bpat_) for a script, or a session token for the dashboard. Tokens are org-pinned and their scopes are re-intersected with live memberships on every request, so a demoted owner’s token shrinks without anything being revoked.

curl https://api.bucker.io/orgs/<orgSlug>/projects \
  -H 'authorization: Bearer $BUCKER_TOKEN'

The data plane is a different host and a different credential: envelopes go to the region-prefixed ingest host in your DSN, authenticated by the DSN’s public key alone. That protocol has its own page — see the ingest wire protocol.

Errors, pagination and versioning

Error responses are listed per route below. The rule behind them: every endpoint answers 400 for a body that fails validation, 401 without a usable token, 403 when the token is valid but the scope or membership is not, 404 for a resource this principal cannot see, and 429 with x-ratelimit-* headers. List endpoints are keyset-paginated: pass the nextCursor from the previous page back as cursor. Every response carries X-API-Version, and a route on its way out carries RFC 8594 Deprecation, Sunset and a successor Link.

Route groups

Grouped by the tag the API assigns each route. The full document is 6.3 MB, which is why it is linked rather than inlined: a reference you have to download is not a reference.

Route groups
GroupOperationsWhat it covers
.well-known2
accountability4
admin69The deployment-operator console.
agent25
agents26Autonomous agents: delegation, budgets and the trust ladder.
alert-events2
alert-rules5
anomaly3
api10
approval-policies4
approval-requests5
approvals1
artifacts4
auth16Authentication, sessions, MFA and account recovery.
autofix6
behavioral-fingerprint3
billing13Plans, usage and subscription billing.
code-mappings3
codebase3
compliance25Data-subject rights, retention, residency and audit export.
dashboards7
dependency-commons5
digest2
durability6
escrow5
evidence-pricing6
explore5
feedback3
flag-events1
grouping4
grouping-precision1
grouping-suggestions4
hotfix-providers1
hotfixes5
incident-close1
integrations11
invites4
issue-embeddings1
issues44Error groups: triage, timeline and remediation.
keys4
landing13
logs1
me8The signed-in principal's own tokens, devices and digest preferences.
members3
merges2
meta3Liveness, readiness, metrics and edition metadata.
mitigation-actions1
mitigation-documents1
mitigation-providers1
mitigations6
monitors6
neutral-verification4
notification-channels4
oauth1
onboarding2
orgs5Organization creation, membership and settings.
probes2
projects14Project creation and settings.
proof-ledger19An organization's tamper-evident proof ledger.
proposals5
public2Unauthenticated routes served to end users and integrations.
release-health2
releases3
replay1
repos5
retention4
reversal-debt5
rollouts9Feature-flag rollout evaluation and bisection.
scim23SCIM provisioning for users, groups and agents.
scm1Source-control provider connections.
scoreboard14Autonomy scoreboard attempts, replays and pins.
security-lane1
security-policy2
sso6SAML and OIDC single sign-on connections.
state-probes6
stats1
status19Public status-page summaries.
status-pages47
suite-config3
support-access3
teams9
traces1
transparency8The public transparency register and its Merkle proofs.
uptime-monitors7
v12
views4
warehouse6
webhooks7Inbound webhooks from source control, Stripe and integrations.
widget-preview1