Update Supplier

🔒

Requires create_product access scope. More access scope

The Update Supplier API updates the details of an existing supplier by its unique identifier (id). This endpoint is useful for modifying supplier information such as the URL, allowing users to maintain accurate supplier data.This API is especially useful for:

  1. Updating supplier information for procurement or inventory purposes.
  2. Ensuring supplier records are up-to-date with accurate data.

Note: The operation is scoped to a specific shop, identified by its unique domain prefix (shopdomain), ensuring all updates 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"["invalid id"] }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

Path Parameters

ParameterTypeRequiredExampleDescription
idstringYes382454149549138220Supplier ID to update.

Body Parameters

ParameterTypeRequiredExampleDescription
supplierobjectYesObject containing supplier details.
supplier.urlstringYes"https://shoplazza.com"Updated URL of the supplier.

Response Explanation

Successful Response

FieldTypeExampleDescription
supplierobjectObject containing supplier details.
supplier.idstring"382453603865993516"Unique identifier of the supplier.
supplier.titlestring"example supplier"Name of the supplier.
supplier.urlstring"https://shoplazza.com"URL associated with the supplier.
supplier.created_atstring"2024-05-21T08:54:04Z"Timestamp when the supplier was created.
supplier.updated_atstring"2024-05-21T08:54:04Z"Timestamp when the supplier was last updated.

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["invalid id"]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 PUT \
     --url https://{shopdomain}.myshoplazza.com/openapi/2022-01/suppliers/{id} \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'access-token: <YOUR_ACCESS_TOKEN>' \
     --data '{
         "supplier": {
             "url": "https://shoplazza.com"
         }
     }'

Success Response Example

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

Error Response Example

{
  "errors": [
    "invalid id"
  ]
}
{
  "error": "store is not active"
}

Error Details

Status CodeMessagePossible ReasonExample Response
400Bad RequestInvalid input format or request structure (e.g., missing required fields or incorrect data types).Bad Request
UnauthorizedThe request is missing valid authentication credentials or the credentials provided are invalid.Unauthorized
empty supplier_idmissing required supplier_id{ "errors": [ "invalid id"]}
404Supplier not foundThe supplier ID provided in the request does not exist.{ "errors": [ "Supplier not found"]}
Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!