Skip to main content

List Access Rule Mappings

GET/access-rule-mappings
Agency-scoped keys

This endpoint is not available for agency-scoped API keys.

Summary

Returns global default role-based access control (RBAC) grants. Requires a valid company-scoped key.

Each row grants the action in can to the role in a. The role identifiers are internal values such as projectApprover, rather than friendly display labels. These mappings are global defaults.

Defaults do not include user overrides, project membership, workflow restrictions, or record-level checks. To inspect a user's effective project permissions, use List User Permissions.

Query Parameters

NameTypeDescription
groupBystringrole or rule; omit for individual mappings
rolestringExact role identifier, matched against a
actionstringExact action identifier, matched against can
querystringCase-insensitive search across a, can, and configKey
pageintegerPage number (default 1)
limitintegerMappings per page (default 50, maximum 200)
sortBystringa, can, or configKey (default a)
sortOrderstringasc or desc (default asc)
fieldsstringComma-separated response fields to return

All parameters are optional. Filters combine and apply before grouping. When grouped, page, limit, and meta.total count groups, with all matching mappings included in each returned group. Groups are ordered by role, or action then configuration key, using sortOrder. sortBy applies only to ungrouped results.

Request Example

curl 'https://api.requidex.com/api/open/v1/access-rule-mappings?role=projectApprover&page=1&limit=50' \
-H 'Authorization: Bearer <API_KEY>'

Response Fields

FieldTypeDescription
idstringMapping id
astringRole identifier
canstringAction identifier granted by default
configKeystringConfiguration key, when present on the mapping
typestringRBAC

The response contains success, a data array, and meta with page, limit, and total matching mappings. No matching mappings returns an empty data array and total: 0.

Grouped Response Fields

Use ?groupBy=role to collect each role's default rules, or ?groupBy=rule to see which roles share each action and configuration key. Omit groupBy to keep the response fields above.

FieldTypeDescription
astringRole identifier; present with groupBy=role
canstringAction identifier; present with groupBy=rule
configKeystringConfiguration key, when present; included with groupBy=rule
rulesarrayMatching mappings in this group
Show child attributes
  • id string - Mapping id
  • a string - Role identifier
  • can string - Action identifier
  • configKey string - Configuration key, when present
  • type string - RBAC

Use fields with the grouped response shape, for example fields=a,rules when grouping by role.

Response Examples (200)

The identifiers, action, and configuration key below are illustrative.

Omit groupBy to return individual mappings.

{
"success": true,
"data": [
{
"id": "67bc36db80a1616ec3f47003",
"a": "projectApprover",
"can": "exampleAction",
"configKey": "exampleConfig",
"type": "RBAC"
}
],
"meta": {
"page": 1,
"limit": 50,
"total": 1
}
}

MCP Tool

Use open_api_list_access_rule_mappings (operation ListAccessRuleMappings) with the query parameters above. The same authentication and company-only restrictions apply.

Errors

HTTP StatusDescription
400Invalid groupBy value
401Missing or invalid authentication
403Agency-scoped key or another access restriction
429Rate limit exceeded
500Unexpected internal error