STAC item search, cql2-text
const url = 'https://api.satellitedata.net/v1/search?collections=sentinel-2-l2a&ids=S2C_T15TVK_20260712T171233_L2A&bbox=-93.3%2C44.9%2C-93.2%2C45&intersects=%7B%22type%22%3A%22Point%22%2C%22coordinates%22%3A%5B-93.25%2C44.95%5D%7D&datetime=2026-06-01T00%3A00%3A00Z%2F2026-08-31T23%3A59%3A59Z&limit=10&token=2026-08-29T10%3A56%3A03.794000Z%2CS2A_T31TCF_20260829T105044_L2A%2Csentinel-2-c1-l2a&sortby=%2Bproperties.eo%3Acloud_cover&fields=id%2Cproperties.datetime%2Cproperties.eo%3Acloud_cover&query=%7B%22eo%3Acloud_cover%22%3A%7B%22lte%22%3A20%7D%7D';const options = {method: 'GET', headers: {'X-API-Key': '<X-API-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.satellitedata.net/v1/search?collections=sentinel-2-l2a&ids=S2C_T15TVK_20260712T171233_L2A&bbox=-93.3%2C44.9%2C-93.2%2C45&intersects=%7B%22type%22%3A%22Point%22%2C%22coordinates%22%3A%5B-93.25%2C44.95%5D%7D&datetime=2026-06-01T00%3A00%3A00Z%2F2026-08-31T23%3A59%3A59Z&limit=10&token=2026-08-29T10%3A56%3A03.794000Z%2CS2A_T31TCF_20260829T105044_L2A%2Csentinel-2-c1-l2a&sortby=%2Bproperties.eo%3Acloud_cover&fields=id%2Cproperties.datetime%2Cproperties.eo%3Acloud_cover&query=%7B%22eo%3Acloud_cover%22%3A%7B%22lte%22%3A20%7D%7D' \ --header 'X-API-Key: <X-API-Key>'STAC search on Earth Search. collections take ids or aliases (default both lean collections); cloud filter through the query extension; paging links carry token.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Collection ids or aliases.
Example
?collections=sentinel-2-l2aItem ids.
Example
?ids=S2C_T15TVK_20260712T171233_L2AWest, south, east, north in CRS84.
Example
?bbox=-93.3,44.9,-93.2,45GeoJSON geometry as URL-encoded JSON text; mutually exclusive with bbox.
Example
{"type":"Point","coordinates":[-93.25,44.95]}RFC 3339 instant or interval (dates alone are allowed); an open end is written .. . Tiles default to the last 30 days.
Example
2026-06-01T00:00:00Z/2026-08-31T23:59:59ZPage size.
Example
10Opaque paging token from a next or prev link.
Example
2026-08-29T10:56:03.794000Z,S2A_T31TCF_20260829T105044_L2A,sentinel-2-c1-l2aComma-separated sort fields, each prefixed + or -. Default -datetime.
Example
+properties.eo:cloud_coverFields extension: comma-separated fields, prefixed - to exclude.
Example
id,properties.datetime,properties.eo:cloud_coverSTAC query extension as URL-encoded JSON, for example {“eo:cloud_cover”:{“lte”:20}}.
Example
{"eo:cloud_cover":{"lte":20}}Responses
Section titled “Responses”One page of matching items.
STAC item collection, one page of results.
object
Always FeatureCollection.
Matching items, at most limit.
STAC item.
object
Always Feature.
STAC version.
Extensions.
Native upstream item id.
Collection id.
Bounding box as [west, south, east, north] in CRS84 longitude and latitude, or six numbers with heights.
Item properties. Any property listed by queryables can appear; the common ones are named here.
object
Acquisition time, UTC.
Normalized lowercase platform, for example sentinel-2c or landsat-9.
Constellation.
Instruments.
Scene cloud cover percentage from the producer.
Sentinel-2 MGRS tile.
Sentinel-2 processing baseline, which decides the DN offset.
Landsat WRS-2 path.
Landsat WRS-2 row.
Native collection of an item returned through optical-sr.
Cloud-mask source for the item.
Mask classes the item can detect.
Harmonization level that applies to this item at the collection default.
Assets keyed by native band name or role.
object
STAC asset. href points at the public upstream COG.
object
Asset URL.
Media type.
Title.
Asset roles such as data, overview or cloud.
Band name the asset holds, when it holds one band.
Links, including self, collection and preview.
A STAC and OGC API link object.
object
Link target.
Relation type, such as self, root, parent, next, prev, items, queryables, tiles or license.
Media type of the target.
Human-readable title.
HTTP method for the link, GET unless stated. Paging POST /v1/search uses POST.
Request body to send with a POST link, used for the next page of POST /v1/search.
object
When true the client merges body into the previous request body.
Paging links: next and prev carry the token.
A STAC and OGC API link object.
object
Link target.
Relation type, such as self, root, parent, next, prev, items, queryables, tiles or license.
Media type of the target.
Human-readable title.
HTTP method for the link, GET unless stated. Paging POST /v1/search uses POST.
Request body to send with a POST link, used for the next page of POST /v1/search.
object
When true the client merges body into the previous request body.
Total matches, present when under 10,000.
Items in this page.
Example
{ "type": "FeatureCollection", "features": [ { "type": "Feature", "geometry": { "type": "Point" }, "properties": { "sdn:source_collection": "sentinel-2-l2a", "sdn:mask_source": "scl", "sdn:harmonization": "none" }, "links": [ { "method": "GET" } ] } ], "links": [ { "method": "GET" } ]}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DThe request is malformed or a parameter is invalid.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Example
{ "type": "https://docs.satellitedata.net/problems/invalid-parameter", "title": "Invalid parameter", "status": 400, "detail": "bbox must have 4 or 6 numbers; got 3.", "instance": "/v1/search", "code": "invalid-parameter", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "errors": [ { "pointer": "bbox", "detail": "expected 4 or 6 numbers" } ]}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DThe X-API-Key header is missing or the key is unknown, disabled or not on this API’s usage plan.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Example
{ "type": "https://docs.satellitedata.net/problems/invalid-key", "title": "Invalid or missing credentials", "status": 401, "detail": "Send a valid key in the X-API-Key header.", "instance": "/v1/search", "code": "invalid-key", "requestId": "c1d2e3f4-0000-4a5b-8c9d-0123456789ab"}Headers
Section titled “Headers”Challenge naming the accepted scheme.
Example
ApiKey header="X-API-Key"The key’s rate limit or monthly quota (usage plan satdata-personal) was hit.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Example
{ "type": "https://docs.satellitedata.net/problems/rate-limited", "title": "Rate limit exceeded", "status": 429, "detail": "This key spent 300 of its 300 units in the current minute.", "instance": "/v1/process", "code": "rate-limited", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "retryAfter": 17, "limits": { "unitsPerMinute": 300, "unitsSpentThisMinute": 300 }}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DSeconds to wait before retrying.
Example
17An unexpected server error. No units are charged.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Example
{ "type": "https://docs.satellitedata.net/problems/internal", "title": "Internal error", "status": 500, "detail": "The request failed on our side and was logged. No units were charged.", "instance": "/v1/process", "code": "internal", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D"}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DEarth Search or the renderer is unavailable.
RFC 9457 problem details. Every 4xx and 5xx response uses this shape with media type application/problem+json. The type URL opens a documentation page that explains the cause and the fix.
object
URL of the documentation page for this problem type, stable for the life of /v1.
Short summary of the problem type. It does not change between occurrences.
HTTP status code, repeated for clients that lose the status line.
Explanation specific to this occurrence, written for a developer.
Path of the request that failed.
Machine-readable problem code; equals the last path segment of type.
Request id, also sent in X-Request-Id. Quote it in support requests.
Field-level validation failures, present on 400 and 422.
One field-level failure.
object
JSON Pointer (RFC 6901) into the request body, or the query parameter name.
What is wrong with that member.
Seconds until the request can succeed; equals the Retry-After header.
The limit that was hit and the value requested, for example maxWidth and requestedWidth.
object
Example
{ "type": "https://docs.satellitedata.net/problems/upstream-unavailable", "title": "Upstream unavailable", "status": 503, "detail": "Earth Search did not answer: ReadTimeout", "instance": "/v1/process", "code": "upstream-unavailable", "requestId": "01JQ7Z3M8R5V2W6X9Y0A1B2C3D", "retryAfter": 120}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DSeconds to wait before retrying.
Example
17