Skip to content

Resolve

Resolve endpoints answer who should handle a workflow question and expose auditable resolve request history. Resolve returns directly associated users plus active members of associated groups, with active delegations applied as runtime coverage.

MethodPathRequired scope
POST/api/v1/resolveapi:resolve
GET/api/v1/resolve-requestsapi:resolve-requests:read
GET/api/v1/resolve-requests/:idapi:resolve-requests:read
Terminal window
curl -X POST "<your-roster-public-url>/api/v1/resolve" \
-H "Authorization: Bearer ${ROSTER_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"query": "Who should handle vendor security review for Atlas onboarding?",
"project_id": "proj_123",
"mode": "live"
}'

project_id is optional. When it is omitted, Resolve searches all projects visible to the API key owner. mode is optional, defaults to live, and accepts live or test.

Resolve uses project status and project read access:

  • Without project_id, live mode receives readable live projects and test mode receives resolvable test projects.
  • A live project can be resolved explicitly when the caller has read access.
  • A test project can be resolved explicitly only with mode: "test" and admin or project-owner access.
  • draft and archived projects are excluded from REST Resolve.
Terminal window
curl "<your-roster-public-url>/api/v1/resolve-requests?project_id=proj_123&resolution_status=success&limit=25" \
-H "Authorization: Bearer ${ROSTER_API_KEY}"

Supported filters include project_id, actor_id, resolution_status, created_after, created_before, query, and limit. resolution_status accepts success, not_found, out_of_scope, or error. Date filters accept ISO date-time strings. query searches the original Resolve request text. limit accepts values from 1 to 100 and defaults to 25.