High-volume Endpoint

If you're making lots of automated requests to Earth Engine, you should consider using the high-volume endpoint. This service is designed to support a much larger number of simultaneous requests per user, but provides less caching, so it's best for small queries that don't involve any sort of aggregation (like fetching tiles from pre-built images). Because there's less caching, intermediate results often need to be recomputed on the high-volume endpoint. Complex queries typically require more EECU-time when using the high-volume endpoint than they do in the regular online endpoint.

The high-volume endpoint does not affect the batch system or the number of concurrent exports you can run.

If you are making requests that exceed the default quota for the Earth Engine service, you will receive a Quota exceeded error. To avoid that error, you may apply to get higher QPS from the high volume endpoint. If you are granted higher QPS quota, the increased quota only applies to automated requests to the high-volume endpoint. It does NOT increase the number of concurrent tasks (exports) you are able to run.

To obtain high QPS from the high-volume endpoint, your application for increased QPS quota must first be approved by the Earth Engine team.

Using the high-volume endpoint

REST API

Direct your REST requests to https://earthengine-highvolume.googleapis.com (instead of https://earthengine.googleapis.com, as shown in the REST API Quickstart, for example).

Python

When initializing the EE library pass in an opt_url parameter and set it to https://earthengine-highvolume.googleapis.com. As always, be sure to also pass in proper credentials and specify the Cloud Project. For example:

ee.Initialize(
  credentials=credentials,
  project=project,
  opt_url='https://earthengine-highvolume.googleapis.com'
)

JavaScript

When initializing the EE library using ee.initialize(), pass https://earthengine-highvolume.googleapis.com for the first parameter.