---
title: "Get all countries"
method: POST
path: "/api/connector/v1/countries/getAll"
tags: ["Countries"]
---

# Get all countries

`POST /api/connector/v1/countries/getAll`

Returns all countries supported by the API.

## Request body

- Parameters
  - `ClientToken` string, required — Token identifying the client application.
  - `AccessToken` string, required — Access token of the client application.
  - `Client` string, required — Name and version of the client application.

## Response `200`

OK

- CountryResult
  - `Countries` Country[], required — The supported countries.
    - `Code` string, required — ISO 3166-1 alpha-2 code, e.g. `CZ` or `SK`.
    - `SovereignCountryCode` string, required — ISO 3166-1 alpha-2 code of the sovereign country. May differ from `Code` for dependent territories.
    - `EnglishName` string, required — English name of the country.
  - `CountrySubdivisions` CountrySubdivision[], required — The supported country subdivisions.
    - `Code` string, required — ISO 3166-2 code of the administrative division, e.g AU-QLD.
    - `CountryCode` string, required — ISO 3166-1 code of the [Country](https://mews-systems.gitbook.io/connector-api/operations/countries#country).
    - `EnglishName` string, required — English name of the country subdivision.
  - `CountryRules` CountryRule[], required — Country-specific rules
    - `CountryCode` string, required — ISO 3166-1 alpha-2 code, e.g. US or GB.
    - `IdentityCardExpirationDateNotRequired` boolean, required — Whether the country requires expiration date for identity card.
    - `DriverLicenceExpirationDateNotRequired` boolean, required — Whether the country requires expiration date for driver's license.
  - `CountryGroups` CountryGroup[], required — The supported country groups.
    - `Code` string, required — Group code, e.g. `EU`, `SCHENGEN`, `NORDIC`...
    - `EnglishName` string, required — English name of the country group.
    - `CountryCodes` string[], required — Codes of countries included in the group, in ISO 3166-1 alpha-2 format.

## Other responses

- `204` — Server has successfully fulfilled the request and there is no additional information to send back.
- `400` — Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
- `401` — Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
- `403` — Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
- `408` — Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see [Request timeouts](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts)
- `429` — Error caused by too many requests sent in a given amount of time. Response contains `Retry-After` header indicating how long the user agent should wait before making a follow-up request. For more information, see [Request limits](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-limits).
- `500` — Unexpected error on the Mews side. This may be due to a software fault. If such a situation occurs, the error will be logged and the development team notified, however you can raise an issue through GitHub on our [documentation repository](https://github.com/MewsSystems/gitbook-connector-api).

---

[API](https://skmtc.net/mews/apis/connector-api.md) · [All operations](https://skmtc.net/mews/apis/connector-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mews/connector-api/versions/81933a8ff730/schema)