Approve a deployment (approver)
Record approval for a deployment job. When all required approvers have approved, the job transitions to pending and dispatch runs. Session callers are always themselves. An ordinary API key without actingUserEmail approves as the key owner. A key with deployment:approve-as must send actingUserEmail (the Ellavox path); that names a required approver, is logged via: ellavox, and can satisfy every vote in a multi-approver flow — it is opt-in at key creation by an org admin.
Authentication
API key supplied via the X-API-Key header. Takes precedence over bearerApiKey when both are present. Listed only on operations that actually accept a key.
Same organization API key supplied as a Bearer token in the Authorization header (Authorization: Bearer <key>). Compatible with OpenAI-SDK-standard clients. Accepted wherever this scheme is listed on the operation — not every endpoint; if both X-API-Key and Authorization: Bearer are present, X-API-Key wins.
Supabase session JWT from a signed-in browser session, supplied as Authorization: Bearer <jwt>. This is what the web app sends. It shares the Authorization header with bearerApiKey; the server distinguishes them by the ela_ prefix on API keys.