Postal Data API
Postal Data API validates and looks up postal codes, locations, coordinates, and regional metadata across more than 240 countries and territories.
Integration
- Vendor
- Postal Data API
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 6
- Composio slug
postal_data_api
Tools
- Get API Information
Return Postal Data API version, coverage, usage guidance, current balance, and configured rate-limit status when returned, for connectivity or service discovery. The provider does not document this endpoint as unbilled, so assume it may con
- Get Postal Code Metadata
Return all available country-specific metadata for a postal code, such as coordinates, timezone, county, elevation, and administrative levels. The metadata fields vary by country and availability. Each successful call consumes one Postal Da
- Look Up Postal Code
Look up the city, region, and coordinates for a postal code. Use this for a concise location result; use Get Postal Code Metadata for country-specific administrative details. Each successful call consumes one query.
- Search Postal Codes by City
Return all postal codes matching a city and optional region, including fuzzy-match details. For US searches, provide a state name or state code. Each successful call consumes one Postal Data API query.
- Validate Postal Code
Check whether one postal code exists without treating a nonexistent code as an execution error. Inspect valid in the response. Each successful call consumes one Postal Data API query.
- Validate Postal Codes in Bulk
Validate 1 to 1,000 postal codes synchronously, including mixed-country batches. Results preserve input order and report per-record failures. A batch of N records consumes N queries and is rejected atomically if balance or rate-limit budget
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Postal Data API.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Postal Data API tools in chat.
What teammates see: by default, memories from Postal Data API are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.