How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Google Earth Engine REST Projects API

The Projects API from Google Earth Engine REST — 10 operation(s) for projects.

Google Earth Engine REST Projects API is published by Google Earth Engine REST on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Project. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, and 1 JSON Schema.

This API exposes 11 operations across 10 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://earthengine.googleapis.com/v1.

11 operations 10 paths 2 schemas 1 DELETE4 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://earthengine.googleapis.com/v1
Authentication
OAuth 2.0
Contact
Resource Areas
1

Authentication & Security 1

Google Earth Engine REST Projects API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 3 scopes. By default, every request must be authenticated.

Paths & Operations 11

Across 10 paths, the API surfaces 11 operations — 1 DELETE, 4 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Projects 11
GET
/projects/{project}/assets
List assets
listAssets 3 params → 200
GET
/projects/{project}/assets/{assetId}
Get an asset
getAsset 2 params → 200
DELETE
/projects/{project}/assets/{assetId}
Delete an asset
deleteAsset 2 params → 200
POST
/projects/{project}/image:computePixels
Compute pixels
computePixels 1 param body → 200
POST
/projects/{project}/image:export
Export an image
exportImage 1 param body → 200
POST
/projects/{project}/table:computeFeatures
Compute features
computeFeatures 1 param body → 200
POST
/projects/{project}/table:export
Export a table
exportTable 1 param body → 200
POST
/projects/{project}/value:compute
Compute a value
computeValue 1 param body → 200
POST
/projects/{project}/maps
Create a map
createMap 1 param body → 200
GET
/projects/{project}/operations
List operations
listOperations 3 params → 200
GET
/projects/{project}/operations/{operationId}
Get an operation
getOperation 2 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are EarthEngineAsset (12 properties), ListAssetsResponse (2 properties). Each schema is shown below with its type and property counts.

EarthEngineAsset
object
12 properties
ListAssetsResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

google-earth-engine-projects-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Google Earth Engine REST Projects API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.