Pagination, errors & limits

Pagination

List endpoints accept:

Parameter	Description
`page`	Page number (1-based)
`page_size`	Items per page (max enforced per API, typically 100)

Responses include items and pagination metadata (total, page, page_size).

curl -s "https://api.catazenta.com/v1/products?page=2&page_size=50" \
  -H "Authorization: Bearer ${TOKEN}"

Code	Meaning	Action
400	Validation / bad input	Fix request body or query params
401	Missing or expired token	Login or refresh token
403	Forbidden	Check RBAC permission for user
404	Not found	Verify UUID and tenant
409	Conflict	Retry with current state or resolve duplicate
422	Business rule violation	Read `error.message`; fix catalog rules
429	Rate limited	Back off and retry with exponential delay
500	Server error	Retry; contact support if persistent

{
  "success": false,
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Human-readable message",
    "details": []
  }
}

Log code and message in your integration for support tickets.

Area	Guidance
Interactive API	Avoid tight loops; use pagination and batch jobs for bulk work
Export/import jobs	Preferred for large catalogs — async, retriable per item
Amazon SP-API	Connector respects Amazon quotas; large jobs may run longer
429 responses	Wait and retry; do not spin hundreds of parallel requests

For bulk updates, use jobs or MCP tools that batch internally rather than thousands of sequential GETs.

Some write operations support idempotency keys — see Integration and Job APIs in the OpenAPI specs.