# Delete Information
source: https://developer.mastercard.com/agent-suite-for-merchants/documentation/use-cases/delete-database-information/index.md

👉 Replace the generic delete flows, example endpoints, and Mermaid diagram with the real delete or archival behavior for your service. Update the Mermaid `basename` to the correct sequence file in `data/mermaid/`, and replace each Swagger embed with the real spec file and delete or archive endpoint. If records are archived or soft-deleted instead of removed, explain that here.

Delete information about a resource record, transaction record, or administrative record.

### Preconditions {#preconditions}

* The record must already exist in the system.
* Before deleting it, keep the identifier from a previous create, retrieve, or search response.

These deletion use cases typically appear at the end of the lifecycle, after a record has been created, reviewed, and, if necessary, updated. Use them only when a resource should be permanently removed from the system.

### Example sequence {#example-sequence}

Diagram pet-deletion

## Delete a Resource Record {#delete-a-resource-record}

Use the delete endpoint to permanently remove a resource record from the system. In the sample specification, this is represented by `DELETE /pets/{pet_id}`.

### Delete resource request {#delete-resource-request}

An operator permanently removes a record that is no longer needed. This action cannot be undone, so services commonly require role-based authorization and an exact identifier.

See the endpoint structure used by the sample specification:


API Reference: `DELETE /pets/{pet_id}`

<br />

## Delete a Transaction Record {#delete-a-transaction-record}

Use the transaction delete endpoint when a downstream workflow record must be removed entirely. In the sample specification, this is represented by `DELETE /adoptions/{adoption_id}`.

### Delete transaction request {#delete-transaction-request}

An operator permanently removes a transaction record that is no longer valid or required. This action cannot be undone and should usually be limited to privileged users.

See the endpoint structure used by the sample specification:


API Reference: `DELETE /adoptions/{adoption_id}`

<br />

## Delete an Administrative Record {#delete-an-administrative-record}

Use the administrative delete endpoint to remove an operational record that should no longer exist in the platform. In the sample specification, this is represented by `DELETE /employees/{username}`.

### Delete administrative record request {#delete-administrative-record-request}

An administrator offboards or removes an internal record by its unique key. As with other delete flows, this action is permanent and should be governed carefully.

See the endpoint structure used by the sample specification:


API Reference: `DELETE /employees/{username}`

<br />

## Error Resolution {#error-resolution}

For details on error resolution please visit our [Code and Formats](https://developer.mastercard.com/agent-suite-for-merchants/documentation/code-and-formats/index.md) section.