Flag CDN

Flag files on disk use content hashes. Clients should call /get/ and follow the 301, or use the URLs already present on country records.

Path	Result
`GET /get/{code}`	301 to default PNG.
`GET /get/png/{code}`	301 to PNG.
`GET /get/svg/{code}`	301 to SVG.
`GET /flags/get/…`	Same handlers on the API host.

is a lowercase ISO alpha-2 (or similar key). Paths like /flags/nl.svg are not public; only opaque /flags/{24-hex}.svg|png files are served. Unknown codes return 404.

curl -L "https://cdn.reqi.dev/get/png/nl" -o nl.png
curl -I "https://cdn.reqi.dev/get/svg/nl"

CachingSuccessful flag responses send long-lived Cache-Control and CORS headers. Redirects land on hashed filenames so caches stay immutable when artwork changes.

Get started

Guides

Reference

Agents

Data