Custom API Action
Use the Custom API Action card to make an authenticated request to the Okta Devices API.
See the Okta Devices API for more information on working directly with the Okta Devices API.
Options
Field | Definition | Type | Required |
---|---|---|---|
Request Type |
These are the 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 |
The URL address on the web server that you're attempting to call. Specify the relative URL as /{version}/{insert_remaining_URL}. You can specify query parameters in the relative URL using "?", or specify the query parameters as key and value pairs in the Query input. For example, for the Okta Devices API endpoint: https://{yourOktaDomain}/api/v1/devices, the Relative URL is /api/v1/devices. |
Text |
TRUE |
Headers |
Specify any headers required in addition to authorization or content-type, as the connector already handles those headers. |
Object |
FALSE |
Query |
Specify any additional query parameters that should be included as key and value pairs. For example, {"name":"something-urgent"}. |
Object |
FALSE |
Body |
Specify a request body in JSON format. This input is 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 |