Requires
write_product
access scope. More access scope
The Receive Procurement API processes the receipt of procurement items by updating their quantities (received and rejected) and recording any rejection reasons. This API is used for managing procurement workflows and tracking item status upon receipt.This API is especially useful for:
- Recording quantities of items received and rejected during the procurement process.
- Providing reasons for rejected items to ensure transparency in procurement workflows.
- Tracking and updating the state of procurement items for better inventory management.
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 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"["invalid id"] } | 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
Path Parameters
Parameter | Type | Required | Example | Description |
---|---|---|---|---|
id | string | Yes | "382451985837728044" | The unique identifier of the procurement record. |
Body Parameters
Parameter | Type | Required | Example | Description |
---|---|---|---|---|
items | array | Yes | See below | The array of items to update with received and rejected quantities. |
items.procurement_item_id | string | Yes | "382453603865993516" | The unique identifier of the procurement item. |
items.received_quantity | integer | Yes | 5 | The quantity of the item that was successfully received. |
items.rejected_quantity | integer | Yes | 2 | The quantity of the item that was rejected. |
items.rejected_reason | string | No | "Damaged during shipping" | The reason for rejecting the item. |
Response Explanation
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 | ["Supplier not found"] | A list of errors encountered during the request processing. |
Field | Type | Example | Description |
---|---|---|---|
error | Array | "error": "store is not active" | Indicates an error encountered during the process. |
Request Examples
curl -X PATCH https://{shopdomain}.myshoplaza.com/openapi/2022-01/procurement/{id}/receive \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"items": [
{
"procurement_item_id": "382453603865993516",
"received_quantity": 5,
"rejected_quantity": 2,
"rejected_reason": "Damaged during shipping"
}
]
}'
Success Response Example
{}
Error Response Example
{
"errors": [
"Procurement not found"
]
}
}
{
"error": "Supplier not found"}
}
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). | invalid |
Unauthorized | The request is missing valid authentication credentials or the credentials provided are invalid. | Unauthorized | |
422 | Invalid Input | One or more of the following conditions apply: - procurement_item_id is invalid, missing or not found.- received_quantity is negative or exceeds pending quantity.- rejected_quantity is negative or exceeds pending quantity. | |
Duplicated procurement item id | API request contains multiple entries with the same procurement_item_id |