API Keys

Access to the Mapfluence service is granted using API keys. To obtain one, contact info@urbanmapping.com. An API key must be included in every request to the Mapfluence web services, as either a get parameter or in cookies.

Using HTTP GET Parameters

This is recommended. Every request issued by your application to Mapfluence must include an API key in the GET portion of the request:

http://visual.mapfluence.com/.../5.png?apikey=YOUR_API_KEY

If you develop using Mapfluence Javascript API, include the following in your header:

<script src="http://spatial.mapfluence.com/js/api.js?apikey=YOUR_API_KEY" type="text/javascript"></script>

Then every URL constructed using the Mapfluence Javascript API will include the API key in the request. If you construct URLs manually, you need to manually include the key.

Alternatives

You may have noticed the documentation and API Lab don't explicitly declare an API key. That is because your browser was issued cookies which are passed by your browser with every request to the Mapfluence services. This is not recommended in practice because of browser specific constraints on cookies.

If you are concerned about including your API key in the source of your pages, there is a process for signing requests to restrict key poaching. Please contact UMI support <mailto:support@urbanmapping.com> for more details.