Skip to main content

List User Assignments

GET/companies/{id}/user-assignments
Agency-scoped keys

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

Summary​

Returns project-role users and their assigned projects using the same membership rules as the UI assignments export. Requires a company-scoped key with read:users access.

Results include inactive users and users with no assigned projects. Only projects belonging to the requested company are returned. For effective permissions, use List User Permissions.

URL Parameters​

NameTypeRequiredDescription
idstringYesCompany id or nanoid within the key's company scope

Query Parameters​

NameTypeRequiredDescription
statusstringNoactive or inactive; omit to include all users
pageintegerNoPage number (default 1)
limitintegerNoUsers per page (default 50, maximum 200)
fieldsstringNoComma-separated response fields or nested paths, such as id,name,projects.id

Use ?status=active to fetch only active users. Users are treated as active unless explicitly marked inactive. The filter applies before pagination, and meta.total counts matching users. Results are ordered by name and id.

Request Example​

curl -X GET 'https://api.requidex.com/api/open/v1/companies/{id}/user-assignments' \
-H 'Authorization: Bearer <API_KEY>' \
-H 'Accept: application/json'

Response Fields​

FieldTypeDescription
idstringUser id
namestringUser name
emailstringUser email address
rolestringFriendly project-role label
customRoleobject or nullCustom role in the requested company: id and name, or null
jobTitlestringUser job title
statusstringActive or Inactive
projectsarrayAssigned projects in the requested company
Show child attributes
  • id string - Project id
  • name string - Project name

The response envelope contains success, a data array of users, and meta with page, limit, and total user count. Raw permission records and references to other companies' projects are excluded.

The role field remains the friendly base-role label. customRole is { "id": "…", "name": "…" } for a role assigned in the requested company, or null when no custom role is assigned. Roles from other companies are not included.

Response Example (200)​

{
"success": true,
"data": [
{
"id": "67bc36db80a1616ec3f47001",
"name": "Alex Smith",
"email": "alex@example.com",
"role": "Project Approver",
"customRole": { "id": "67bc36db80a1616ec3f47003", "name": "Contractor Approver" },
"jobTitle": "Project Manager",
"status": "Active",
"projects": [
{
"id": "67bc36db80a1616ec3f47002",
"name": "Central Office"
}
]
}
],
"meta": { "page": 1, "limit": 50, "total": 1 }
}

MCP Tool​

The MCP server exposes this operation as open_api_list_company_user_assignments (operation ListCompanyUserAssignments) with inputs id, status, page, limit, and fields. The same company-only access restriction applies.

Errors​

HTTP StatusDescription
400Missing company identifier or invalid user status
401Missing, invalid, revoked, or expired API key
403Agency-scoped key, missing read:users, or other access restriction
404Company not found within the key's scope
429Rate limit exceeded
500Unexpected internal error