NSns-api
Dial Permisions

Add a new permission to a dialpolicy table in Domain

Changed on
post/domains/{domain}/dialpolicy/{policy}/permission

Request

  • Base URL
    https://ns-api.com/ns-api/v2
  • URL
    https://ns-api.com/ns-api/v2/domains/{domain}/dialpolicy/{policy}/permission
  • Auth
    HTTP bearer

Path parameters

domainstring required

This is the main organization name. This is used to link resource to its group/tenant/organization/enterprise. Then using in path for GET you can set to "~" to use the domain name linked to your token/key instead of the domain name itself when reading for your own domain.

Example:example.com
policystring required

Request body

synchronous'yes' | 'no' required

When synchronous is requested with "yes" the response will be a 200 on success and will contain a valid JSON representiation of the new resource. If no or left off request a 202 "Accepted" will be given in a success case and this can be considered a success. Synchronous responses will be a little slower as the API will process the geo replication request and wait till the local copy has been written and can be read back berfore sending a response.

permission-matchstring required

The specific match to check against

permission-mode'permit' | 'deny' required

To allow or deny specific match

permission-reasonstring required

The description/reason for making the rule.

Response

dialpolicystring required

The Dial Policy Name

domainstring

The domain the owns the Dial Policy

permission-matchstring required

The specific match to check against

permission-mode'permit' | 'deny' required

To allow or deny specific match

permission-reasonstring required

The description/reason for making the rule.

created-datetimestring

The time the rule was created

permission-idstring required

This is the ID fro the permission rule. Its the base64 encode of permission-match, but is needed for edit and delete.

Changes