Skip to main content

Geocoding API

Convert Addresses to Coordinates & Vice Versa

Transform addresses into precise coordinates and coordinates into human-readable addresses. Essential for any application that needs to work with location data.

Key Features

Accurate geocoding for every use case

Forward Geocoding

Convert addresses and place names into precise geographic coordinates (latitude/longitude)

Reverse Geocoding

Transform coordinates into human-readable addresses with detailed location information

Autocomplete

Provide real-time place and address suggestions as users type with smart location filtering and boundary controls

Global Coverage

Geocode addresses worldwide with support for international address formats

High Accuracy

Rooftop-level precision for addresses with building-specific coordinates

Consistent Results

Reliable, reproducible geocoding with high success rates and quality scoring

Reverse Geocoding: Convert Coordinates to Address

Reverse geocoding takes a latitude and longitude pair and returns the closest human-readable address. It is the inverse of forward geocoding, where you start with an address and get coordinates. Reverse geocoding powers any application where the user starts from a point on a map: store locators, delivery drop-off confirmations, GPS check-ins, geotagged photos, and AI agents that need a verifiable street address for a coordinate the user supplied.

The MapAtlas Geocoding API returns the full address breakdown for any coordinate: street, house number, neighborhood, city, region, postal code, and country, in any of the world's address formats. The response is consistent across countries and stable enough to compare against your existing records.

Example request

curl -X GET "https://api.mapatlas.xyz/v1/geocode/reverse?lat=52.3676&lon=4.9041" \
  -H "Authorization: Bearer YOUR_API_KEY"

Global Coverage with Pinpoint Accuracy

Our geocoding engine delivers industry-leading accuracy across 190+ countries and territories. Powered by OpenStreetMap data and advanced address parsing, we provide confidence scoring and detailed metadata for every result.

190+
Countries Covered
High
Accuracy Rate
<100ms
Avg Response Time
  • Confidence scoring for every geocoding result
  • Detailed address components (street, city, postal code)
  • Support for structured and free-form address input

Advanced Features for Every Use Case

Go beyond basic geocoding with powerful features designed for production applications. From structured address parsing to multilingual support, we provide the tools you need to build sophisticated location-based services.

Address Normalization

Standardize and clean inconsistent address formats into structured, validated components

Multilingual Support

Return results in multiple languages with Unicode support for global applications

Autocomplete & Suggestions

Real-time address suggestions as users type for better UX and accuracy

GDPR Compliant

Privacy-first architecture with no data retention and EU-hosted infrastructure

Normalized
"123 main st"
↓
123 Main Street
City, State ZIP
Multilingual
?text=Tokyo Tower
&lang=ja

// 東京タワー
// 日本
Autocomplete
/autocomplete
?text=Eiffe

// Eiffel Tower
// Eiffel 65
GDPR Compliant
No data logsNo retentionEU servers

Technical Specifications

Core Capabilities

Geocoding Types
Forward & Reverse
Accuracy
Rooftop-level precision

Coverage & Scale

Coverage
Global, all countries
Autocomplete
Real-time suggestions

Data Format

Response Format
JSON with full details
Encoding
UTF-8, all languages

Pricing

Free Tier
10,000 geocodes/month
Rate Limits
Unlimited

Ready to Get Started?

Start building with MapAtlas today. Sign up for free and get instant access to all our mapping APIs with generous free tier limits.

Common questions about Geocoding API

Everything you need to know before integrating MapAtlas Geocoding API.

Building with AI? Call this API directly from your agent.

Cursor, Copilot, Cline, and autonomous agents can use this endpoint via the public OpenAPI 3.1 spec or the MapAtlas MCP server. Auto-discovery, no glue code.

See AI integration guide

Common questions about Geocoding API

Everything you need to know before integrating MapAtlas Geocoding API.

What is the difference between forward and reverse geocoding?
Forward geocoding converts a text address into coordinates (latitude and longitude). Reverse geocoding does the opposite: it takes coordinates and returns the nearest address. MapAtlas Geocoding API supports both in a single integration.
How accurate is MapAtlas geocoding?
MapAtlas geocoding uses a combination of official address databases, OpenStreetMap data, and proprietary data enrichment to deliver street-level accuracy across Europe and worldwide. Confidence scores are returned with each result so your application can handle uncertain matches gracefully.
Can I geocode in bulk?
Yes. MapAtlas supports batch geocoding via our API with up to 1,000 addresses per request. This is ideal for migrating address databases, enriching CRM data, or processing delivery addresses.
Is the Geocoding API GDPR compliant?
All geocoding requests are processed on EU-based servers and no addresses or coordinates are stored beyond the request lifecycle. MapAtlas runs in ISO 27001 certified EU data centres and is GDPR compliant.
What formats does the Geocoding API return?
Results are returned as JSON with structured address components (street, city, postal code, country), coordinates, and a confidence score. GeoJSON output is also supported.
How do I convert latitude and longitude to an address?
Use the reverse-geocode endpoint. Send the lat and lng as query parameters and the API returns the closest postal address with structured fields for street, city, postcode, and country. The endpoint is rate-limited generously on the free tier and supports batch lookups on paid plans.
How do I convert an address to coordinates?
Call the forward-geocode endpoint with the address as a single text string. The API returns one or more candidate locations, each with a precise latitude and longitude, a confidence score, and the matched components. You decide whether to take the top result or present a picker.
Is this an address checker?
Yes. Forward geocoding doubles as address validation: if the API returns a high-confidence match with a rooftop or street-level result, the address is valid and resolvable. If the best match falls back to a city or postcode centroid, that is the signal to flag the address as suspect in your checkout or onboarding flow.