Requires
create_product
access scope. More access scope
The Create Supplier API allows users to add a new supplier to the system. This API accepts detailed supplier information and stores it for inventory and procurement management.This API is especially useful for:
- Adding new suppliers for inventory management and procurement purposes.
- Maintaining a directory of external vendors or service providers.
Note: The operation is scoped to a specific shop, identified by its unique domain prefix (shopdomain
), ensuring all actions are applied to the correct store.
Public Request Parameters
Parameter Name | Type | Required | Parameter Location | Parameter Value | Description |
---|---|---|---|---|---|
Access-Token | String | Yes | Header | Bx-_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-Type | String | Yes | Header | application /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 Name | Type | Mandatory | Parameter Location | Example Value | Description |
---|---|---|---|---|---|
error | String | No | Response 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" } . |
errors | Array | No | Response Body | { "errors"["ProductId is required"] } | A list of errors that occurred during the request processing. Example: { "errors": [ "No Context" ] } . |
Request-Id | String | Yes | Header | Bx-_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
Body Parameters
Parameter | Type | Required | Example | Description |
---|---|---|---|---|
supplier | object | Yes | Object containing supplier details. | |
supplier.title | string | Yes | "example supplier" | Supplier's name, must be unique within the store. |
supplier.url | string | No | "https://shoplazza.com" | URL associated with the supplier. |
Response Explanation
Successful Response
Field | Type | Example | Description |
---|---|---|---|
supplier | object | Object containing supplier details. | |
supplier.id | string | "382453603865993516" | Unique identifier of the supplier. |
supplier.title | string | "example supplier" | Name of the supplier. |
supplier.url | string | "https://shoplazza.com" | URL associated with the supplier. |
supplier.created_at | string | "2024-05-21T08:54:04Z" | Timestamp when the supplier was created. |
supplier.updated_at | string | "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.
Field | Type | Example | Description |
---|---|---|---|
errors | Array | [ "Duplicated supplier name"] | A list of errors encountered during the request processing. |
Field | Type | Example | Description |
---|---|---|---|
error | Array | "store is not active" | Indicates an error encountered during the process. |
Request Examples
curl --request POST \
--url https://{shopdomain}.myshoplazza.com/openapi/2022-01/suppliers \
--header 'accept: application/json' \
--header 'access-token: <YOUR_ACCESS_TOKEN>' \
--header 'content-type: application/json' \
--data '{
"supplier": {
"title": "example supplier",
"url": "https://shoplazza.com"
}
}'
Success Response Example
{
"supplier": {
"id": "382453603865993516",
"title": "example supplier",
"url": "https://shoplazza.com",
"created_at": "2024-05-21T08:54:04Z",
"updated_at": "2024-05-21T08:54:04Z"
}
}
Error Response Example
{
"errors": [
"Duplicated supplier name"
]
}
{
"error": "store is not active"
}
Error Details
Status Code | Message | Possible Reason | Example Response |
---|---|---|---|
400 | Bad Request | Invalid input format or request structure (e.g., missing required fields or incorrect data types). | Bad Request |
Unauthorized | The request is missing valid authentication credentials or the credentials provided are invalid. | Unauthorized | |
422 | title is existing | The title provided is existing. | { "errors": [ "Duplicated supplier name"]} |
500 | title is a required field | missing required title | { "errors": ["title is a required field"] } |