---
title: "Deactivate a supplier by identifier"
method: DELETE
path: "/public/v2/suppliers/sites"
tags: ["Suppliers - Sites"]
---

# Deactivate a supplier by identifier

`DELETE /public/v2/suppliers/sites`

Deactivate (disconnect) a supplier from your organization using any identifier (supplier ID, customer ID, own site ID, or Prewave ID).

This unified endpoint allows you to deactivate suppliers using any type of identifier. You can search by one or more ID types, but **exactly one supplier must be found** for the deletion to proceed.

**Related Endpoints:**
- To find suppliers by identifier before deactivating, use `GET /public/v2/suppliers/sites/find-by-identifier`.
- To create a new supplier, use `POST /public/v2/suppliers/sites`.
- To manage supplier identifiers, use `POST /public/v2/suppliers/sites/identifiers` or `DELETE /public/v2/suppliers/sites/identifiers`.

**Search Parameters:**
- `supplierId` (optional): Search by supplier ID
- `customerId` (optional): Search by customer ID
- `ownId` (optional): Search by own site ID
- `prewaveId` (optional): Search by Prewave ID
- `source` (optional): Filter by source system (applies to supplierId, customerId, ownId only)

**Search Behavior:**
- **Multiple ID types**: If you provide multiple ID parameters, the endpoint searches for suppliers matching **ANY** of the provided IDs (OR logic)
- **Exactly one match required**: The supplier must be uniquely identified. Returns `400 Bad Request` if zero or multiple suppliers are found
- **Source filtering**: If `source` is provided, only IDs with that exact source are matched

**What happens when you deactivate a supplier:**

1. **Identifier Deactivation**: All supplier identifier connections are deactivated
2. **Collection Management**: The supplier target is moved to an inactive collection
3. **Audit Trail**: All changes are recorded with user information and timestamps

**Important Notes:**
- At least one ID parameter must be provided
- Exactly one supplier must match the search criteria
- This is a soft deletion (data is preserved but marked inactive)
- The operation can be reversed using the reactivate endpoint

**Required Permission**: `ACCESS_PUBLIC_REMOVE_TARGET`

## Query parameters

- `supplierId` string
- `customerId` string
- `ownId` string
- `prewaveId` integer
- `source` string

## Response `204`

Supplier successfully deactivated (No Content)

## Other responses

- `400` — 400 Bad Request - Invalid request. Either no ID parameters provided, or multiple suppliers found.
- `403` — 403 Forbidden - Authentication or authorization failure. This status code is returned when: (1) the request lacks valid authentication credentials (missing or invalid X-Auth-Token header), or (2) the authenticated user does not have the required permission to access this resource.
- `404` — 404 Not Found - No supplier found matching the provided identifiers.
- `429` — 429 Too Many Requests - API rate limit exceeded. The request has been rejected because the rate limit for this endpoint has been exceeded. Default rate limits: GET requests - 100 per 10 seconds, 500 per minute; POST/PUT/PATCH/DELETE requests - 20 per 10 seconds, 100 per minute. For increased access, please contact customer success.
- `500` — 500 Internal Server Error - An unexpected error occurred on the server. The request may or may not have been processed.

---

[API](https://skmtc.net/prewave/apis/public-prewave-api.md) · [All operations](https://skmtc.net/prewave/apis/public-prewave-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/prewave/public-prewave-api/revisions/466169815b78/schema)