Get your NIMBO API token

Create a NIMBO account, copy your API token, and use it to access NIMBO basemaps from a GIS, web application, or mapping service.

Open NIMBO Earth Online

Keep your token private

Your NIMBO API token is transmitted through the kermap_token parameter.

It identifies your account and attributes GeoCredit usage to it. Never publish it in a public repository, documentation, screenshot, or public client-side application.

Get your token in three steps

1. Open NIMBO Earth Online

   Select Connexion in the top-right corner.

   

2. Create an account or sign in

   Select Free sign up to create an account, or Sign in if you already have one.

   

3. Open your dashboard and copy the API token

   Once signed in, open your Dashboard.

   

   In the Web services section, copy the value displayed in the API field.

   

Authenticate your requests

Add the kermap_token query parameter to your NIMBO service URL:

?kermap_token=<YOUR_TOKEN>

Replace <YOUR_TOKEN> with the complete value copied from your dashboard, without the angle brackets.

When the URL already contains a ? query string, append the token with & instead:

&kermap_token=<YOUR_TOKEN>

Test your token

Before configuring a GIS or application, test your token with the WMTS GetCapabilities endpoint:

https://prod-data.nimbo.earth/mapcache/wmts/1.0.0/WMTSCapabilities.xml?kermap_token=<YOUR_TOKEN>

Open the completed URL in a browser. A successful request returns an XML document describing the available WMTS layers.

This is the simplest authentication test because it does not require selecting tile coordinates.

Service URL examples

TMS

https://prod-data.nimbo.earth/mapcache/tms/1.0.0/{LAYER}/{z}/{x}/{y}.png?kermap_token=<YOUR_TOKEN>

The layer name, available products, and tile-coordinate configuration depend on your integration.

View the TMS URL format and parameters

WMS

https://prod-data.nimbo.earth/mapcache/wms/1.0.0?kermap_token=<YOUR_TOKEN>

View the WMS URL format and parameters

WMTS

https://prod-data.nimbo.earth/mapcache/wmts/1.0.0/WMTSCapabilities.xml?kermap_token=<YOUR_TOKEN>

View the WMTS URL format and parameters

Protect your token

• Keep the token in server-side configuration or a secrets manager.
• Never commit it to Git or include it in public documentation.
• Regenerate it if it has been exposed or shared with someone who should no longer have access.
• Treat exported QGIS projects and configuration files containing the token as sensitive files.

Public web applications

A token sent directly from browser-side JavaScript can be retrieved from the application code or network requests.

For a public application, use a backend proxy or contact NIMBO to define an appropriate production access model. Client-side obfuscation does not protect the token.

Troubleshooting

Problem	What to check
401 Unauthorized or 403 Forbidden	Check that the complete token is present and that the account can access the requested service or product.
WMTS capabilities work, but tiles do not load	Check the layer name, date, tile coordinates, and TMS or XYZ configuration used by your client.
Requests worked and then stopped	Check the remaining GeoCredits and subscription status in your dashboard.
A token was exposed publicly	Regenerate the token in your dashboard and update every application that uses it.
A public web application reveals the token	This is expected with direct browser requests. Use a backend proxy or discuss a production integration with NIMBO.

Continue your integration

Add NIMBO to QGIS

Use NIMBO with MapLibre

Discuss a production integration