curl --request PUT \
--url https://api.dfns.io/permissions/{permissionId}/archive \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'X-DFNS-USERACTION: <api-key>' \
--data '
{
"isArchived": true
}
'{
"id": "pm-37vj4-jkr4l-lc9945spfftkne57",
"name": "<string>",
"operations": [
"<string>"
],
"status": "Active",
"isImmutable": true,
"isArchived": true,
"dateCreated": "2023-04-14T20:41:28.715Z",
"dateUpdated": "2023-04-14T20:41:28.715Z"
}Archives or unarchives a permission (role). Archived permissions are effectively soft-deleted.
curl --request PUT \
--url https://api.dfns.io/permissions/{permissionId}/archive \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'X-DFNS-USERACTION: <api-key>' \
--data '
{
"isArchived": true
}
'{
"id": "pm-37vj4-jkr4l-lc9945spfftkne57",
"name": "<string>",
"operations": [
"<string>"
],
"status": "Active",
"isImmutable": true,
"isArchived": true,
"dateCreated": "2023-04-14T20:41:28.715Z",
"dateUpdated": "2023-04-14T20:41:28.715Z"
}CustomerEmployee)EndUser)Permissions:Archive: Always required.Bearer Token: Used to authenticate API requests. More details how to generate the token: Authentication flows
User Action Signature: Used to sign the change-inducing API requests. More details how to generate the token: User Action Signing flows
ID of the permission (also referred to as "role" in the dashboard).
1 - 64Set to true to archive, false to unarchive.
Success
ID of the permission (also referred to as "role" in the dashboard).
1 - 64^pm-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"pm-37vj4-jkr4l-lc9945spfftkne57"
Human-readable name of the permission (role).
List of API operations this permission grants access to. See Permissions List for available operations.
Current status of the permission.
Active Whether this permission is system-managed and cannot be modified.
Whether this permission has been archived (soft-deleted).
Was this page helpful?