• Optimization
  • Navigation
  • Tracking
  • Maps
  • Places

  • Integrations

Raster Tiles API

Introduction

The Raster Tiles API serves raster tiles from NextBillion.ai raster tilesets. Raster data refers to pixel-based data format in which data is stored in a grid structure. Each pixel, or unit of information, has the same size and shape, but varies in value. Raster Tiles are images created in raster data format. These tiles can be used to display maps as a grid of images which can be loaded on map-based tools or platforms.

GET

https://api.nextbillion.io/maps/{mapId}/{tileSize}/{z}/{x}/{y}{scale}.{format}?key={your_api_key}

Request Parameter

Loading..

Sample Request

curl --location 'https://api.nextbillion.io/maps/dark/256/7/29/51.jpg?key=<your_api_key>'

Sample Response

API Query Limits

NextBillion.ai allows a maximum rate limit of 6000 queries per minute or 100 queries/second for continuous requests. Note: We can increase the quota if needed, on request. Contact support@nextbillion.ai for more details.

API Error Codes

Response codeDescriptionAdditional notes
200Normal success case.Normal success case.
400Input validation failed.There is a missing or an invalid parameter or a parameter with an invalid value type is added to the request.
401APIKEY not supplied or invalidThis error occurs when the wrong API key is passed in the request or the key is missing altogether
403APIKEY is valid but does not have access to requested resourcesYou might be querying for a geographical region which is not valid for your account, or requesting a service which is not enabled for you.
404Requested host/path not foundThis error occurs when a malformed hostname is used.
414Request is too longThis error occurs when the URI is too long. Maximum allowed length is 8192 bytes.
422Could not process the requestThe requested tiles were not found. Please check the input request. Reach out to support@nextbillion.ai if the issue persists.
429Too many requestsQPM limit or API usage quota reached.
500Internal Service error.There was an internal issue with NextBillion.ai services. You can reach out to support@nextbillion.ai for an explanation.