---
title: "Activate/Deactivate Subcontractor"
method: PUT
path: "/subcontractors/{vendor_uid}/activate"
---

# Activate/Deactivate Subcontractor

`PUT /subcontractors/{vendor_uid}/activate`

## Request

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

Operates on Subcontractors, shown in the Zuper client app as "Subcontractor" (in every industry). Subcontractors share the exact same underlying schema and endpoints as Vendors / Suppliers; they're distinguished only by the `vendor_type` field (`SUB_CONTRACTOR` here) and the `/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
  - `message` string

## Changes

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

[Operation history](https://skmtc.dev/zuper/apis/zuper-pro-api/changes/subcontractors/: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)