curl -X DELETE "https://api.scanova.io/multi-users/access-levels/42/" \
-H "Authorization: YOUR_API_KEY"
Shared Users & Roles
Delete a custom role
DELETE /multi-users/access-levels//
DELETE
/
multi-users
/
access-levels
/
{pk}
/
curl -X DELETE "https://api.scanova.io/multi-users/access-levels/42/" \
-H "Authorization: YOUR_API_KEY"
Deletes one of the account’s own custom roles on
A successful call returns
api.scanova.io, authenticated with your raw API key.
DELETE https://api.scanova.io/multi-users/access-levels/{pk}/
Authorization: YOUR_API_KEY
integer
required
The role’s
id.curl -X DELETE "https://api.scanova.io/multi-users/access-levels/42/" \
-H "Authorization: YOUR_API_KEY"
204 No Content.
Reassign teammates first
If the role is still assigned to any shared user, this returns a friendly400 (not a raw database integrity error) asking you to reassign those teammates to a different role before deleting. As with update, a pk belonging to a system role or another account’s custom role returns 404.
Related
- Retrieve a role — check who’s assigned before deleting.
- Update a shared user — reassign a teammate off this role first.
- List roles — pick a replacement role.
- API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: YOUR_API_KEY. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Path Parameters
Response
Role deleted.
Was this page helpful?