Custom API Action
Use the Custom API Action to make an authenticated request to the Okta API. See Okta API Reference for more information on working directly with the Okta API.
Options
Field | Definition | Type | Required |
---|---|---|---|
Request Type |
These are supported HTTP request methods, or HTTP verbs, in a custom API call (see HTTP request methods).
|
Dropdown | TRUE |
Input
Field | Definition | Type | Required |
---|---|---|---|
Relative URL |
URL address on the web server to which you are attempting to interact. Specify the relative URL as A relative URL must have a leading / character. For example, for the Okta API endpoint:
See Okta API. |
String | TRUE |
Headers | Specify any headers required in addition to authorization or content-type (these are already handled by this connector). | Object | FALSE |
Query | Specify any additional query parameters that should be included in object format (key value pairs). | Object | FALSE |
Body | Specify a request body in JSON format. Only available for POST , PUT , and PATCH requests. |
Object | FALSE |
Output
Field | Definition | Type |
---|---|---|
Response | ||
Status Code | Result of the operation. The connector returns an HTTP status code that indicates whether the action taken by the card succeeded or failed. For example:
For a full list of possible status codes, see HTTP status codes. |
Number |
Headers | Detailed context for the status code, unrelated to the output body. Response headers depend on your selected HTTP request option. Not all headers are response headers. This is similar to {"Content-type":"application/json"}. | Object |
Body |
Data returned from your selected HTTP request.
For example, the data from a GET request. |
Object |