Geocoding API
Accurate geocoding results are an essential part of many geospatial processes. Whether you want to show your retail locations on a map, calculate an optimized route for a delivery, or search within the radius of an origin point, the geocoding API enables you to associate latitude and longitude with an associated address. Below you will find all of our documentation for our geocoding API.
Forward Geocode
Forward geocoding (also called address geocoding) is the process of finding an associated latitude and longitude for a given address.
Example: 1060 W. Addison St., Chicago IL, 60613 returns 41.947239,-87.655636.
| Method | Docs Link |
|---|---|
| GET | /geocoding/v1/address |
| POST | /geocoding/v1/address |
Reverse Geocode
Reverse geocoding is the process of taking a latitude and longitude pair and providing the associated address, or nearest address point.
Example: 41.947239,-87.655636 returns 1060 W. Addison St., Chicago, IL 60613
| Method | Docs Link |
|---|---|
| GET | /geocoding/v1/reverse |
| POST | /geocoding/v1/reverse |
Batch Geocode
Batch Geocoding allows you to submit multiple forward or reverse geocode requests at a time. You may submit up to 100 addresses or lat/lng pairs in a single batch request.
| Method | Docs Link |
|---|---|
| GET | /geocoding/v1/batch |
| POST | /geocoding/v1/batch |
Async Batch Geocode
Asynchronous Batch Geocoding is designed for large datasets where you need to process more than 100 addresses or want to avoid timeout issues. This approach allows you to submit up to 1 million rows and retrieve results when processing is complete.
Single-line vs. 5-box Input
The 5-box input format allows for a higher degree of address specification by entering an address, broken down into individual components; it bypasses the parsing functionality of the single-line request.
The following are sample requests for 1600 Pennsylvania Ave NW, Washington, DC, 20500 shown in single-line and 5-box request formats:
Single-line address request
5-box address request