You can make your access tokens for web maps more secure by adding URL restrictions. When creating an access token, you will have the option to add public or private scopes to the token.įor a complete list of available scopes and recommendations see the Account documentation. The API documentation lists the scopes required for each Mapbox API. For more information on the metadata object’s properties, see our Tokens API documentation ScopesĮach access token you create will have a set of permissions that allow the token to make certain types of requests to Mapbox APIs - these are called scopes.

Every token has a metadata object that contains properties with information about the token, like id (unique identifier), note (human readable name), scopes (capabilities), allowedURLs (URLs that token is authorized for), and timestamps for created and modified (last modification). Each token is a string delimited by dots into three parts: header, payload, and signature as described in the Tokens API documentation. Mapbox uses JSON Web Tokens (JWT) as the token format. You can find your access tokens, create new ones, or delete existing ones on your Access Tokens page or programmatically using the Mapbox Tokens API. Mapbox uses access tokens to associate API requests with your account. To use any of Mapbox's tools, APIs, or SDKs, you'll need a Mapbox access token.

Free appnana token id