Status codes
Error response structure
All errors return a consistent JSON structure:errors array with field-level details:
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Starting August 25, 2026, creating a product requires a universal identifier (EAN, UPC, GTIN or ASIN) plus title, description and condition. See what changes.
HTTP status codes and error structures returned by the nocnoc API.
| Code | Meaning | When it happens |
|---|---|---|
200 | OK | Request succeeded. |
201 | Created | Resource created successfully. |
400 | Bad Request | Invalid payload, missing required fields, or duplicate SKU. |
401 | Unauthorized | Missing or invalid API key. |
404 | Not Found | The requested resource does not exist. |
409 | Conflict | The request conflicts with the current state of the resource. |
415 | Unsupported Media Type | Missing Content-Type: application/json header. |
500 | Internal Server Error | An unexpected error occurred on nocnoc’s side. |
{
"code": 401,
"message": "Unauthorized"
}
errors array with field-level details:
{
"code": 400,
"message": "Invalid Request Payload.",
"errors": [
"Sku should be between 1 character minimum and 45 characters maximum.",
"Brand should be between 1 character minimum and 45 characters maximum."
]
}