GetMapGlyphs - Amazon Location Service


Retrieves glyphs used to display labels on a map.

Request Syntax

GET /maps/v0/maps/MapName/glyphs/FontStack/FontUnicodeRange HTTP/1.1

URI Request Parameters

The request uses the following URI parameters.


A comma-separated list of fonts to load glyphs from in order of preference. For example, Noto Sans Regular, Arial Unicode.

Valid fonts stacks for Esri styles:

  • VectorEsriDarkGrayCanvas – Ubuntu Medium Italic | Ubuntu Medium | Ubuntu Italic | Ubuntu Regular | Ubuntu Bold

  • VectorEsriLightGrayCanvas – Ubuntu Italic | Ubuntu Regular | Ubuntu Light | Ubuntu Bold

  • VectorEsriTopographic – Noto Sans Italic | Noto Sans Regular | Noto Sans Bold | Noto Serif Regular | Roboto Condensed Light Italic

  • VectorEsriStreets – Arial Regular | Arial Italic | Arial Bold

  • VectorEsriNavigation – Arial Regular | Arial Italic | Arial Bold

Valid font stacks for HERE Technologies styles:

  • VectorHereContrast – Fira GO Regular | Fira GO Bold

  • VectorHereExplore, VectorHereExploreTruck – Firo GO Italic | Fira GO Map | Fira GO Map Bold | Noto Sans CJK JP Bold | Noto Sans CJK JP Light | Noto Sans CJK JP Regular

Required: Yes


A Unicode range of characters to download glyphs for. Each response will contain 256 characters. For example, 0–255 includes all characters from range U+0000 to 00FF. Must be aligned to multiples of 256.

Pattern: ^[0-9]+-[0-9]+\.pbf$

Required: Yes


The map resource associated with the glyph file.

Length Constraints: Minimum length of 1. Maximum length of 100.

Pattern: ^[-._\w]+$

Required: Yes

Request Body

The request does not have a request body.

Response Syntax

HTTP/1.1 200 Content-Type: ContentType Blob

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The response returns the following HTTP headers.


The map glyph content type. For example, application/octet-stream.

The response returns the following as the HTTP body.


The blob's content type.


For information about the errors that are common to all actions, see Common Errors.


The request was denied because of insufficient access or permissions. Check with an administrator to verify your permissions.

HTTP Status Code: 403


The request has failed to process because of an unknown server error, exception, or failure.

HTTP Status Code: 500


The resource that you've entered was not found in your AWS account.

HTTP Status Code: 404


The request was denied because of request throttling.

HTTP Status Code: 429


The input failed to meet the constraints specified by the AWS service.

HTTP Status Code: 400

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: