List Suppliers

🔒

Requires read_product access scope. More access scope

The List Suppliers API allows users to retrieve a list of suppliers with optional filtering by specific supplier IDs. The API supports pagination to handle large datasets and returns detailed information about suppliers, including their metadata.This API is especially useful for:

  1. Fetching a list of suppliers for inventory and procurement purposes.
  2. Retrieving specific suppliers by their unique IDs.
  3. Supporting pagination for managing large supplier datasets.

Note: The operation is scoped to a specific shop, identified by its unique domain prefix (shopdomain), ensuring all queries are applied to the correct store.

Public Request Parameters

Parameter NameTypeRequiredParameter LocationParameter ValueDescription
Access-TokenStringYesHeaderBx-_5aV
eXNwl-4AB98s5xLV
yg0fNzGf

MuTpqtlBA
Used to authenticate API requests. Obtain an access token from the Access Token Guide.
Pass it in the Authorization header for every request.
Content-TypeStringYesHeaderapplication
/json
Indicates the media type of the request body. It tells the server how to parse the request and
the client how to interpret the response. For more details, visit Content-Type.

Public Response Parameters

Parameter NameTypeMandatoryParameter LocationExample ValueDescription
errorStringNoResponse Body{ "error": "store is not active" }Indicates an error encountered during the process. This field typically appears when the Access Token is missing or invalid. Example: { "error": "store is not active" }.
errorsArrayNoResponse Body{ "errors"["ProductId is required"] }A list of errors that occurred during the request processing. Example: { "errors": [ "No Context" ] }.
Request-IdStringYesHeaderBx-_5aV
eXNwl-4AB98s5xLV
yg0fNzGf

MuTpqtlBA
A unique identifier for each request. It helps in identifying and debugging specific requests.

Error and Errors Clarification:

Added explanation that the error and errors fields are currently dependent on the API implementation, with plans for future unification.

Request Parameters

Query Parameters

ParameterTypeRequiredExampleDescription
idsarray of stringsNo["382453603865993516"]A list of supplier IDs to filter results. Empty value retrieves all suppliers.
pageint32No1Page number of results to retrieve, starting from 1. Must be a positive integer.
limitint32No10Maximum number of results per page. Acceptable range: 1 to 100.

Response Explanation

Successful Response

FieldTypeExampleDescription
suppliersarrayList of supplier objects.
suppliers.idstring"382453603865993516"Unique identifier of the supplier.
suppliers.titlestring"example supplier"Name of the supplier.
suppliers.urlstring"https://shoplazza.com"URL associated with the supplier.
suppliers.created_atstring"2024-05-21T08:54:05Z"Timestamp when the supplier was created.
suppliers.updated_atstring"2024-05-21T08:54:05Z"Timestamp when the supplier was last updated.
countint1Total number of suppliers retrieved.

Error Response

Error responses in the API can be represented using two different fields: errors and error. Both fields provide details about issues encountered during request processing. Below is an explanation of the fields with their respective examples and descriptions.

FieldTypeExampleDescription
errorsArray[ "Duplicated supplier name"]A list of errors encountered during the request processing.
FieldTypeExampleDescription
errorArray "store is not active"Indicates an error encountered during the process.

Request Examples

curl --request GET \
     --url https://{shopdomain}.myshoplazza.com/openapi/2022-01/suppliers?ids=382453603865993516&page=1&limit=10 \
     --header 'accept: application/json' \
     --header 'access-token: <YOUR_ACCESS_TOKEN>'

Success Response Example

{
  "suppliers": [
    {
      "id": "382453603865993516",
      "title": "example supplier",
      "url": "https://shoplazza.com",
      "created_at": "2024-05-21T08:54:05Z",
      "updated_at": "2024-05-21T08:54:05Z"
    }
  ],
  "count": 1
}

Error Response Example

{
  "errors": [
     "Context Error"
  ]
}
{
  "error": "store is not active"
}

Error Details

Status CodeError MessagePossible CauseExample Response
400Bad RequestThe request contains invalid input or is missing required fields.
UnauthorizedThe request is missing valid authentication credentials or the credentials provided are invalid.
Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!