Request authorisations

Request authorisation from one or more Brand Owners to send under their existing registered Sender IDs. A single call can span multiple clients, each with multiple Sender IDs. Each (client, sender_id) pair becomes one authorisation and emails the owner’s representative a secure one-time link. The link is sent only to the owner by email and is never returned in the API response. Processing is best-effort per pair: one invalid Sender ID does not sink the batch. Each pair returns its own status. Required permission: authorisations:write

Before anything is created

Your organisation must be an approved participant in the country’s SMS Sender ID scheme register. This is the same check the Senderz webform applies before Entity Associate intake. If the check does not pass, the request creates nothing and sends no email.

Status	Code	Meaning
`403`	`scheme_participation_required`	Your organisation is not an approved scheme participant.
`503`	`scheme_register_stale`	Participation cannot be confirmed because the register copy is out of date. Retry later.
`502`	`scheme_check_failed`	The participation check could not run. Retry later.
`422`	`market_not_supported`	Entity Associate authorisation is only available where a live authority register exists (AU today).
`403`	`insufficient_scope`	The key lacks `authorisations:write`.

Use Scheme participation check to confirm your status in advance.

Request body

string

required

Market for all authorisations in this batch. ISO 3166-1 alpha-2 (e.g. AU).

array

required

One or more Brand Owner clients.

Show client properties

string

required

The Brand Owner’s registered legal entity name.

string

The Brand Owner’s registration number (e.g. ABN). Recommended.

string

Name of the owner’s authorised representative.

string

required

Email of the representative. Each Sender ID sends this person a secure one-time link.

array

required

The owner’s existing Sender IDs you seek authorisation to send under. Up to 25 per client; up to 50 clients per batch.

Response

Returns 201 when at least one authorisation was created, or 207 when every pair failed.

string

Batch identifier for this request.

array

One entry per (client, sender_id) pair.

Show properties

string

created or failed.

string

Authorisation ID (when created).

string

The country’s registration authority (ACMA for AU).

string

awaiting_owner_confirmation on creation.

boolean

Whether the owner’s authorisation email was sent.

string

Present when status is failed.

object

Counts: clients, requested, created, failed.

Example

curl -X POST https://api.senderz.ai/v1/associate-authorisations \
  -H "Authorization: Bearer sk_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "country": "AU",
    "clients": [
      {
        "owner_entity_name": "CHIC MANAGEMENT PTY LIMITED",
        "owner_entity_abn": "80104930743",
        "owner_rep_name": "Paul",
        "owner_rep_email": "paul@example.com",
        "sender_ids": ["CHIC", "Scoop"]
      },
      {
        "owner_entity_name": "HELLOWORLD TRAVEL LIMITED",
        "owner_entity_abn": "60091214998",
        "owner_rep_name": "Geoff",
        "owner_rep_email": "geoff@example.com",
        "sender_ids": ["Hello"]
      }
    ]
  }'

201

{
  "ok": true,
  "data": {
    "session_id": "3f2a9c1e-7b4d-4e8a-9f10-2c5d8e6a1b40",
    "authorisations": [
      {
        "status": "created",
        "id": "aa_a1b2c3",
        "touchpoint_id": "tp_a1b2c3",
        "owner_entity_name": "CHIC MANAGEMENT PTY LIMITED",
        "owner_entity_abn": "80104930743",
        "claimed_sender_id": "CHIC",
        "owner_rep_email": "paul@example.com",
        "country": "AU",
        "authority": "ACMA",
        "state": "awaiting_owner_confirmation",
        "email_sent": true
      }
    ],
    "summary": { "clients": 2, "requested": 3, "created": 3, "failed": 0 }
  },
  "meta": {
    "request_id": "req_auth123",
    "timestamp": "2026-09-19T14:30:00+10:00"
  }
}

Sandbox keys validate the request and return simulated results without running the participation check or sending email. Sandbox responses include a placeholder link for integration testing only; live responses never include one.

Brands

Sender IDs

Registrar Intelligence & Authorisation

Request authorisations

Before anything is created

Request body

Response

Example

​Before anything is created

​Request body

​Response

​Example

Before anything is created

Request body

Response

Example