Create domain event subscription

Creates a subscription that sends one domain's events of one model to your post-url. It is POST /subscriptions with the domain taken from the path; a domain in the body is ignored.

Requires Basic User, Site Manager, Office Manager, Reseller, or Super User, and read access to the model (403 without it). A Reseller can name any domain in its own territory. Office Manager, Site Manager, and Basic User can name only their own domain, and a Site Manager only users of its own site.

Choose model from these values:

`model`	Sends
`call`	Active call updates
`call_origid`	Active call updates, only the latest state of each call per batch
`cdr`	Completed call records
`agent`	Call center agent status changes, matched on the call queue
`voicemail`	New voicemail
`message`, `messagesession`	Chat and SMS messages and sessions

Also available: presence, subscriber, auditlog, auditlog_lite (creates and deletes of main objects only), domain, and device.

post-url must be an http:// or https:// URL with a host, at most 256 characters, with the scheme only once and no user:password@ part. Unless you are a Super User, every address the host resolves to must be public: loopback, link-local, private, shared (CGNAT), and unique-local addresses are refused, and so are this platform's own servers. A host that does not resolve is refused too. Each refusal is a 400 that names the rule. An installation can allow private addresses with the NsSubscriptionAllowPrivateUrls setting. Use https:// with a certificate that validates, because a certificate error counts as a failed delivery.

subscription-expires-datetime takes RFC 3339, such as 2027-09-01T14:30:00+00:00, or YYYY-MM-DD HH:MM:SS in UTC. It is stored in UTC and read back as RFC 3339. Any other value returns 400.

The call waits up to 5 seconds for the subscription to be stored, then returns it with 200. Creating the same subscription twice returns 409. See POST /subscriptions for how events are delivered and expired. Retries and a signing secret are tracked in NN-663.

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//subscriptions' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "post-url": "https://core1.example.com/log.php", "model": "call", "user": "*", "reseller": "*", "domain": "*", "user-scope": "Super User", "subscription-geo-support": "yes", "server_preferred": "core1.example.com" }'

{ "id": "f38d00a5eed9d15603922fe98db23600", "subscription-geo-support": "yes", "post-url": "https://core1.example.com/log.php", "model": "call", "user-scope": "Super User", "reseller": "*", "domain": "*", "user": "*", "preferred-server": "core1.example.com", "current-active-server": "", "status": "pending", "error-count": 0, "posts-count": 0, "subscription-creation-datetime": "2026-10-09T17:16:36+00:00", "subscription-expires-datetime": "2027-10-04T17:16:36+00:00" }

Create domain event subscription

Request

Responses