# Deactivate a partner

`DELETE /lokta-lms/api/v1/sourcing-partners/{partnerId}/activation`

Deactivates a sourcing partner, with a reason.

Moves `active` → `inactive`. **Nothing is deleted**: existing attributions, terms, documents and invoices are untouched and stay readable; only new attribution is refused. Standing a partner down is not the same as pretending it never introduced anyone.

`reason` is required here though optional on activation, and the asymmetry is deliberate: activation is the expected end of onboarding, while deactivation ends a commercial relationship and the "why" is what somebody looks for months later.

## Parameters
- `partnerId` (path, string, required)
- `Idempotency-Key` (header, string): Per-intent key

## Request body (application/json)
- `reason` (string, required): Why the partner is being deactivated. Recorded in the status history.

## Responses
- `default`: default response

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

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