---
title: "Delete Part Vendor Association"
method: DELETE
path: "/v2/parts/vendors/associations/{relationID}"
tags: ["Routes", "Parts", "Vendor Associations"]
---

# Delete Part Vendor Association

`DELETE /v2/parts/vendors/associations/{relationID}`

## Request

- Base URL: `{{server}}:{{port}}`
- URL: `{{server}}:{{port}}/v2/parts/vendors/associations/{relationID}`
- Auth: HTTP basic
- TypeScript: <https://skmtc.dev/limblecmms/apis/limble-api-v2/docs/v2/parts/vendors/associations/:relationID/delete.ts> (a function with typed inputs; its response is checked against the schema)

Deletes a vendor-part association by its `relationID`. Only manually created associations (associationType: `manual`) can be deleted through this endpoint.

Returns `204 No Content` on success. Returns `404 Not Found` if the association does not exist or does not belong to your account.

## Response `204`

Delete Part Vendor Association

## Other responses

- `400`: The request was malformed — either invalid JSON syntax or a validation failure (missing required field, wrong type, etc.).
- `401`: No `Authorization` header was provided on the request.
- `403`: The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `404`: The vendor-part association does not exist.
- `429`: The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500`: An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

[API](https://skmtc.dev/limblecmms/apis/limble-api-v2.md) - [All operations](https://skmtc.dev/limblecmms/apis/limble-api-v2/llms.txt) - [OpenAPI document](https://skmtc.dev/limblecmms/apis/limble-api-v2/revisions/488d795f846f?raw)