> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daya.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete recipient

> Soft-delete a recipient

## Overview

Soft-delete a recipient. The recipient will no longer appear in list results and cannot be used for new transfers or settlement destinations. This action is irreversible.

## Authentication

<ParamField header="X-Api-Key" type="string" required>
  Your merchant API key
</ParamField>

## Path Parameters

<ParamField path="id" type="string" required>
  Recipient ID (UUID)

  **Example:** `750e8400-e29b-41d4-a716-446655440000`
</ParamField>

## Request Example

<CodeGroup>
  ```bash cURL theme={null}
  curl --request DELETE \
    --url https://api.daya.co/v1/recipients/750e8400-e29b-41d4-a716-446655440000 \
    --header 'X-Api-Key: YOUR_API_KEY'
  ```

  ```javascript JavaScript theme={null}
  const response = await fetch(
    "https://api.daya.co/v1/recipients/750e8400-e29b-41d4-a716-446655440000",
    {
      method: "DELETE",
      headers: {
        "X-Api-Key": "YOUR_API_KEY",
      },
    }
  );

  // 204 No Content on success
  if (response.status === 204) {
    console.log("Recipient deleted successfully");
  }
  ```
</CodeGroup>

## Response

A successful deletion returns a `204 No Content` response with an empty body.

### Success Response

<ResponseExample>
  ```text 204 No Content theme={null}
  (empty response body)
  ```
</ResponseExample>

## Error Responses

<ResponseExample>
  ```json 400 Bad Request - Invalid UUID theme={null}
  {
    "error": {
      "code": "validation_failed",
      "message": "Invalid UUID format"
    }
  }
  ```

  ```json 404 Not Found theme={null}
  {
    "error": {
      "code": "not_found",
      "message": "Recipient not found"
    }
  }
  ```

  ```json 401 Unauthorized theme={null}
  {
    "error": {
      "code": "unauthorized",
      "message": "Invalid or missing API key"
    }
  }
  ```
</ResponseExample>

## Notes

* This is a soft-delete operation. The recipient record is retained internally but is no longer accessible via the API.
* Any in-progress movements referencing this recipient will not be affected.
* Deleting a recipient that has already been deleted will return a `404 Not Found` error.

## Next Steps

<CardGroup cols={2}>
  <Card title="Create recipient" icon="plus" href="/api-reference/recipients/create-recipient">
    Create a new recipient
  </Card>

  <Card title="List recipients" icon="list" href="/api-reference/recipients/list-recipients">
    Retrieve all saved recipients
  </Card>
</CardGroup>