All Interzoid products and tools from a single launch point: Quickly solve data challenges - better ROI for everything your data flows into -> See it Now!

API Error Codes

HTTP status codes returned by Interzoid APIs, what they mean, and how to handle them

Overview

Every Interzoid API returns a standard HTTP status code with each response, so your application can tell at a glance whether a request succeeded and, if not, why.

The codes below apply across our API suite, including matching, standardization, enrichment, utility, and batch processing APIs. Checking the status code before reading the response body makes integrations more resilient, and helps you decide whether to retry a request, correct it, or contact support.

2xx
Success

The request was received and processed. The response body contains your results.

4xx
Client Errors

Something about the request needs attention, such as parameters, credentials, credits, or request volume.

5xx
Server Errors

A problem on our side prevented the request from completing. These are typically safe to retry.

Status Code Reference

Select the icon next to any code to copy a direct link to it.

HTTP Code Status Context Retry?
200 OK The request completed. Not needed
400 Bad Request Missing or invalid parameters, malformed JSON, invalid field mappings, or too many records. Fix first
401 Unauthorized Authentication failed or the supplied credentials do not authorize access to the requested service. Fix first
402 Payment Required Insufficient API credits. Fix first
405 Method Not Allowed Unsupported HTTP method. Use POST for JSON batch requests or GET for file-based enrichment. Fix first
408 Request Timeout The request timed out before completion. Consider a smaller batch before retrying. Yes
429 Too Many Requests Request volume or concurrent activity exceeded service limits. Reduce concurrency and allow time before retrying. Yes, after a pause
500 Internal Server Error A server-side error prevented completion, such as an input-file retrieval or internal processing failure. Yes

Handling Errors

Correct the Request First

Repeating these requests unchanged will return the same result. Resolve the cause, then send the request again.

  • 400 Check required parameters, JSON formatting, field mappings, and record counts.
  • 401 Confirm your API key is correct and authorized for the service you are calling.
  • 402 Add credits to your account before continuing.
  • 405 Switch to the HTTP method the endpoint expects.
Safe to Retry

These are usually temporary. Retry with an increasing wait between attempts (exponential backoff) rather than immediately.

  • 408 Retry, ideally with a smaller batch of records.
  • 429 Lower your request rate or number of concurrent calls, pause, then retry.
  • 500 Retry after a short wait. If the error persists, contact support.

Linking to a Specific Code

Direct Link Format

Each status code has its own anchor, so documentation, product pages, and support responses can point straight to it.

https://www.interzoid.com/apis/error-codes#http-429

Additional Resources

Try Our APIs Interactively

Our API interactive usage tool lets you call any of our APIs through a user interface without writing code, which is a quick way to see responses and status codes in action.

Try it Now
Code Examples, Database Queries, and Specifications

See quick and easy code examples in multiple programming languages, including Python, Node.js, Java, Typescript, and Go, along with database query examples and open specifications such as OpenAPI.

See All Examples
Still Seeing Errors?

If an error persists or the cause is not clear, reach out with the API you are calling, the status code returned, and the approximate time of the request, and we will help you track it down.

Contact Support