GET /api/v1/users/{id}

Retrieves a User from your Okta org.

Note: You can substitute me for the id to fetch the current User linked to an API token or session cookie.

Note: Some browsers block third-party cookies by default, which disrupts Okta functionality in certain flows. See Mitigate the impact of third-party cookie deprecation.

Note: When fetching a User by login or login shortname, URL encode the request parameter to ensure that special characters are escaped properly. Logins with a / character can only be fetched by id due to URL issues with escaping the / character.

Servers

Path parameters

Name Type Required Description
id String Yes

id, login, or login shortname (as long as it is unambiguous) of user

Request headers

Name Type Required Description
Content-Type String No

Specifies the media type of the resource. Optional okta-response value can be included for performance optimization.

Complex DelAuth configurations may degrade performance when fetching specific parts of the response, and passing this parameter can omit these parts, bypassing the bottleneck.

Enum values for okta-response:

  • omitCredentials: Omits the credentials subobject from the response.
  • omitCredentialsLinks: Omits the following HAL links from the response: Change Password, Change Recovery Question, Forgot Password, Reset Password, Reset Factors, Unlock.
  • omitTransitioningToStatus: Omits the transitioningToStatus field from the response.

Query parameters

Name Type Required Description
expand String No

An optional parameter to include metadata in the _embedded attribute. Valid value: blocks

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. 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.
  3. Click Test request to test run your request to the API and see the API's response.