Skip to main content

Find Approvals

Search for approvals associated with a user. Filter by state, date range, entitlement, or request details.

GET https://instance.securid.com/aveksa/command.submit?cmd=findApprovals

note

When using a trusted application token, auth-user-id is required to specify the user whose approvals to search. When using a user token from loginUser, auth-user-id is not applicable. The state and sort parameter values are case-sensitive and must be lowercase.

caution

Invalid auth-user-id values return 401 The token is invalid or expired rather than a meaningful user-not-found error. Invalid sort values are silently ignored and fall back to asc.

Request

Parameters

findApprovals
formatxml - (Default) Returns the response as XML.

json - Returns the response as JSON.
auth-user-idThe ID of the user whose approvals to search. Required when using a trusted application token. Not applicable for user tokens.
approval-idThe ID of a specific approval, in id:WPDS:n format. Returns a single approval object when matched.
stateThe approval state to filter by. Valid values: pending completed all. (Default) pending
sortSort results by due date. Valid values: asc desc. (Default) asc. Values are case-sensitive.
page-sizeNumber of approvals per page. (Default) 20
start-pageStarting page number. (Default) 1
user-idFilter by the ID of the user who placed the request.
user-first-nameFilter by the first name of the user who placed the request.
user-last-nameFilter by the last name of the user who placed the request.
business-sourceFilter by the business source of the request.
entitlement-nameFilter by the name of the entitlement in the request.
entitlement-typeFilter by the type of the entitlement in the request.
requested-afterLower bound for the request date. Format: dd-mmm-yyyy (e.g. 01-jan-2025).
requested-beforeUpper bound for the request date. Format: dd-mmm-yyyy (e.g. 31-dec-2025).
due-afterLower bound for the due date. Format: dd-mmm-yyyy (e.g. 01-jan-2025).
due-beforeUpper bound for the due date. Format: dd-mmm-yyyy (e.g. 31-dec-2025).
completed-afterLower bound for the completion date. Format: dd-mmm-yyyy (e.g. 01-jan-2025).
completed-beforeUpper bound for the completion date. Format: dd-mmm-yyyy (e.g. 31-dec-2025).

Headers

Bearer token

Response

Parameters

NumApprovalsTotal number of matching approvals.
ApprovalAbsent when no approvals are returned. A single object when 1 approval is returned. An array of objects when multiple approvals are returned.
Approval.WorkItemIdUnique identifier of the approval work item, in id:WPDS:n format.
Approval.WorkItemNameDisplay name of the approval step.
Approval.RequestNameName of the change request this approval belongs to.
Approval.WorkItemDueDateDue date and time of the approval.
Approval.WorkItemCompletedDateDate and time the approval was completed. Empty string if not yet completed.

Examples

Request

curl -K -X GET \
"https://instance.securid.com/aveksa/command.submit?cmd=findApprovals&format=json&auth-user-id=jsmith&state=all" \
-H "Authorization: Bearer <token>"

Response

{
"findApprovals": {
"Approval": [
{
"WorkItemName": "Asset Business Owner Approval",
"WorkItemId": "1001:WPDS:1",
"RequestName": "00001",
"WorkItemCompletedDate": "2025-12-10 10:03:10.0",
"WorkItemDueDate": "2025-12-15 10:02:40.0"
},
{
"WorkItemName": "Asset Business Owner Approval",
"WorkItemId": "1002:WPDS:1",
"RequestName": "00002",
"WorkItemCompletedDate": "",
"WorkItemDueDate": "2026-01-15 10:00:00.0"
}
],
"NumApprovals": 2
}
}

Verified with RSA Governance & Lifecycle version 8.0.0.188886 P10_HF01.

See Also