Retries and timeouts

Set a timeout and check the HTTP status before treating a response as data. For rate_limited or dns_resolution_failed, wait the number of seconds in Retry-After. Temporary connection failures and 500 or 503 responses can be retried with bounded backoff.

A timeout does not prove the original lookup was never processed. Repeating a metered check can consume another unit. Official SDKs default to no automatic retries for metered checks; choose an explicit retry policy if your application needs one.

Keep the error's request_id when debugging or contacting support. A 429 with quota_exceeded needs allowance or billing action; waiting a few seconds will not resolve it.

A server-side JavaScript example with a ten-second timeout and one attempt:

const response = await fetch('https://api.parseapi.com/ip/8.8.8.8', {
  headers: { 'X-API-Key': 'YOUR_API_KEY', 'Parse-Version': '2.0.0' },
  signal: AbortSignal.timeout(10_000),
});
const body = await response.json();

if (!response.ok) {
  throw new Error(body.code + ': ' + body.message + ' (' + body.request_id + ')');
}

console.log(body);