Grant sender account delegation

This page documents the canonical HTTP contract for this endpoint.

Requires a user session and the account owner or an admin. The account must belong to the authenticated organization and support send when a nonempty capabilities list is present; managed-fleet senders also require the actor’s current allocation and mailbox access. The delegate must be an active user in that organization and cannot be the account owner. Repeating a grant updates the active delegation.

Allowed scopes are view, send, reply, schedule, and draft. Unsupported values return 400. Granting a scope does not make an account support that capability or guarantee the account is ready.

Path parameters

sender_account_idrequired
string
Sender account ID.

Name	Type	Description
sender_account_idrequired	string	Sender account ID.

Body parameters

delegateUserIdrequired
string
Active user ID or exact email of a user in the same organization. The account owner cannot be the delegate.
scopes · optional
array<string>
Unique values from view, send, reply, schedule, draft. Default when omitted or empty: ["send"].

Name	Type	Description
delegateUserIdrequired	string	Active user ID or exact email of a user in the same organization. The account owner cannot be the delegate.
scopes	array<string>	Unique values from view, send, reply, schedule, draft. Default when omitted or empty: ["send"].

Errors

Status	Meaning
400	Delegate must be an active organization user other than the owner; scopes must use supported values.
401	Authentication failed or a user session is required.
403	Developer API keys are blocked; only the account owner or an admin user session can grant delegation.
404	Sender account or active delegate user not found in the current organization.
409	Sender account does not support the send scope required to manage delegation.
422	Invalid or missing delegateUserId/scopes request fields.

Example

bash

curl -X POST "https://app.autotouch.ai/api/sender-accounts/sacct_linkedin_67c1/delegations" \
    -H "Authorization: Bearer <user_session_token>" \
    -H "Content-Type: application/json" \
    -d '{"delegateUserId":"67c1dc35b4dd8f2d4999ed02","scopes":["send"]}'

Request body

json

{
    "delegateUserId": "67c1dc35b4dd8f2d4999ed02",
    "scopes": ["send"]
  }

Response example

json

{
    "success": true,
    "delegation": {
      "id": "sdel_123",
      "sender_account_id": "sacct_linkedin_67c1",
      "owner_user_id": "67c1dc35b4dd8f2d4999ed01",
      "delegate_user_id": "67c1dc35b4dd8f2d4999ed02",
      "scopes": ["send"],
      "revoked_at": null
    }
  }