---
title: "New Vendor"
method: POST
path: "/v2/vendors"
tags: ["Routes", "Vendors"]
---

# New Vendor

`POST /v2/vendors`

This request creates a new Vendor.

name | String | Required | The name of the Vendor.
locationID | string | Required | The locationID of the Location the Vendor will be at.
email | string | Optional | The Vendor's email address.
contact | string | Optional | The Vendor's primary contact.
phone | string | Optional | The Vendor's phone number.
address | string | Optional | The Vendor's address.

## Response `201`

New Vendor

- object
  - `vendorID` string, utc-millisec

## 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.
- `409` — The request conflicts with the current state of the resource (e.g. a uniqueness constraint or a referenced parent that is in the wrong state).
- `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.net/limblecmms/apis/limble-api-v2.md) · [All operations](https://skmtc.net/limblecmms/apis/limble-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/limblecmms/limble-api-v2/revisions/eceb9442ed4d/schema)