Errors

Every response tells you how it went in its status code. Codes in the 2xx range mean success. Codes in the 4xx range mean the request needs to change: a bad parameter, a missing scope, a resource that is not yours. Codes in the 5xx range mean something went wrong on our side, and the same request may succeed if you retry it.

Error format#

An error body has success: false and a human-readable message. Messages are written for the developer reading the log; do not parse them, branch on the status code instead.

{
  "success": false,
  "message": "This API key is missing the analytics:read scope"
}

Status codes#

A resource that belongs to another brand is always 404, never 403, so the API never confirms that someone else's campaign or survey exists.

Rate limit responses#

A 429 has its own body, along with Retry-After and the X-RateLimit-* headers described in Rate limits:

{
  "error": "Rate limit exceeded",
  "message": "Rate limit exceeded for this API key (60 requests/minute).",
  "retryAfter": 23
}

Handle errors#

• Retry 429, 500 and 503 with exponential backoff. For a 429, wait at least Retry-After seconds first.
• Do not retry any other 4xx. Fix the request, the key or its scopes.
• Treat 402 as a plan question for your Rendezvu admin, not a code problem.

async function rendezvu(path, attempt = 0) {
  const res = await fetch(`https://api.rendezvu.co/api/brand/v1${path}`, {
    headers: { Authorization: `Bearer ${process.env.RENDEZVU_BRAND_API_KEY}` },
  });
  const retryable = res.status === 429 || res.status >= 500;
  if (retryable && attempt < 5) {
    const wait = Number(res.headers.get('retry-after')) || 2 ** attempt;
    await new Promise((resolve) => setTimeout(resolve, wait * 1000));
    return rendezvu(path, attempt + 1);
  }
  const body = await res.json();
  if (!res.ok) throw new Error(`Rendezvu ${res.status}: ${body.message}`);
  return body;
}