First Steps
On this page
Step 1: Get an API key
localhost and 127.0.0.1 without adding them to the key.RapidAPI (self-service)
Sign up at RapidAPI (Maptoolkit). Tiered plans with different request volumes are available. Once subscribed, your API key is available in the RapidAPI dashboard.
Enterprise
Includes access to all Maptoolkit APIs, dedicated infrastructure, custom SLAs, and direct account management. Contact us to get started.
Step 2: Add your API key to requests
Once you have an API key, add it to every request using one of the two methods below.
As a query parameter (simplest for testing):
https://staticmap.maptoolkit.net?center=48.2,16.4&zoom=12&size=750x400&api_key=YOUR_API_KEYAs an HTTP header (preferred for server-side requests):
MTK-ApiKey: YOUR_API_KEYProtect your key
Never commit your API key to source control or hard-code it in client-side code.
Store it in an environment variable (MAPTOOLKIT_API_KEY) and in browser apps, proxy tile and API requests through your backend so the key is never exposed to end users.
Restrict your key
In the Maptoolkit admin panel you can limit each key to specific origins:
Referers: only allow requests from your domain (for browser apps).
User-Agents: only allow requests from your app identifier (for mobile or server apps).
Step 3: Create your first map
To display interactive maps, we recommend MapLibre GL JS. It is open source, renders the Maptoolkit vector styles directly from a style URL, and supports 3D terrain and the globe view. Our MapLibre Plugins add a style switcher, an isochrone control and more.
Consider another library if you’re already using Mapbox GL JS in an existing codebase, or if you need Leaflet or OpenLayers for raster-tile use cases.
- MapLibre GL JS: recommended starting point
- Mapbox GL JS
- OpenLayers
- Leaflet
Step 4: Explore examples
Once your map is running, the MapLibre GL JS examples are the fastest way to add features. Each one is a working, copy-pasteable starting point.