# Detach a loan from its partner

`DELETE /lokta-lms/api/v1/loan-attributions/{id}`

Detaches a loan from its partner, which corrects the loan to Direct.

Equivalent to `POST …/corrections` with `partner_id: null`, and it behaves identically.

This is a correction, not a deletion. `reason` is required in the body, the change lands in the loan's attribution trail, and the trail outlives the row; read it at `GET /v1/loan-attribution-corrections?loan_id=…`, which keeps answering after the attribution is gone.

Offered because "remove this partner from the loan" is how an operator thinks about it, while the API models it as the loan becoming Direct. Same event, two vocabularies; one implementation.

## Parameters
- `id` (path, string, required): Opaque attribution id, spa_…
- `Idempotency-Key` (header, string): Per-intent key

## Request body (application/json)
- `reason` (string, required): Why the loan is being detached.

## Responses
- `default`: default response

## Example request (cURL)
```bash
curl -X DELETE \
  'https://default.lokta.tech/lokta-lms/api/v1/loan-attributions/{id}' \
  -u '{username}:{password}' \
  -H 'Tenant-Identifier: default'
```

Interactive: https://developer.lokta.ai/reference#operation/detach