List Mapping Sets.
curl --request GET \ --url https://auth.example.com/api/admin/identity-mapping/sets \ --header 'Authorization: Bearer <token>'Lists the Mapping Sets the calling tenant owns together with the platform’s, which every tenant can read, in the form of the Mapping Set facade: whether each is switched on (enabled), its owner (tenant or platform), the version in use (active_version_id; null when the set is off) and content_version. The content itself is read with GET /api/admin/identity-mapping/sets/{id}. A set another tenant owns is never listed. Rate limited with the strict profile.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”The Mapping Sets of the tenant and the platform’s.
object
The fields every answer about a Mapping Set carries. The detail and the save answers add to them, so the schema is open.
object
Whether an activation is in use.
The label of the version the set is now (the one in use, else the last saved).
What the set is now: the ID of the version in use, else of the version saved last, else none. Changes with every save; sent as If-Match.
Example
{ "sets": [ { "owner": "tenant" } ]}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}