Skip to main content

​
Error hierarchy

Everything the SDK throws extends CestoError. Server responses become typed APIError subclasses; transport problems become connection errors. All classes are exposed on the Cesto client for instanceof checks. 
import { Cesto } from '@cesto/sdk';

try {
  await cesto.products.get('missing-slug');
} catch (err) {
  if (err instanceof Cesto.NotFoundError) {
    // 404
  } else if (err instanceof Cesto.AuthenticationError) {
    // 401 — invalid / missing / revoked key
  } else if (err instanceof Cesto.RateLimitError) {
    // 429 — err.retryAfter (ms)
  } else if (err instanceof Cesto.APIConnectionError) {
    // network failure or timeout
  } else {
    throw err;
  }
}
ClassWhen
BadRequestError400
AuthenticationError401 — invalid / missing / revoked key
PermissionDeniedError403
NotFoundError404
ConflictError409
UnprocessableEntityError422
RateLimitError429 — carries retryAfter (ms)
InternalServerError5xx
APIConnectionErrornetwork failure
APIConnectionTimeoutErrorrequest exceeded timeout
APIUserAbortErroryour AbortSignal fired
Every APIError carries status, code, requestId, and details from the API — useful when reporting an issue.

​
Automatic retries

Transient failures (408, 409, 429, 5xx, connection errors, and timeouts) are retried automatically with exponential backoff and jitter, honoring the Retry-After header. Tune with maxRetries (default 2), or disable per request with { maxRetries: 0 }.

​
Timeouts & cancellation

Each request times out after timeout ms (default 60s), throwing APIConnectionTimeoutError. Pass an AbortSignal to cancel a request yourself: 
const controller = new AbortController();
const promise = cesto.products.list({}, { signal: controller.signal });
controller.abort(); // → APIUserAbortError