Most “how to get a geocoding API key” tutorials cover sign-up screenshots and stop there, leaving out the parts that actually determine whether your integration works smoothly: which fields to request, how to structure requests for ambiguous addresses, and what to do once your free tier stops covering real traffic. This guide walks through the entire process to get geocoding api key access through Distancematrix.ai, from account creation to a working production request, with the practical details most guides skip.
Step 1: Create an Account
Go to distancematrix.ai and sign up using either an email address and password or the Google OAuth option for a single-click setup. There’s no business verification, no use-case justification form, and no approval queue; the account activates as soon as you confirm your email, and the free tier is available immediately.
This matters more than it sounds. Several competing geocoding providers require a credit card upfront or a manual review before issuing credentials, which adds friction to even the smallest proof-of-concept project. Here, you can be testing real requests within minutes of landing on the homepage.
Step 2: Generate Your API Key
From your dashboard, navigate to the API keys section and click to create a new key. Name it something that identifies its purpose, “dev-testing” or “production-app”, since most projects eventually need separate keys for different environments, and retrofitting that separation later means going back through every place the original key was hardcoded.
The key appears instantly and is active immediately. Copy it somewhere secure right away, treat it the same way you’d treat a database password, since anyone with the key can make billable requests against your account. Store it in an environment variable or Secrets Manager, never directly in source code that might end up in a public repository.
Step 3: Make Your First Real Request
With a key in hand, a basic forward geocoding request looks like this:
https://api.distancematrix.ai/maps/api/geocode/json?address=221B+Baker+Street+London&key=YOUR_API_KEY
The response returns a status field you should always check first; “OK” means at least one match was found, “ZERO_RESULTS” means the address couldn’t be matched, and anything else generally points to a malformed request. Successful responses include a results array ordered by confidence, with geometry. location giving you the lat/lng pair, formatted_address giving a cleaned-up address string, and address_components breaking the address down into individually labeled parts like street, city, and postal code.
Reverse geocoding, going from coordinates back to an address, uses the same endpoint with a latlng parameter instead:
https://api.distancematrix.ai/maps/api/geocode/json?latlng=51.5237,-0.1585&key=YOUR_API_KEY
Handling the Responses You’ll Actually Get
| Status | Meaning | What To Do |
| OK | At least one match found | Use results[0] for highest confidence |
| ZERO_RESULTS | No matching location | Prompt user to refine input |
| INVALID_REQUEST | Missing or malformed parameter | Check request format, not the address |
A surprising number of integration bugs come from skipping the status check entirely and assuming the results array is always populated. Real address input from real users is messier than test data; building in explicit handling for ZERO_RESULTS and multiple ambiguous matches from day one saves a debugging session later.
Security Habits Worth Building In Early
- Keep keys in environment variables, never hardcoded in committed source files
- Use separate keys for development and production so you can rotate one without breaking the other
- Proxy requests through your own backend if calling from client-side code, so the key never appears in browser network traffic
- Rotate immediately if you suspect a key has leaked; don’t wait to confirm it
Ready to Start
Getting a working geocoding key through Distancematrix.ai takes minutes, not days, and the free tier provides enough room to fully validate your integration before any billing starts. Usage-based pricing afterward means you’re never stuck paying for capacity you didn’t use. Get started at get geocoding api key and have a working request running before your coffee gets cold.
