Update Procurement

🔒

Requires write_product access scope. More access scope

The Update Procurement API allows updating the details of an existing procurement record, such as its supplier, note, or other properties. This enables users to modify procurement data efficiently.This API is especially useful for:

  1. Updating supplier or notes information for procurement records.
  2. Managing and tracking procurement details over time.
  3. Reviewing procurement notes and updates for auditing.

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
idstringYes382454149549138220The unique identifier of the procurement record to update.

Body Parameters

ParameterTypeRequiredExampleDescription
procurementobjectNo
procurement.supplier_idstringNo"382453603865993516"The unique identifier of the supplier.
procurement.notestringNo"test note"Notes or additional details about the procurement.

Response Explanation

Successful Response

ParameterTypeExampleDescription
procurement.idstring"382451985837728044"The unique identifier of the procurement record.
procurement.procurement_snstring"00000002"The procurement serial number.
procurement.supplier_idstring"382411381263052204"The unique identifier of the supplier.
procurement.location_idstring"190035786870033452"The unique identifier of the location.
procurement.notestring"testaaa"Notes or additional details about the procurement.
procurement.stateinteger1The state of the procurement. Accepted values:1 (waiting for stock), 2 (partial receipt), 3 (complete receipt), 4 (cancelled).
procurement.pending_quantityinteger0The quantity of items still pending delivery.
procurement.received_quantityinteger0The quantity of items received.
procurement.rejected_quantityinteger0The quantity of items rejected.
procurement.transfer_quantityinteger0The quantity of items transferred.
procurement.created_bystring""The user who created the procurement record.
procurement.created_atstring"2024-05-21T08:47:39Z"The date and time when the procurement was created.
procurement.updated_atstring"2024-05-21T08:50:36Z"The date and time when the procurement 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["Supplier not found"]A list of errors encountered during the request processing.
FieldTypeExampleDescription
errorArray"error": "store is not active"Indicates an error encountered during the process.

Request Examples

curl -X PUT https://{shopdomain}.myshoplaza.com/openapi/2022-01/procurements/{id} \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
  "procurement": {
    "supplier_id": "382453603865993516",
    "note": "Updated procurement note"
  }
}'

Success Response Example

{
  "procurement": {
    "id": "382451985837728044",
    "procurement_sn": "00000002",
    "supplier_id": "382411381263052204",
    "location_id": "190035786870033452",
    "note": "testaaa",
    "state": 1,
    "pending_quantity": 0,
    "received_quantity": 0,
    "rejected_quantity": 0,
    "transfer_quantity": 0,
    "created_by": "",
    "created_at": "2024-05-21T08:47:39Z",
    "updated_at": "2024-05-21T08:50:36Z"
  }
}
}

Error Response Example

{
  "errors": [
    "Supplier not found"
  ]
}
}
{
  "error": "Supplier not found"}
}

Error Details

Status CodeMessagePossible ReasonExample Response
400Bad RequestInvalid input format or request structure (e.g., missing required fields or incorrect data types).{ "errors": [ "invalid procurement_id"]}
UnauthorizedThe request is missing valid authentication credentials or the credentials provided are invalid.Unauthorized
422Invalid or empty supplier_idmissing required supplier_id or supplier_id with incorrect UUID types{ "errors": [ "Supplier not found"]}
supplier_id is not foundProvidedsupplier_id is not found{ "errors": [ "Supplier not found"]}
404procurement_id is not foundProvidedprocurement_id is not found{ "errors": [ "Procurement not found"]}
Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!