Create domain dial policy rule

POST

/domains/{domain}/dialpolicy/{policy}/permission

Last modified:2026-10-30 21:29:49

OperationId:CreatePermissionDomain

Adds a rule to a dial policy the domain can use. The name resolves to the domain's own policy first, then to the shared one under * or admin-only, and the rule is filed under the resolved policy's domain. Requires Office Manager scope or higher for a policy the domain owns, Reseller scope for a domain in its territory, or Super User scope, which a shared policy always needs.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Body Params application/json

Examples

Responses

🟢200Accepted

application/json

Returned instead of 202 when synchronous=yes and the rule appeared within 2 seconds: the new rule.

Bodyapplication/json

🟢202OK

🟠400Bad Request

🟠401Authentication Required

🟠404Record not found

🟠403Forbidden

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//dialpolicy//permission' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "permission-match": "sip:+1900???????@*",
    "permission-mode": "deny",
    "permission-reason": "Premium rate",
    "synchronous": "yes"
}'

Response Example

200 - Deny premium numbers

Answer to synchronous=yes.

{
    "dialpolicy": "No Premium",
    "domain": "example.com",
    "permission-match": "sip:+1900???????@*",
    "permission-mode": "deny",
    "permission-reason": "Premium rate",
    "created-datetime": "2026-09-01T14:30:00Z",
    "permission-id": "c2lwOisxOTAwPz8_Pz8_P0Aq"
}

Modified at 2026-10-30 21:29:49

Create shared dial policy rule

Update shared dial policy rule