Errors

All errors return a JSON body with ok: false and a human-readable error message. Stack traces are never exposed.

Error Format

{
  "ok": false,
  "error": "Human-readable error message"
}

HTTP Status Codes

CodeMeaningWhen
200OKSuccessful request
201CreatedResource created (triggers, shares)
400Bad RequestMissing or invalid parameters
401UnauthorizedMissing Authorization header
403ForbiddenInvalid token
404Not FoundResource or endpoint not found
429Too Many RequestsRate limit exceeded
500Internal Server ErrorUnhandled error
502Bad GatewayExternal service or connector error
503Service UnavailableAuth secret not configured or component unavailable

CLI Exit Codes

When interacting via the CLI, commands use numeric exit codes that map to error categories:

Exit CodeNameMeaning
0SUCCESSCommand completed successfully
1GENERALGeneral error
2NETWORKNetwork or connectivity failure
3AUTHAuthentication error
5NOT_FOUNDResource not found
7TIMEOUTOperation timed out