Documentation

API Documentation

40 REST APIs behind one key and one monthly credit balance. JSON over HTTPS, no SDK required.

Quick start

  1. 1 Get an API key. Sign up free and create a key on the API Keys page — 1,000 credits a month, no card.
  2. 2 Make your first call. Any HTTP client works — pass the key in the X-Api-Key header.
  3. 3 Track your usage. Credits, latency and errors per key on the Usage page.
bash
curl https://api.apicodex.io/countries/v1/all \
  -H "X-Api-Key: $APICODEX_KEY"

Authentication

Every request carries your key in the X-Api-Key header. Keys start with acx_live_ and belong to your team — every key shares the team's plan and credit balance.

Keep keys server-side. A compromised key can be revoked instantly; revocation takes effect within minutes.

Credits & rate limits

Each call spends credits from one monthly balance: cheap lookups cost 1, heavyweight scrapes cost more. The exact cost of every endpoint is on the pricing page and in each API's reference below.

Requests per second is capped per plan. Over quota or over the rate limit, the gateway answers 429 until the billing period rolls over or you back off.

Errors

Failures are JSON with an error message and a conventional status code:

400Bad request — a required parameter is missing or malformed.
401Missing, invalid or revoked API key.
403Key suspended — contact support.
404Unknown endpoint — check the path against the reference below.
429Over the plan's credit quota for this period, or over the per-second rate limit.
5xxUpstream failure — safe to retry with backoff; failed calls still show on your Usage page.

Reference

Every API, straight from the spec

Each reference is rendered live from its OpenAPI spec (/openapi/{api}.yaml) — parameters, responses and examples, always in sync with what the gateway serves.

Email

Document Parsers

Text Intelligence

Web Intelligence

Infrastructure

Data & Reference

Developer Tools

Vehicle Data

Web Scraping

Social Media