Delete a Mapping Set.
curl --request DELETE \ --url https://auth.example.com/api/admin/identity-mapping/sets/example \ --header 'Authorization: Bearer <token>' \ --header 'Idempotency-Key: example'Deletes a Mapping Set with its versions. A set that is switched on is switched off and deleted by the same request, in one atomic batch: there is no separate step of switching it off first (the older DELETE /api/admin/field-mapping/field-mapping-sets/{fieldMappingSetId} still refuses an active set). The request is refused with 409 (reason referenced or scan_incomplete, with references) while a default, an app, a SAML provider, a credential profile, a federation trust source or SCIM still names the set, or when where it is used could not be checked everywhere; nothing is changed then. If-Match (optional) carries the content_version (or ETag) read last; another value is refused with 409 and nothing is deleted. Whether or not it is sent, the batch starts with a check that the set is still as this request read it (the version in use, else the one saved last): a save or a switch by someone else in between fails the check with 409 and deletes nothing. A platform set needs platform authority (403); a set another tenant owns, and one that does not exist, answer 404 (a repeat without an Idempotency-Key match after the set is gone is a 404; a repeat with the same key is answered with the stored answer). Idempotency-Key is required. One audit record (identity_mapping.set.deleted, with whether the set was switched on). Rate limited with the strict profile.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Mapping Set identifier.
Header Parameters
Section titled “Header Parameters ”Required replay-protection key retained for 15 minutes.
The content_version (or ETag) of the set as it was read.
Responses
Section titled “ Responses ”The Mapping Set was deleted.
object
Example
{ "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"}The change was refused: the Mapping Set is named somewhere (referenced), the version would not meet what the references need (would_break_references), or where it is used could not be checked everywhere (scan_incomplete).
object
object
Everything found, other tenants’ included.
True when a place held more rows than were read.
The first references the caller may see in full.
object
The tenant the reference is in. Absent for the platform’s own default.
The entity ID of the SAML partner the provider is configured for.
A federation trust source whose runtime resolution names the set.
A Mapping Set version the reference pins.
The compiled snapshot a credential profile version was published with.
When asked about a Destination Profile, the Mapping Set the reference is through.
References in other tenants the caller may not see, as counts only.
object
False when the other tenants’ Core databases were not read (the caller has no global authority): the counts then hold only what the Admin database knows.
object
object
Given only for the caller’s own tenant, or to a caller with global authority.
A fixed code (for example core_database_unavailable, no_such_table).
Only on would_break_references, the condition the version would fail.
object
Example
{ "error": "conflict", "reason": "referenced", "references": { "items": [ { "kind": "platform_default", "federationRole": "saml_idp", "role": "issuance" } ], "unscanned": { "items": [ { "area": "platform_settings" } ] }, "violation": { "code": "destination_profile_invalid" } }}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"}