Getting Started

Error handling

The ResellerClub API returns standard HTTP status codes and structured error responses.

Common status codes

Code	Meaning
`200`	Success
`400`	Bad request — invalid parameters or body
`401`	Unauthorized — missing or invalid credentials
`403`	Forbidden — valid credentials but insufficient permissions
`404`	Not found — resource does not exist
`500`	Internal server error
`503`	Service unavailable

A typical error body includes:


Code
{
  "message": "Please add your user id an api key in the header.",
  "path": "/customers/33",
  "status": 401
}

Symptom	Likely cause
`401 Unauthorized`	Missing or invalid authentication headers
`403 Forbidden`	Valid credentials but access denied for this resource

Ensure you have clicked Authorize in the playground and entered the correct credentials before testing endpoints.

Getting Started

The ResellerClub API returns standard HTTP status codes and structured error responses.

Code	Meaning
`200`	Success
`400`	Bad request — invalid parameters or body
`401`	Unauthorized — missing or invalid credentials
`403`	Forbidden — valid credentials but insufficient permissions
`404`	Not found — resource does not exist
`500`	Internal server error
`503`	Service unavailable

A typical error body includes:


Code
{
  "message": "Please add your user id an api key in the header.",
  "path": "/customers/33",
  "status": 401
}

Symptom	Likely cause
`401 Unauthorized`	Missing or invalid authentication headers
`403 Forbidden`	Valid credentials but access denied for this resource

Ensure you have clicked Authorize in the playground and entered the correct credentials before testing endpoints.