security
1 operation. Shapes are sketches of the declared schemas, bounded in depth — the authoritative document is linked from the index.
POST/security/secret-scan
No declared credential scheme
Reachable without a Bucker session token. Signature-authenticated by GitHub's published key over the exact bytes; answers one body for every outcome; the leak response disables a credential, never revokes (P3-45).
Response 200
{
received: true
}Response 429 · `rate_limited` or `quota_exceeded` — over a ceiling. `Retry-After` says when to come back, and `x-ratelimit-limit` / `-remaining` / `-reset` describe the bucket.
{
error: {
code: "bad_request" | "conflict" | "forbidden" | "internal_error" | "mfa_required" | "not_found" | "payload_too_large" | "quota_exceeded" | … 6 more
message: string
details?: unknown
requestId?: string
}
}Response 500 · `internal_error` — an unhandled failure on this side. The message is always generic; `requestId` is the part worth quoting.
{
error: {
code: "bad_request" | "conflict" | "forbidden" | "internal_error" | "mfa_required" | "not_found" | "payload_too_large" | "quota_exceeded" | … 6 more
message: string
details?: unknown
requestId?: string
}
}Request
curl -X POST https://api.bucker.io/security/secret-scan