Data and APIs

Blob API, Volatile Blob API, and Interactive API provide APIs to retrieve actual data.

Blob API and Volatile Blob API

Thes Blob API and Volatile Blob API are optimized for high-load and high-throughput workflows. To achieve ultimate performance, applications should use multiple connections to retrieve or upload data in parallel. HERE recommends using a pool of HTTP connections and re-using each connection for multiple requests.


To maintain reasonable quality of service (QoS), the Blob API will reject slow write requests with the HTTP 408 Request timeout status code if the average upload speed is lower than 50 kB/sec. This can be an issue when working with Data API in the China region.

Additionally, when dealing with batch and streaming workloads, it is hard to anticipate a “traffic spike” with a sudden surge in demand, which typically doubles the existing traffic levels in a very short period of time. To continue functioning and meet the existing service level agreement (SLA), the system can return HTTP 429/503status codes for short periods of time, usually up to 10 minutes, and throttle requests from one or more users while it adapts to new request rates.

Interactive API

The Interactive API supports queries by property and spatial queries. If you expect more than 100 MB of data in a response, you can iterate over the result data to retrieve portions in subsequent requests. You can use header ‘accept-encoding: gzip’ to reduce the network traffic.

You can improve the query time by adding relevant properties to the searchableProperties list when configuring your layer. These properties are indexed.


When the layer contains less than 10,000 features, all properties are searchable.

Indexing happens continuously, and no cost for data I/O is incurred. However, indexes are added to the data stored.

The maximum number of searchable properties is eight. This is the maximum number of user-added and automatically indexed properties combined.

results matching ""

    No results matching ""