---
title: "Get Part Vendor Associations"
method: GET
path: "/v2/parts/vendors/associations"
tags: ["Routes", "Parts", "Vendor Associations"]
---

# Get Part Vendor Associations

`GET /v2/parts/vendors/associations`

Returns a paginated list of vendor-part associations for the customer.

**Note:** this endpoint supports both cursor-based and page-based pagination. Please refer to the [**Pagination**](#pagination) section for more information.

Return data description

Property: relationID, Description: The unique ID of this vendor-part association.
Property: partID, Description: The ID of the associated part.
Property: vendorID, Description: The ID of the associated vendor.
Property: vendorPartNumber, Description: The vendor's part number for this part, if provided.
Property: partPrice, Description: The vendor's price for this part, if provided.
Property: createdAt, Description: Unix timestamp of when this association was created.
Property: updatedAt, Description: Unix timestamp of when this association was last updated.
Property: partName, Description: The name of the associated part.
Property: number, Description: The part's internal part number.
Property: locationID, Description: The ID of the location this part belongs to.
Property: vendorName, Description: The name of the associated vendor.

## Query parameters

- `parts` string
- `vendors` string
- `vendorPartNumber` string
- `vendorName` string
- `start` integer
- `end` integer
- `cursor` integer
- `limit` integer
- `orderBy` string
- `page` integer

## Response `200`

Get Part Vendor Associations

- object[]
  - `relationID` integer
  - `partID` integer
  - `vendorID` integer
  - `vendorPartNumber` string
  - `partPrice` number
  - `createdAt` integer
  - `updatedAt` integer
  - `partName` string
  - `number` string
  - `locationID` integer
  - `vendorName` string

## 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.
- `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/20801e23f7f2/schema)