Skip to content

Endpoints

Endpoints

Name

List countries

Full country catalog with ISO code, calling code and MCC.

HTTP method and path

GET/api/v6/tools/countries

https://developers.hablame.co/api/v6/tools/countries

What happens when you run it

  • Read only: it does not change your organization’s data.
  • The call is not charged.

What it does

Returns the full country catalog the API knows about, with ISO code, calling code, mobile country code (MCC) and names in English and Spanish. Use it to render country pickers, autodetect a country from a phone prefix, or resolve MCCs.

The catalog rarely changes. The response includes Cache-Control: public, max-age=3600 so your client and any intermediate CDN can amortize the traffic.

Languages

Names are provided only in English (en) and Spanish (es). Any other lang value falls back to English.

Availability and prerequisites

  • Published and available in the production API v6.
  • Every path starts at https://developers.hablame.co.
  • You need a Hablame API key to call it.

Create your API key

Authentication and permissions

  • Send your API key in the Authorization header with the Bearer scheme.

Who can call it: Any valid API key.

Limits and operational notes

Usage limit: 60 requests per minute.

Path parameters

This endpoint has no path parameters.

Query parameters

NameTypeDescription and rules
langOptionalstring

ISO-639-1 code. When specified, each country returns a flat name in that locale instead of the full names map.

Allowed values:en esExample:es

callingCodeOptionalstring

Filters countries by E.164 calling code (for example 57 for Colombia). An optional leading + is accepted.

Example:57

searchOptionalstring

Case-insensitive substring match on the country name in the requested locale. Minimum 2 characters.

Minimum length:2Example:col

HTTP headers

NameTypeDescription and rules
AuthorizationRequiredstring

Your API key with the Bearer scheme.

Example:Bearer hk_TU_API_KEY

Request body

This endpoint takes no request body.

Successful responses

200

Country catalog.

Response example
{
  "success": true,
  "data": [
    {
      "code": "CO",
      "code3": "COL",
      "callingCode": "57",
      "mcc": "732",
      "flag": "https://flagcdn.com/co.svg",
      "names": { "en": "Colombia", "es": "Colombia" }
    },
    {
      "code": "MX",
      "code3": "MEX",
      "callingCode": "52",
      "mcc": "334",
      "flag": "https://flagcdn.com/mx.svg",
      "names": { "en": "Mexico", "es": "México" }
    }
  ],
  "meta": {
    "requestId": "b9b1704baffab211",
    "clientIp": "203.0.113.45",
    "timestamp": "2026-05-23T02:00:00+00:00",
    "responseTimeMs": 4.12
  }
}

The example values are illustrative.

Response fields

NameTypeDescription and rules
successAlways presentboolean

dataAlways presentarray<object>

data[].codeAlways presentstring

ISO 3166-1 alpha-2 (2 uppercase letters).

Example:CO

data[].code3Always presentstring

ISO 3166-1 alpha-3.

Example:COL

data[].callingCodeAlways presentstring

E.164 calling code, without +. A string so leading zeros survive.

Example:57

data[].mccAlways presentstring

Mobile Country Code (E.212).

Example:732

data[].flagAlways presentstring

Flag URL (SVG).

Format:uri

data[].namesobject

Country name per language (en, es). Present only when ?lang is NOT sent; a language with no name loaded is absent.

data[].names.{any key}string

data[].namestring

Country name in the requested lang. Present only when ?lang is sent.

metaAlways presentobject

Response metadata.

meta.requestIdAlways presentstring

Unique request identifier (16 hexadecimal characters). It matches the X-Request-Id header. Quote it when contacting support.

Example:b9b1704baffab211

meta.clientIpAlways presentstring

IP the API saw your request come from. Useful if your API key only accepts certain networks.

Example:203.0.113.45

meta.timestampAlways presentstring

Date and time the response was built (ISO 8601 with offset).

Format:date-timeExample:2026-06-04T19:43:59+00:00

meta.responseTimeMsAlways presentnumber

Time (ms) the server took to process the request.

Example:4.24

Error codes

Every error response has the same shape: success set to false and an error object whose code says what happened. They are grouped here by kind, with the codes this endpoint can return.

Shape of an error response
NameTypeDescription and rules
successAlways presentboolean

Fixed value:false

metaAlways presentobject

Response metadata.

meta.requestIdAlways presentstring

Unique request identifier (16 hexadecimal characters). It matches the X-Request-Id header. Quote it when contacting support.

Example:b9b1704baffab211

meta.clientIpAlways presentstring

IP the API saw your request come from. Useful if your API key only accepts certain networks.

Example:203.0.113.45

meta.timestampAlways presentstring

Date and time the response was built (ISO 8601 with offset).

Format:date-timeExample:2026-06-04T19:43:59+00:00

meta.responseTimeMsAlways presentnumber

Time (ms) the server took to process the request.

Example:4.24

errorAlways presentobject

error.codeAlways presentstring

Stable UPPER_SNAKE_CASE identifier. Clients branch on this value.

Example:AUTH_REQUIRED

error.legacyCodeinteger

Legacy v5 numeric code, only when a bridge exists. Omitted for codes born in v6.

Example:40002

error.typeAlways presentstring

URL to the error documentation.

Format:uriExample:https://developers.hablame.co/docs/v6/errors/auth-required

error.messageAlways presentstring

Human readable text, in English. It is for the developer log, not the end user: do not parse it.

error.detailsAlways presentarray<object>

Structured context (validation issues, affected resource). Empty array when there is no extra context.

Validation

This endpoint does not declare responses of this kind.

Authentication

  • 401Invalid or missing credentials.
  • 401AUTH_REQUIRED

    No Bearer token was sent, and every call requires one.

    Message the API returns: Authentication is required. Send your API key as `Authorization: Bearer <token>`.

  • 401AUTH_INVALID_KEY

    The API key is not recognized: wrong format, revoked or expired.

    Message the API returns: The provided API key is invalid or has expired. Please verify the value sent in the `Authorization: Bearer` header.

Permissions

  • 403AUTH_IP_NOT_ALLOWED

    The key only works from certain networks and your IP is not one of them.

    Message the API returns: This API key cannot be used from this IP address. The address we saw is in `meta.clientIp`: call from one of the networks allowed for the key, or use a key that allows this one.

  • 403ACCOUNT_NOT_ACTIVE

    Your organization is suspended or closed.

    Message the API returns: The organization associated with this API key is not active. Please contact support.

Usage limits

  • 429Request limit exceeded.
  • 429RATE_TPS_EXCEEDED

    You exceeded your organization quota for this endpoint.

    Message the API returns: You have exceeded the allowed request rate for this endpoint. Please wait before retrying.

  • 429RATE_DDOS_EXCEEDED

    Unusually high volume from your source IP.

    Message the API returns: Too many requests from this IP within a short window. Please wait before retrying.

Resource not found

This endpoint does not declare responses of this kind.

Internal errors and availability

  • 503Service temporarily unavailable.

Other responses

This endpoint does not declare responses of this kind.

See it in the error catalog

Special considerations

This endpoint has no special considerations.

Related documentation

Need help?

Was this page helpful?

See all support channels

Ask for help about this: this endpoint

We build a message with the details that help us look into your case. Read it, complete it and send it yourself: nothing is sent on its own.

The message never carries your API key or passwords.