Skip to main content
Feedback

Delete Quarantine Entry for Transaction

The Delete Quarantine Entry for Transaction operation deletes the quarantine entry associated with a specific transaction from a universe (domain) hosted in a specified repository under a specified account accessible to the authenticating user, provided the user is entitled to delete the entry.

note

Retrieval of the quarantine entry is subject to access restrictions imposed by the authenticating user’s tag-based entitlements.

To perform this operation, send an HTTP POST request to:

https://api.boomi.com/mdm/api/rest/v1/<accountID>/repositories/<repositoryID>/universes/<universeID>/quarantine/<transactionID>/delete

note

This operation requires the authenticating user to have the API Access privilege and the Delete Quarantine entitlement.

You can implement requests for this operation in processes using the HTTP Client connector, as demonstrated by example 2 in the sample process Hub: Delete Quarantine Entries, which you can install in your account from the process library in Integration.

Path parameters

accountID
ID of the account

repositoryID
ID of the repository

universeID
ID of the universe

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

Responses

  • 200 (OK) The body of the response is XML. The root element is <mdm:DeleteResponse>. Within that element <mdm:success> contains a Boolean value indicating the result of the delete operation — true for success.

    Sample response body for a successful operation:

    <mdm:DeleteResponse xmlns:mdm="http://mdm.api.platform.boomi.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <mdm:success>true</mdm:success>
    </mdm:DeleteResponse>

  • 400 (Bad Request) The authenticating user does not have the API Access privilege and the Delete Quarantine entitlement required for this operation. Sample response body:

    <error>
      <message>The authenticated user does not have access rights to this functionality</message>
    </error>

  • 400 (Bad Request) The universeID parameter value contains only space characters. Sample response body:

    <error>
      <message>The given universe id is blank.</message>
    </error>

  • 400 (Bad Request) repositoryID does not identify a repository under the specified account. Sample response body:

    <error>
      <message>Could not find containerAccount for container id 
        dbe797ff-6d6f-44e9-acd9-d77494a44b15 and account id account-123456</message>
    </error>

  • 403 (Forbidden) Authentication failure. Sample response body:

    <UserMessage id="error.user.login" type="error">
      <Data>Incorrect user name and password combination.</Data>
    </UserMessage>

  • 403 (Forbidden) One or more path parameter values are omitted. Sample response body:

    <UserMessage id="error.user.login" type="error">
      <Data>Incorrect user name and password combination.</Data>
    </UserMessage>

  • 403 (Forbidden) accountID does not identify an account accessible to the authenticating user. Sample response body:

    <UserMessage id="error.user.login" type="error">
      <Data>Incorrect user name and password combination.</Data>
    </UserMessage>

  • 404 (Not Found) universeID does not identify a universe hosted in the specified repository. 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 a quarantine entry in the specified universe. Sample response body:

    <error>
      <message>A quarantined entity version with id '42dbadd8-d226-4c4d-abe3-1dae8636e77a' does not exist.</message>
    </error>
On this Page