FAQ & Troubleshooting

Q: I keep getting a 401 API_KEY_REQUIRED response. What am I doing wrong?

A: This means the API did not receive your API key, or the key is invalid. Make sure you included the x-api-key header in every request and that its value is correct. If you have a key but still get this error, double-check for typos and ensure your key hasn’t expired or been revoked. (If you don't have a key yet, you need to obtain one from Ambalay Maps first.)

Q: I provided coordinates to /reverse or /route but got a 500 REVERSE_GEO_CODING_ERROR or similar error message. Why?

A: A 500 error in this context usually indicates a bad request or an inability of the server to handle the input. Common causes are missing or malformed parameters. For reverse geocoding, ensure you include both lat and lon and they are valid numbers. For routing, ensure origin, destination, and mode are all provided. Also check that latitude values are between -90 and 90, and longitude between -180 and 180. If the coordinates are extremely out of bounds or the route is impossible to calculate (e.g., over the ocean or outside the service area), the API might respond with an error. Adjust the input and try again.

Q: The /search endpoint returned an empty list but I expected results. What should I do?

A: An empty data array means the API could find no location matching your query. This is not an error (the request succeeded, but found nothing). Here are some steps to troubleshoot:

  • ● Check for typos or spelling errors in your query.
  • ● Try making the query more general or different. If it’s too specific or uncommon, the database might not have it.
  • ● Include additional context in the query if possible (e.g., add a city or country name).
  • ● If you continue getting no results for queries you believe should exist, contact support – it could be that the place is not yet in the database.

Q: How accurate are the routes and geocoding results?

A: Ambalay Maps aims to provide accurate routing and location data, especially within its supported regions. Routes take into account known roads and can calculate travel time based on distance and possibly road speeds. Geocoding results (both forward and reverse) use the latest available map data. However, accuracy can vary if the location is in a newly developed area or a remote region. Always verify critical information, and if something seems off, you can report it via the support channels.

Q: Does Ambalay Maps support other features like distance matrix or map tiles?

A: The current documentation covers routing and geocoding. Ambalay may offer additional APIs such as distance matrix (calculating travel times between many points) or map tile services, but those would be accessed via different endpoints or require enabling in your account. Check Ambalay’s official documentation or announcements for any new features. If you need a feature not documented here, reach out to the Ambalay support team for the latest info.