POST
/
LocationServices
/
Mapping
/
GetUrl
/
v1.00
/
json6.ws
cURL
curl --request POST \
  --url https://api.addressy.com/LocationServices/Mapping/GetUrl/v1.00/json6.ws \
  --header 'Content-Type: application/json' \
  --data '{
  "Key": "<string>"
}'
{
  "VectorStyleUrl": "<string>",
  "RasterStyleUrl": "<string>",
  "GeneratedOnUtc": "2023-11-07T05:31:56Z"
}
Please note that we are unable to serve map data for China.
The Map Tile API takes an input of your Loqate key and returns a Signed URL, which is valid for one hour and can be used to provide secure access our tile server. Whilst the Signed URL is active you can make as many requests using that URL as needed. Our tile server provides access to basemap data, tiles and styling for a map. This can then be used with a map rendering library, such as MapLibre or Leaflet, to add an interactive map to your application. Other functionality required for your map, such as pins for locations, can then be added afterwards via the map renderer.

​
Mapping Concepts

There are several key concepts that are important to understand when implementing a map using this API:
  • Signed URL: a secure URL generated for a specific session within a limited time period, with limited permissions. This contains authentication information within the query, thus reducing the time required to authenticate and reducing overall response times. You will receive two signed URLs, one for vector based tiles and another for raster based tiles
  • Basemap data: basemaps form the foundation for your map, providing geographic context stored as tile layers. These layers include the context required to display useful information such as the names of streets, buildings and land categorisation
  • Vector tiles: a format of tile that stores map data using vector shapes. As these are composed dynamically, they can be easily styled and smoothly zoom in and out as a user is navigating. These are generally faster to load than Raster tiles, but can be more demanding on the end user’s hardware
  • Raster tiles: a format of tile that stores map data using grids of pixels, commonly as images. These tiles can be slower to load than vector tiles, but are generally less demanding on the end user’s hardware
  • Map Style: a Map style is a JSON document that defines how the map will appear when rendered
  • Map renderer: library required to render a map within an application. Once you have defined your data source as the signed URL you receive from this API, the map rendering library will pull data from Loqate at run time, rendering the map data for you. Commonly used open source libraries for this include MapLibre, Leaflet and Amplify

​
Application flow using a map renderer

Signed URLs can be used to request individual map tiles if required, however for more complex applications you’re likely to use a map renderer. The following diagram represents how an application could be designed to work with our API and a map renderer: Application Flow Here are the steps this flow takes:
  1. Make a request to https://api.addressy.com/LocationServices/Mapping/GetUrl/v1.00/json4.ws?key={{license_key}} (adding in your own API key)
  2. Receive multiple Signed URLs in the response (one for Raster tiles and one for Vector tiles)
  3. Choose whether you want to use Raster tiles or Vector tiles, and pass the appropriate Signed URL to the map renderer
  4. The map renderer will request basemap data from Loqate as needed (for instance this could be when a user scrolls on your map and the renderer interprets which tiles will be needed next)
  5. Loqate will return the appropriate map data
  6. The map renderer will then use this data to render the map on the screen of your browser
This method will consume credit each time a signed URL is generated.

Body

application/json

Response

200
application/json

Success

The response is of type object.