setup-cells
1 operation. Shapes are sketches of the declared schemas, bounded in depth — the authoritative document is linked from the index.
GET/orgs/{orgSlug}/projects/{projectSlug}/setup-cells
Requires bearerAuth
The first-week read of one project: a cell per pillar (errors, source maps, first event, capture per signal, ingest loss, hosts, collectors, replay, consent, vitals, AI calls, databases, alerting, checks, analytics trust, spend, status pages, approvals, Slack, mail), each with a state from a closed list (live, lossy, silent, missing, unknown, not_applicable), the time of its last evidence, an evidence handle, the next step as a tool or a human act and the per-area read that holds the detail. Every cell is the stored result of that area and never a check of its own; a check not built reads unknown and never disappears. A cell whose read needs a scope the caller lacks is named in omitted with the scope.
Parameters
| Name | In | Type | Notes |
|---|---|---|---|
orgSlugrequired | path | string | min length 1 |
projectSlugrequired | path | string | min length 1 |
Response 200
{
generatedAt: string
cells: {
id: "errors" | "first_event" | "source_maps" | "capture_health" | "capture_traces" | "capture_logs" | "capture_sessions" | "ingest_loss" | … 15 more
state: "live" | "lossy" | "silent" | "missing" | "unknown" | "not_applicable"
reason: "evidence_present" | "no_evidence_yet" | "evidence_stopped" | "defect_reported" | "check_not_built" | "not_applicable_here" | "read_failed" | "not_enough_data" | … 6 more
lastEvidenceAt: string | null
evidence: string
next: {
kind: "tool" | "human_act"
name: string
} | null
read: string
pendingCard: string | null
counts: Record<string, number>
}[]
omitted: {
id: "errors" | "first_event" | "source_maps" | "capture_health" | "capture_traces" | "capture_logs" | "capture_sessions" | "ingest_loss" | … 15 more
scope: string
}[]
summary: {
live: number
lossy: number
silent: number
missing: number
unknown: number
not_applicable: number
}
}Response 400 · `bad_request` — the path, query or body failed validation. `details` carries the Zod issues, one per offending field.
{
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 401 · `unauthorized` — no credential, or one that is expired, revoked or not valid for this resource. `mfa_required` when the credential is good but a second factor is owed.
{
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 403 · `forbidden` — the credential is valid and its scopes or this principal’s membership do not reach this resource. Scopes are re-intersected with live memberships on every request, so this can appear for a token that worked yesterday.
{
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 404 · `not_found` — no such resource, OR one this principal cannot see. The two are deliberately one answer: a 403 would confirm the existence of something whose identifier is guessable.
{
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 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 https://api.bucker.io/orgs/{orgSlug}/projects/{projectSlug}/setup-cells \
-H "authorization: Bearer $BUCKER_TOKEN"