API Keys
Owner onlyLet an AI agent or automation tool query your SchedHubPH data, using its own scoped key
Owner access only
API Keys is a tenant-wide administrative surface (§5.1/D20/D19). Manager and Staff accounts don't get a read-only view here — the surface doesn't render for them at all, same as it wouldn't in the real app.
| Label | Scopes | Last used | Created | |
|---|---|---|---|---|
| n8n AI receptionist | read:bookingswrite:bookings | 2 hours ago | Sep 15, 2026 | |
| Reporting dashboard (Looker) | read:reports | 1 day ago | Aug 2, 2026 | |
| Old integration test | read:pos | — | Jun 1, 2026 | Revoked |
A key authenticates as this Business's own account, scoped to only what you check above (§18) — it can never see another business's data, and every creation, revocation, and use is written to your Audit Trail.
Implementation notes for Cursor
Entities: ApiKey (label, scopes[], last_used, created, business_id) — always scoped to a single Business (§18), never a platform-wide credential.
Key states: the raw key value is shown once, on settings-api-key-new.html (D29) and never retrievable again — only its scopes/metadata are listed afterward. Scope checkboxes here are additive/least-privilege by default (start unchecked except a sane default like read:bookings).
Forbidden inventions: no key rotation/expiry policy modeled beyond manual Revoke — don't invent auto-expiry. Revoke is mocked (see button title); wire to the real DELETE endpoint.
Governs: §18 (scoped API access), §5.1/D20 (Owner-only gate), Audit Trail logging on create/revoke/use.