PUT /api/v1/apps/{appId}/federated-claims/{claimId}
Replaces a claim that will be included in tokens produced by federation protocols (for example: OIDC id_tokens or SAML Assertions)
Servers
- https://{yourOktaDomain}
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
claimId |
String | Yes |
The unique |
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 |
|---|---|---|---|
id |
String | No |
The unique ID of the federated claim |
created |
String | No |
Timestamp when the federated claim was created |
name |
String | No |
The name of the claim to be used in the produced token |
expression |
String | No |
The Okta Expression Language expression to be evaluated at runtime |
lastUpdated |
String | No |
Timestamp when the federated claim was updated |
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.