GET /api/v1/users/{id}
Retrieves a User from your Okta org.
Note: You can substitute
me
for theid
to fetch the current User linked to an API token or session cookie.
- The request returns the User linked to the API token that is specified in the Authorization header, not the User linked to the active session. Details of the Admin User who granted the API token is returned.
- When the end User has an active Okta session, it is typically a CORS request from the browser. Therefore, it's possible to retrieve the current User without the Authorization header.
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
orlogin shortname
, URL encode the request parameter to ensure that special characters are escaped properly. Logins with a/
character can only be fetched byid
due to URL issues with escaping the/
character.
Servers
- https://{yourOktaDomain}
Path parameters
Name | Type | Required | Description |
---|---|---|---|
id |
String | Yes |
|
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | No |
Specifies the media type of the resource. Optional 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
|
Query parameters
Name | Type | Required | Description |
---|---|---|---|
expand |
String | No |
An optional parameter to include metadata in the |
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.