- Management APIs
- Access Requests - V1
Creates a request to access a resource in your organization.
When creating a request, you specify:
- the request type (
requestTypeId) to use for the request - and the subject line (
subject) of the request
Optionally, you can specify:
- The requester user IDs for the request. If not provided, user IDs are obtained from the user identity of the
API TokenorAccess Token.
The writable attributes of a request
The request type id.
The subject of the request
A list of requester Okta user ids.
[ "00ub0oNGTSWTBKOLGLNR", "00ub0oNGTSWTBKOLGLNR" ]
- field-date-time-value
- field-select-value-writable
- field-text-value
- When requesting for authenticated user |tooltip| Request access for authenticated user by omitting `requesterUserIds`
- When requesting for non-authenticated user |tooltip| As an admin service account, request access for a user by providing `requesterUserIds`
- When request type has required fields |tooltip| As an admin service account, request access for a user and provide required field values
curl -i -X POST \
https://okta-subdomain.pixtulate.com/governance/api/v1/requests \
-H 'Content-Type: application/json' \
-d '{
"requestTypeId": "08ab2db568c7c300079fefd0",
"subject": "I need access to Salesforce"
}'A successful create request response
The id of the Okta user who created the resource
The ISO 8601 formatted date and time when the resource was created
The ISO 8601 formatted date and time when the object was last updated
The id of the Okta user who last updated the object
The request type id.
The subject of the request
A list of requester Okta user ids.
[ "00ub0oNGTSWTBKOLGLNR" ]
A request has a lifecycle. See our request lifecycle documentation.
A request progresses in its lifecycle state based on requester, approver, and administrator activities across a variety of channels, such as:
- Access Request portal
- Slack
- Microsoft teams
The following lifecycle operations are available on a single request.
The date the request was resolved. The property may transition from having a value to null if the request is reopened.
Field values provided when adding the request.
If a request type has required requesterFields, they must be provided when the request is created.
Non-required fields may be omitted when creating the request.
A list of actions. Currently only supports one action per request.
The immutable, persistent identifier that always resolves to the request
- ACCESS_REQUEST
- CUSTOM
- When requesting for authenticated user |tooltip| Request access for authenticated user by omitting `requesterUserIds`
- When requesting for non-authenticated user |tooltip| As an admin service account, request access for a user by providing `requesterUserIds`
- When request's request type has required requester fields |tooltip| When request's request type has required requester fields
- When request type has required fields |tooltip| As an admin service account, request access for a user by providing `requesterUserIds`
- When request's request type has no requester fields, one approval required |tooltip| When request's request type has no requester fields, one approval required
- When request's request type has no requester fields, many approvals required |tooltip| When request's request type has no requester fields, many approvals required
{ "id": "61eb06a3c462d20007f0235c", "subject": "Tom requests access to Salesforce", "requestTypeId": "08ab2db568c7c300079fefd0", "created": "2022-05-05T14:15:22Z", "createdBy": "00ub0oNGTSWTBKOLGLNR", "lastUpdated": "2022-05-05T14:15:22Z", "lastUpdatedBy": "00ub0oNGTSWTBKOLGLNR", "permalinkId": 1, "resolved": null, "requestStatus": "OPEN", "requesterUserIds": [ "00ub0oNGTSWTBKOLGLNR" ], "requesterFieldValues": null, "approvals": [ { … }, { … } ], "actions": [ { … } ], "type": "ACCESS_REQUEST", "_links": { "requestType": { … }, "self": { … } } }