GET /api/v1/mappings
Lists all profile mappings in your organization with pagination. You can return a subset of profile mappings that match a supported sourceId and/or targetId.
The results are paginated according to the limit parameter. If there are multiple pages of results, the Link header contains a next link that should be treated as an opaque value (follow it, don't parse it).
The response is a collection of profile mappings that include a subset of the profile mapping object's parameters. The profile mapping object describes the properties mapping between an Okta User and an App User Profile using JSON Schema Draft 4.
Servers
- https://{yourOktaDomain}
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
limit |
Integer | No |
Specifies the number of results per page (maximum 200) Default value: 20 |
after |
String | No |
Mapping |
targetId |
String | No |
The UserType or App Instance |
sourceId |
String | No |
The UserType or App Instance |
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.