Error Handling

Reliable error handling helps your Synoria integration remain stable when requests fail unexpectedly. Errors can occur because of invalid parameters, authentication problems, unavailable resources, network interruptions, or temporary service issues. Your app should identify these situations, respond appropriately, and provide users with helpful feedback without exposing sensitive technical details. For temporary failures, retrying with a controlled backoff strategy can improve reliability. For permanent errors, such as invalid credentials or malformed requests, the app should surface a clear message and avoid unnecessary retries. Consistent error handling also makes debugging easier and helps your team maintain dependable AI-powered experiences as your app grows.

Catch API Errors

Wrap Synoria requests in structured error handling so your application can respond gracefully when an operation fails or returns an unexpected result.

try {
  const response = await client.chat.create({
    model: "axiom-1",
    messages: [
      {
        role: "user",
        content: "Explain this error."
      }
    ]
  });

  console.log(response.output);
} catch (error) {
  console.error("Request failed:", error.message);
}

Handle Status Codes

HTTP status codes help determine whether an error comes from invalid input, authentication, usage limits, or a temporary service problem.

function getErrorMessage(status) {
  if (status === 400) {
    return "Check your request parameters.";
  }

  if (status === 401) {
    return "Check your API credentials.";
  }

  if (status === 404) {
    return "The requested resource was not found.";
  }

  if (status === 429) {
    return "Too many requests. Try again later.";
  }

  if (status >= 500) {
    return "Synoria is temporarily unavailable.";
  }

  return "An unexpected error occurred.";
}

Retry Temporary Failures

Temporary network or service errors may succeed when retried. Use a limited number of attempts with increasing delays instead of repeatedly sending requests without a pause.

async function retryRequest(request, attempts = 3) {
  for (let attempt = 0; attempt < attempts; attempt++) {
    try {
      return await request();
    } catch (error) {
      const temporary = error.status >= 500 ||
        error.status === 429;

      if (!temporary || attempt === attempts - 1) {
        throw error;
      }

      const delay = 1000 * 2 ** attempt;

      await new Promise(resolve =>
        setTimeout(resolve, delay)
      );
    }
  }
}

Best Practices

Keep error handling predictable by separating temporary failures from permanent ones, logging useful diagnostic information, and showing concise messages to users. Avoid exposing credentials or internal system details.