Understanding How The API Works »
Adding forbid permission rules to a user, which denies the user the specified permissions within Dyn Managed DNS, via the API requires specific syntax depending on whether you are using REST or SOAP. Use this table to find the syntax for your command.
REST Syntax
Click to view all REST Resources |
UserForbidEntry/ POST — Adds the forbid rule to the user’s permission group.
HTTP Action — POST
URI — https://api.dynect.net/REST/UserForbidEntry/<user_name>/<permission>
|
Arguments — Click for More Info
- array
zone — A list of zones where the forbid rule applies.
- string
zone_name — Required. The name of the zone or FQDN where the forbid rule applies.
- string
recurse — Indicates whether or not the forbid rule applies to subnodes of the zone_name as well.
Valid values:
Y – Permissions apply to zone_name and any nodes below zone_name . Default.
N – Permissions apply only to zone_name .
|
Response:
Not Applicable.
|

SOAP Syntax
Click to view all SOAP Commands |
AddUserForbids — Adds the forbid rule to the user’s permission group. |
Arguments — Click for More Info
- string
user_name — Required. The user’s name.
- array
forbid — A list of forbid rules to add to the user.
- string
name — Required. The name of the permission forbidden to the user.
- array
zone — A list of zones where the forbid rule applies.
- string
zone_name — Required. The name of the zone or FQDN where the forbid rule applies.
- string
recurse — Indicates whether or not the forbid rule applies to subnodes of the zone_name as well.
Valid values:
Y – Permissions should apply to zone_name and any nodes below zone_name . Default.
N – Permissions should apply only to zone_name .
- string
token — Required. The session identifier.
|
Response:
Not Applicable.
|
Example Request — Click for More Info
{
'token' => 'asdlj34ot879834cdzjklfK',
'user_name' => 'user1',
'forbid' => [
{
name => 'RecordGet'
}, {
name => 'RecordUpdate',
zone => [
{
zone_name => 'test.com',
recurse => 'N'
},
],
},
],
}
|
<< DNS API Knowledge Base