Service proxies
Registered applications can create service proxies that act as copies of specific location services but whose authentication is handled by the application's client_id and client_secret.
Service proxies can manage your credentials and provide authentication in the following manner:
- The client app sends a security-sensitive request to the proxy service, but without sensitive credentials.
- The service proxy adds authentication to the request, such as API key or token, and then forwards it to the target service.
- The target service replies to the service proxy, which forwards the reply to your app.
To implement a service proxy
- Create a new application or use one of your existing applications.
- Register the application if it was not previously registered.
- Select the Services tab.
- Select which service to proxy and enter a rate limit for the number of requests you want to allow over a given period.
- You can also set a permissions list of allowed referrers that can access this proxy. We recommend creating a list of allowed referrers for your application domains in both development and production environments.
- A new proxy URL is returned. You can use this URL to access the requested premium service.
Available proxy services
The following services are available using service proxies:
| Service | Proxy Value |
|---|---|
| Geocoding (stored) | geocode |
| Geocoding (not stored) | geocode |
| Routing | route |
| Routing (asynchronous or optimized) | asyncRoute |
| Routing Utilities | routingUtilities |
| Closest Facility | closestFacility |
| Closest Facility (asynchronous) | asyncClosestFacility |
| Service Area | serviceArea |
| Service Area (asynchronous) | asyncserviceArea |
| Location Allocation | asyncLocationAllocation |
| Multi-vehicle routing | syncVRP |
| Origin Destination Cost Matrix Service | asyncODCostMatrix |
| Demographic data and GeoEnrichment | geoenrichment |