PATCH /api/v1/org/privacy/oktaSupport/cases/{caseNumber}
Updates access to the org for an Okta Support case:
-
You can enable, disable, or extend access to your org for an Okta Support case.
-
You can approve Okta Support access to your org for self-assigned cases. A self-assigned case is created and assigned by the same Okta Support user.
Servers
- https://{yourOktaDomain}
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
caseNumber |
String | Yes |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
caseNumber |
String | No |
Okta Support case number |
selfAssigned |
Object | No |
Customer allows Okta Support access to self-assigned cases. Support cases are self-assigned when an Okta Support team member creates and assigns the case to themselves. |
selfAssigned.status |
String | No |
Okta Support access approval status for self-assigned cases Valid values:
|
subject |
String | No |
Subject of the support case |
impersonation |
Object | No |
Allows the Okta Support team to sign in to your org as an admin and troubleshoot issues |
impersonation.expiration |
String | No |
Expiration date of Okta Support access |
impersonation.status |
String | No |
Status of Okta Support access Valid values:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.