Commerce
Update product limits
PUT{baseUrl}/v1.0/commerce/product-limits/{CompanyLocationKey}
Updates product limits for multiple products in a single batch request.
Auth
x-api-keyField | Type | Required |
|---|---|---|
| CompanyLocationKey | string | Yes |
application/jsonField | Type | Required |
|---|---|---|
| productLimits[] | object[] | Yes |
| productLimits[]. | string | Yes |
| productLimits[]. | number | No |
| productLimits[]. | string | Yes |
Status | When |
|---|---|
| 200 | Success |
| 400 | Bad Request |
| 401 | Unauthorized |
| 500 | An unexpected error occurred on the server. |
Field | Type | Required | Description |
|---|---|---|---|
| data | object | null | No | |
| data. | boolean | No | Whether the operation succeeded |
| data. | string | No | Human-readable description of the result or failure reason |
| errors[] | object[] | null | No | One or more errors describing why the request failed. Absent ( |
| errors[]. | string | null | No | Human-readable explanation of the error. Intended for display to end users or logs. Wording is not stable and should not be branched on. |
| errors[]. | string | null | No | Machine-readable, stable error identifier. Consumers should branch on this value
rather than on Description. See |
| paging | object | null | No | Paging metadata for list endpoints. Absent on single-item responses. |
| paging. | integer | No | |
| paging. | integer | No | |
| paging. | integer | No |
Example 200 response
{
"data": {
"success": true,
"message": "string"
},
"errors": [
{
"description": "string",
"errorId": "string"
}
],
"paging": {
"limit": 0,
"start": 0,
"total": 0
}
}