---
title: "Activate/Deactivate Vendor"
method: PUT
path: "/vendors/{vendor_uid}/activate"
---

# Activate/Deactivate Vendor

`PUT /vendors/{vendor_uid}/activate`

## Request

- Base URL: `https://dc-region.zuperpro.com/api`
- URL: `https://dc-region.zuperpro.com/api/vendors/{vendor_uid}/activate`
- Auth: API key in header `x-api-key`

Operates on Vendors. In the Zuper client app this module is labeled "Vendor" for most companies, and "Supplier" for companies in the roofing industry — the API and data shape are identical either way. Vendors and Subcontractors share the exact same underlying schema and endpoints; they're distinguished only by the `vendor_type` field (`VENDOR` here) and the `/vendors` vs `/subcontractors` route prefix. Activates or deactivates the record based on `is_active`.

## Path parameters

- `vendor_uid` string, required

## Request body

- object
  - `is_active` boolean, required

## Response `200`

200

- object
  - `type` 'SUCCESS'
  - `title` string: Exact wording is "Vendor" for most companies, or "Supplier" for roofing-industry companies.
  - `message` string: Exact wording is "Vendor" for most companies, or "Supplier" for roofing-industry companies.

## Changes

- **2026-11-03** `3c21bc232e16`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zuper/apis/zuper-pro-api/changes/vendors/:vendor_uid/activate/put.md)

---

[API](https://skmtc.dev/zuper/apis/zuper-pro-api.md) - [All operations](https://skmtc.dev/zuper/apis/zuper-pro-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zuper/apis/zuper-pro-api/revisions/3c21bc232e16?raw)