POST /api/v1/apps/{appId}/credentials/secrets
Creates an OAuth 2.0 Client Secret object with a new active client secret. You can create up to two Secret objects. An error is returned if you attempt to create more than two Secret objects.
Note: This API lets you bring your own secret. If token_endpoint_auth_method of the app is
client_secret_jwt, then the minimum length ofclient_secretis 32 characters. If no secret is specified in the request, Okta adds a new system-generated secret.
Servers
- https://{yourOktaDomain}
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
appId |
String | Yes |
Application ID |
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 |
|---|---|---|---|
client_secret |
String | No |
The OAuth 2.0 client secret string |
status |
String | No |
Status of the OAuth 2.0 Client Secret Possible 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.