Use this when you are deciding which scopes your app should request at install time, or when you need to render a permission picker showing the developer what each scope covers. The same catalog drives the merchant-facing install screen, so what you see here is exactly what the merchant will see when approving your app.

This endpoint is public — no token required.

Each row carries the ISO 3166-1 alpha-2 code (US), alpha-3 code (USA), name, capital, primary currency, recommended default locale, calling codes, and postal-code metadata. Use this to render country pickers in checkout, address forms, store onboarding, and the storefront builder.

Returns the ISO 3166-2 subdivisions for a given country — typically states (US), provinces (CA, IN), regions, etc. Used to populate state pickers in storefront checkout, address forms, and shipping-zone configuration.

countryCode is a 2-letter ISO 3166-1 alpha-2 code (US, IN, GB, ...). Case-insensitive on the wire; canonicalized to uppercase server-side.

No scope required.

Each row carries the BCP-47 code (en, pt-BR, zh-TW), the English name, the native name as the language writes it, and a rtl flag so right-to-left scripts (Arabic, Hebrew, Persian, Urdu) render correctly. Use this to populate locale pickers in storefront builders, translation tooling, and the admin's language settings.

Use this to populate timezone pickers in store onboarding, shipping schedules, scheduled posts — anywhere the merchant or end user picks a timezone. Strings are the canonical IANA identifiers (America/Los_Angeles, Asia/Kolkata, Europe/London) — the same ones every standard timezone library understands.

Returns ISO 4217 currency definitions used across the platform — code, symbol, name, decimal places, and sample formatting. Identical for every store; safe to cache aggressively client-side.

No scope required — every authenticated token can call this.

Each row carries the ISO country code, country name, dial code as a string (+1), the same code as an integer for sorting (1), an example local number in the country's typical format, and the flag emoji derived from the country code. Use this to build phone inputs where the merchant picks a country and the dial code auto-fills.

Pass any ISO 3166-1 alpha-2 country code and get back the decimal separator, thousands separator, digit grouping pattern, and where the currency symbol belongs relative to the amount. Use this to mirror the admin's price formatting on the storefront so a customer in Germany sees 1.234,56 € and a customer in the US sees $1,234.56 — same product, same data, different presentation.

Values come from CLDR (Unicode's locale database), so they match every other major platform's defaults for the same country.

Use this when you want to bake every country's address format into your client at build time, instead of fetching per-country at runtime. The same data is available per-country at /reference/address-format/:countryCode if you only need one.

Each country carries a format string (the order and arrangement of address lines), which fields are required, regional label conventions (state vs province vs prefecture; zip vs postal vs pin; city vs district), the postal-code validation regex, and the list of valid subdivisions.

Data sourced from Google's i18n address library; updates ride platform releases.

Same shape as a single row in /reference/address-format. Use this when you already know the country (the merchant just picked it, the shopper is checking out from a known billing country) and you want to render an address form with the right field order, labels, validation regex, and subdivision list.

The response carries everything you need to build a country-correct form without baking per-country logic into your client.