Get sender account - Autotouch AI

This page documents the canonical HTTP contract for this endpoint.

Resolution uses the send scope: the actor must own the account, have an active send delegation, or be an admin. Read-only delegations do not qualify. For managed-fleet accounts, platform assignment/access rules still apply to admins. If a nonempty capabilities list is present, the account must include send; otherwise the endpoint returns 409. Ordinary account connection status does not have to be ready for inspection; managed-fleet accounts also require current allocation and mailbox access.

Only active (not revoked) delegations are included. The example is abbreviated; account and delegation records can contain additional fields.

Path parameters

sender_account_idrequired
string
Sender account ID.

Name	Type	Description
sender_account_idrequired	string	Sender account ID.

Errors

Status	Meaning
401	Authentication failed or the actor/organization context is unavailable.
403	The actor lacks the required send access to this sender account.
404	Sender account not found.
409	The sender account does not support the required send scope.

Example

bash

curl -X GET "https://app.autotouch.ai/api/sender-accounts/sacct_linkedin_67c1" \
    -H "Authorization: Bearer YOUR_DEVELOPER_API_KEY"

Response example

json

{
    "success": true,
    "account": {
      "id": "sacct_linkedin_67c1",
      "channel": "linkedin",
      "provider": "unipile_linkedin",
      "owner_user_id": "67c1dc35b4dd8f2d4999ed01",
      "status": "ok",
      "is_default": true,
      "capabilities": ["send"]
    },
    "delegations": [
      {
        "id": "sdel_123",
        "sender_account_id": "sacct_linkedin_67c1",
        "owner_user_id": "67c1dc35b4dd8f2d4999ed01",
        "delegate_user_id": "67c1dc35b4dd8f2d4999ed02",
        "scopes": ["send"],
        "revoked_at": null
      }
    ]
  }