The Forward Geocoding API is a powerful tool that enables users to search for addresses and corresponding locations using a free-form address string. With this API, users can input a wide range of address formats, including partial or incomplete addresses, and receive standardized address and individual address components, as well as latitude and longitude coordinates and other useful information.
The API is designed to be easy to use, with a simple interface that makes it accessible to users of all skill levels. Simply input the address string you are interested in, and the API will return the corresponding location data, including latitude and longitude coordinates, as well as other useful information such as postal code, city, state, and country.
One of the key advantages of the Forward Geocoding API is its accuracy. The API draws on comprehensive and up-to-date databases of global address data, ensuring that users receive the most accurate information available. This can be particularly useful in situations where precise location information is critical, such as in logistics or transportation.
Another advantage of the API is its speed and efficiency. With a fast response time, users can quickly retrieve the information they need and integrate it into their workflows or applications. Additionally, the API is designed to handle large volumes of requests, making it a scalable solution for businesses and organizations with high-volume needs.
The Forward Geocoding API is also highly customizable, with a range of options and parameters that can be tailored to meet specific user needs. For example, users can choose to receive additional information such as street-level imagery or elevation data, or limit their queries to specific geographic regions.
Overall, the Forward Geocoding API is a valuable tool for anyone who needs to quickly and accurately determine the location associated with an address string. With its accuracy, speed, and customizability, the API is a versatile solution for businesses, individuals, and organizations across a range of industries and use cases, including logistics, transportation, real estate, and more.
Real Estate: Real estate agents and property managers can use the Forward Geocoding API to provide accurate location data for properties they are listing. This can help potential buyers or renters to better understand the location of a property and make informed decisions.
Logistics and Transportation: Companies in the logistics and transportation industry can use the Forward Geocoding API to accurately determine the locations of delivery addresses. This can help to streamline delivery routes, reduce delivery times, and optimize overall logistics operations.
Emergency Services: Emergency services such as police, fire, and ambulance services can use the Forward Geocoding API to quickly locate addresses in emergency situations. This can help first responders to arrive on the scene quickly and provide assistance as needed.
Travel and Tourism: Travel and tourism companies can use the Forward Geocoding API to provide location information for their customers. This can include identifying nearby attractions, providing directions, or helping customers to navigate unfamiliar cities or regions.
Marketing and Advertising: Companies conducting targeted marketing or advertising campaigns can use the Forward Geocoding API to identify potential customers in specific geographic regions. This can help to ensure that marketing materials are tailored to the needs and preferences of customers in different locations.
Besides the number of API calls, there is no other limitation
Geoapify provides Geocoding API that searches addresses worldwide. The API works via HTTP GET API. So it's cross-platform and can be used with most of the programming languages.
Geocode - Endpoint Features
Object | Description |
---|---|
text |
[Required] |
{"type":"FeatureCollection","features":[{"type":"Feature","properties":{"datasource":{"sourcename":"openstreetmap","attribution":"© OpenStreetMap contributors","license":"Open Database License","url":"https://www.openstreetmap.org/copyright"},"name":"Schwimmschulstraße","country":"Germany","country_code":"de","state":"Bavaria","city":"Augsburg","postcode":"86153","district":"Stadtjägerviertel","suburb":"Innenstadt","street":"Schwimmschulstraße","lon":10.880888,"lat":48.3736943,"formatted":"Schwimmschulstraße, 86153 Augsburg, Germany","address_line1":"Schwimmschulstraße","address_line2":"86153 Augsburg, Germany","timezone":{"name":"Europe/Berlin","offset_STD":"+01:00","offset_STD_seconds":3600,"offset_DST":"+02:00","offset_DST_seconds":7200,"abbreviation_STD":"CET","abbreviation_DST":"CEST"},"plus_code":"8FWG9VFJ+F9","plus_code_short":"9VFJ+F9 Augsburg, Bavaria, Germany","result_type":"street","rank":{"importance":0.20000999999999994,"popularity":7.539614846696554,"confidence":1,"confidence_city_level":1,"confidence_street_level":1,"match_type":"full_match"},"place_id":"51b1e07ec003c3254059ce99fe36d52f4840f00102f901c6bb400000000000c0020492031353636877696d6d736368756c73747261c39f65"},"geometry":{"type":"Point","coordinates":[10.880888,48.3736943]},"bbox":[10.8808677,48.3733624,10.8809263,48.3743088]},{"type":"Feature","properties":{"datasource":{"sourcename":"openstreetmap","attribution":"© OpenStreetMap contributors","license":"Open Database License","url":"https://www.openstreetmap.org/copyright"},"name":"Schwimmschulstraße","country":"Germany","country_code":"de","state":"Bavaria","city":"Augsburg","postcode":"86153","district":"Stadtjägerviertel","suburb":"Innenstadt","street":"Schwimmschulstraße","lon":10.8821152,"lat":48.3779289,"formatted":"Schwimmschulstraße, 86153 Augsburg, Germany","address_line1":"Schwimmschulstraße","address_line2":"86153 Augsburg, Germany","timezone":{"name":"Europe/Berlin","offset_STD":"+01:00","offset_STD_seconds":3600,"offset_DST":"+02:00","offset_DST_seconds":7200,"abbreviation_STD":"CET","abbreviation_DST":"CEST"},"plus_code":"8FWG9VHJ+5R","plus_code_short":"9VHJ+5R Augsburg, Bavaria, Germany","result_type":"street","rank":{"importance":0.17500999999999992,"popularity":7.545601521517001,"confidence":1,"confidence_city_level":1,"confidence_street_level":1,"match_type":"full_match"},"place_id":"51e79b7e9aa4c32540594cdb64f95f304840f00102f9019aa80a4200000000c0020492031353636877696d6d736368756c73747261c39f65"},"geometry":{"type":"Point","coordinates":[10.8821152,48.3779289]},"bbox":[10.8818623,48.3774636,10.8823827,48.3782923]}],"query":{"text":"Schwimmschulstraße, 86154 Augsburg","parsed":{"street":"schwimmschulstraße","postcode":"86154","city":"augsburg","expected_type":"street"}}}
curl --location --request GET 'https://zylalabs.com/api/1602/forward+geocoding+api/1285/geocode?text=Schwimmschulstraße, 86154 Augsburg' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, look at the ‘X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The ‘X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
760ms
Service Level:
100%
Response Time:
340ms
Service Level:
100%
Response Time:
2,088ms
Service Level:
50%
Response Time:
2,089ms
Service Level:
100%
Response Time:
1,770ms
Service Level:
100%
Response Time:
642ms
Service Level:
100%
Response Time:
1,191ms
Service Level:
100%
Response Time:
715ms
Service Level:
100%
Response Time:
127ms
Service Level:
100%
Response Time:
1,551ms
Service Level:
100%
Response Time:
1,436ms
Service Level:
100%
Response Time:
570ms
Service Level:
100%
Response Time:
1,399ms
Service Level:
100%
Response Time:
680ms
Service Level:
100%
Response Time:
628ms
Service Level:
100%
Response Time:
1,365ms
Service Level:
100%
Response Time:
1,163ms