Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.letmepost.dev/llms.txt

Use this file to discover all available pages before exploring further.

Your key is valid; it just can’t do this. The two most common causes are role mismatch (e.g., a member key trying to manage org settings) and write attempts on a read-only endpoint shape. For most cross-organization or cross-profile attempts you’ll see not_found instead — we 404 to avoid leaking resource existence to a key that shouldn’t see it.

​
What triggers it

  • An owner-only action (e.g., deleting an organization, rotating an org-wide secret) attempted by a member key.
  • A read-only key on a write endpoint.
  • A profile-scoped key trying to modify org-wide settings.

​
Response shape

unauthorized.json
{
  "error": {
    "code": "unauthorized",
    "message": "This action requires an owner-scoped key.",
    "remediation": "Mint an owner-scoped key from the dashboard, or have an owner perform the action.",
    "requestId": "req_..."
  }
}