How to resolve HTTP 429 errors and migrate Oracle OTM HERE Maps integration to API key authentication (deprecated endpoints)
Symptoms / Triggers
-------------------
You may need this article if:
You are receiving HTTP 429 (Too Many Requests) errors from HERE APIs in your Oracle OTM integration
Your existing HERE credentials (app_id / app_code) have stopped working and you need to migrate to API key authentication
* You see errors when OTM calls HERE geocoding or routing endpoints and suspect the legacy endpoints have been deprecated
* You need to update HERE properties configuration in Oracle OTM to use the new HERE platform services
* You are setting up a new Oracle OTM instance with HERE Maps integration and need current endpoint URLs and authentication method
Quick Answer
------------
The HERE legacy endpoints (e.g., geocoder.ls.hereapi.com, route.ls.hereapi.com) and app_id/app_code authentication are deprecated. You must:
1. Register a new HERE platform account and generate an API key
2. Update the HERE properties in OTM with the new API key and new endpoint URLs
3. Consult Oracle OTM documentation for the specific property configuration steps
Important: The integration with HERE is a feature maintained by Oracle within OTM. HERE support can assist with API key generation and endpoint documentation, but OTM-side configuration must be handled through Oracle support.
Step 1: Obtain a New API Key from HERE
--------------------------------------
1. Register on the HERE Platform and create a project. This project will be provided with an App ID.
2. Generate an API key within this project. You can generate up to two API keys at any given time. Keys can be rotated by deleting one and generating a fresh one.
3. For detailed instructions, search "API key" on https://www.here.com/docs
Step 2: Update HERE Endpoint URLs
---------------------------------
The legacy HERE service host URLs are deprecated. Update your OTM HERE properties to the current endpoints:
| Service | Deprecated URL | Current URL |
| --- | --- | --- |
| Geocoding | https://geocoder.ls.hereapi.com/6.2/ | https://geocode.search.hereapi.com/v1/geocode |
| Routing | https://route.ls.hereapi.com/routing/7.2/ | https://router.hereapi.com/v8/routes |
For other services (e.g., reverse geocode, matrix routing), look up the latest host URLs at https://www.here.com/docs by searching "geocode" or "routing".
Step 3: Configure Oracle OTM Properties
---------------------------------------
In Oracle OTM, update the HERE properties settings:
1. Set the here.api_key property with the API key obtained from Step 1.
2. Set here.useLatestApiKey to true to use the latest API version.
3. Update the geocode and routing host URL properties to the values in Step 2.
4. Configure any additional properties as required — these are not set by the installer and must be configured manually. Refer to Oracle OTM documentation for the full list.
Step 4: Test and Validate
-------------------------
After configuring the properties, test the integration to confirm that Oracle OTM can communicate with HERE Maps and that geocoding and routing functionalities return expected results.
Oracle OTM Documentation References
-----------------------------------
* How to Set Up HERE in OTM
* HERE Engine Properties in OTM
Note: Some HERE service host URLs referenced in the above Oracle documentation may be deprecated. Oracle as a HERE partner may still have access to legacy endpoints. If you encounter issues following those guides, contact Oracle support.
Important Disclaimer
--------------------
The integration with HERE Maps is a feature on OTM maintained by Oracle. The steps above (particularly Steps 3 and 4) are provided as general guidance based on publicly available information and need to be tested and verified by you. For OTM-specific configuration support, please contact Oracle support.
Applies to: Oracle Transportation Management (OTM) with HERE Maps integration | HERE Geocoding & Search API v1 | HERE Routing API v8 | API Key authentication (replaces app_id/app_code)
Tags: Oracle OTM, Oracle Transportation Management, HERE Maps integration, 429 error, too many requests, API key migration, app_id app_code deprecated, geocoder.ls.hereapi.com deprecated, route.ls.hereapi.com deprecated, HERE platform registration, here.api_key property, here.useLatestApiKey, geocode endpoint update, routing endpoint update, OTM HERE properties, credential migration, legacy endpoint deprecated, Global Trade Management
Updated 3 days ago