REST Countries compatibility - Countries API

Routes and response shapes follow REST Countries v3.1 conventions where possible, with deliberate limits and enrichments documented here.

Route mapping

REST Countries	Countries API
`GET /v3.1/all`	Not available — use GET /v1 with pagination
`GET /v3.1/alpha/{code}`	`GET /v1/alpha/{codes}`
`GET /v3.1/name/{name}`	`GET /v1/name/{name}` (+ fullText query)
`GET /v3.1/capital/{capital}`	`GET /v1/capital/{capital}`
`GET /v3.1/region/{region}`	`GET /v1/region/{region}`
`GET /v3.1/subregion/{subregion}`	`GET /v1/subregion/{subregion}`
`GET /v3.1/lang/{lang}`	`GET /v1/lang/{lang}`
`GET /v3.1/currency/{currency}`	`GET /v1/currency/{currency}`
`GET /v3.1/independent`	`GET /v1/independent?status=`
—	`GET /v1/current` (geo single object)
—	`GET /v1/random`
—	`GET /v1/notice`

Important differences

List and filter responses return at most 5 countries per request (limit 1–5).
No bulk /all endpoint — walk with offset or page on GET /v1.
Extra fields: wikidataId, unRegionalGroup, nested enrichment, and CDN flags URLs.
GET /v1/current returns one object, not an array.

See endpoints overview and country object for field-level detail.