Skip to main content
Feedback

Delete Quarantined Entry for Transaction

The Delete Quarantined Entry for Transaction operation deletes a quarantine entry associated with a specified transaction from a specified universe (domain) under the authenticated account.

If the quarantined transaction is for a potential duplicate or a record already end-dated error, consider using the Reject operation instead since it sends a REJECT request to the source.

Basic authentication

To perform this operation using Basic auth, send an HTTP POST request with an empty request body to:

https://<base URL>/mdm/universes/<universeID>/quarantine/<transactionID>/delete

where base URL is the URL for your Hub cloud that hosts your repository.

JWT authentication

To perform this operation using JSON Web Token (JWT) auth, send an HTTP POST request with an empty request body to:

https://<base URL>/mdm/universes/<universeID>/quarantine/<transactionID>/delete?repositoryId=<repository ID>

You must have the following MDM privileges:

  • With the Advanced Security feature on your account:

    • MDM - Stewardship with Delete Quarantine Hub role entitlement for the queried repository
      or
    • MDM - Stewardship Management

  • Without Advanced Security:

    • MDM - Stewardship

Path parameters

universeID
ID of the universe

transactionID
ID of the transaction, which you can obtain from a Query Quarantine Entries operation.

Query parameters

repositoryId
ID of the repository. Case sensitive. Required with JWT authentication only. You can obtain the repository ID from the URL after navigating to the repository in the user interface.

Responses

  • 200 (OK) The operation deleted the retrieved quarantine entry, and an update request specifying a delete operation propagated on the channel of the contributing source.

  • 404 (Not Found) universeID does not identify a universe under the authenticated account. Sample response body:

    <error>
       <message>A universe with id 'ac11cc59-c77a-4afe-8c92-ed86a7daabec' does not exist.</message>
    </error>

  • 404 (Not Found) transactionID does not identify the quarantine entry in the specified universe. Sample response body:

    <error>
       <message>A quarantine entry associated with transaction ID '42dbadd8-d226-4c4d-abe3-1dae8636e77a' does not exist.</message>
    </error>

  • 401 (Invalid Credentials) JWT auth token is expired. Sample response body:

    <body>
    <h2>HTTP ERROR 401</h2>
       <p>Problem accessing /mdm/universes. Reason:
       <pre>Invalid credentials.</pre>
    </p>
    </body>

  • 403 (You do not have permissions to access this resource) User does not have the required MDM privilege to perform the action. Applicable to JWT auth only. Sample response body:

    <error><message>You do not have permissions to access this resource.</message></error>
On this Page