canonical: https://jentic.com/apis/ote-godaddy.com/countries

# Ote Godaddy GoDaddy Countries API

Retrieve localized country information including ISO codes, calling codes, and state/province data. This test environment (OTE) provides summary and detailed country data filtered by market ID for building and testing international applications. No authentication required for public country metadata access.

## For AI agents

Look up country metadata, calling codes, and state lists filtered by market for localization and international form validation.

## Scope

Does not handle production GoDaddy domain services, DNS management, or hosting operations-use for country metadata lookup in test environments only.

## Capabilities

- Retrieve summary country lists filtered by market ID with ISO codes and calling codes
- Look up detailed country information including all states and provinces
- Access localized country names based on market language preferences
- Validate ISO country codes against supported country database
- Query calling code prefixes for phone number validation

## Use cases

### International Checkout Forms

Build localized checkout and registration forms with country and state dropdowns populated from GoDaddy's validated dataset. The API returns country names in the appropriate language based on market ID, ISO country codes for backend processing, and state/province lists for address validation. Supports BCP-47 market codes for 20+ languages.

Example prompt: Retrieve all countries for market 'en-US' and then fetch detailed state information for country code 'US' to populate a checkout address form

### Phone Number Validation

Validate and format international phone numbers by looking up calling code prefixes for each country. The API provides the dialing prefix for every supported country, enabling real-time phone validation in user input forms and normalizing phone numbers to E.164 format before storage.

Example prompt: Look up the calling code for country 'GB' to validate a UK phone number format

### Market-Specific Localization Testing

Test application behavior across different market locales by retrieving country data with localized labels. The OTE environment allows developers to verify that country names display correctly in each supported language before deploying to production. Essential for QA workflows on international SaaS platforms.

Example prompt: Compare country name localization by fetching the full country list for market 'fr-FR' and 'en-US' to verify French translations

### AI Agent Address Validation

AI agents use this API through Jentic to validate user-provided addresses during automated workflows like order processing or account setup. By searching for country validation operations in Jentic, agents can verify ISO codes, retrieve state lists for data normalization, and localize country names without manual API integration. The no-auth design makes it ideal for agent-driven validation tasks.

Example prompt: Search Jentic for 'validate country and state data' to retrieve the GoDaddy Countries API schema, then call GET `/v1/countries/{countryKey}` with marketId to validate an address

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/countries` | List all countries with summary information (ISO code, label, calling code) for a market |
| GET | `/v1/countries/{countryKey}` | Retrieve detailed country information including states and provinces for a specific country code |

## Key resources

- **Countries** — List all countries or retrieve detailed country information with states and provinces, filtered by market ID

## Why Jentic

- **Setup:** Wiring the GoDaddy Countries API by hand means targeting the developer.godaddy.com test host and handling retries yourself for simple metadata reads. Through Jentic you install once, import the GoDaddy Countries API from the API Directory, and your agent calls it.
- **Permission scoping:** The Countries API puts the country key in the URL path (`/v1/countries/{countryKey}`), so a rule can pin your agent to reading one country or the country list. You choose the operations it may call, and since the surface is read-only country metadata, nothing beyond those lookups is included.
- **Credential handling:** Any access value this test-environment metadata service requires is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'look up country metadata' or 'get details for one country', and Jentic returns the matching GoDaddy Countries operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Country Layer API** — Commercial country data API with richer metadata including currencies, languages, and regional information
- **Country State City API** — Extends country and state data with city-level information for three-tier address dropdowns
- **IP2Location API** — Determines user country and location from IP address for auto-populating country fields

## FAQ

### What authentication does the GoDaddy Countries API use?

None. The GoDaddy Countries API does not require authentication. It provides public access to country metadata, ISO codes, calling codes, and state lists. This is an OTE (test environment) endpoint designed for development and testing.

### Can I retrieve state lists for specific countries with the GoDaddy Countries API?

Yes. Use GET `/v1/countries/{countryKey}` with a valid ISO country code and marketId query parameter. The response includes an array of states with their state keys and localized labels. For example, calling `/v1/countries/US` returns all US states and territories.

### What are the rate limits for the GoDaddy Countries API?

Rate limit violations return HTTP 429 with a retryAfterSec field indicating the wait time before retrying. Specific rate limits are not documented in the OpenAPI spec. The OTE environment is designed for testing and may have different limits than production GoDaddy APIs.

### How do I get localized country names with the GoDaddy Countries API through Jentic?

Search Jentic for 'retrieve localized country data' to find the GoDaddy Countries API operations. Load the schema for GET `/v1/countries`, then execute with a BCP-47 marketId parameter like 'fr-FR' or 'es-ES'. The API returns country labels localized to that market's language. Install via pip install jentic and run it through Jentic One, the self-hosted execution layer.

### What is the difference between the summary and detailed country endpoints?

GET `/v1/countries` returns summary data for all countries (countryKey, label, callingCode only). GET `/v1/countries/{countryKey}` returns detailed information for one country including the full states array with stateKey and label fields. Use the summary endpoint for dropdowns, and the detailed endpoint when you need state/province lists.

### Is the GoDaddy OTE Countries API free?

Yes. This is a test environment endpoint (OTE = Operational Test Environment) provided by GoDaddy for developers building applications. It requires no authentication or payment. For production use, verify whether GoDaddy offers a production version of this API and check their pricing.

### Can AI agents use the GoDaddy Countries API for address validation?

Yes. AI agents discover this API through Jentic by searching for intents like 'validate country code' or 'get state list'. Jentic returns the operation schemas, and agents call the endpoints directly. The no-auth design makes it particularly simple for agent integration. Common agent tasks include validating ISO codes, populating country dropdowns, and normalizing address data.

### Can I limit what my agent is allowed to do with the GoDaddy Countries API?

Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, so you can allow just the country lookups it needs. Since this API puts the country key in the URL path (`/v1/countries/{countryKey}`), a rule can pin the agent to reading a single country or only the summary list from GET `/v1/countries.` The surface is read-only country metadata, so nothing beyond those lookups is ever exposed.