Landing page with links (STAC API root)
const url = 'https://api.satellitedata.net/v1';const options = {method: 'GET'};
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/v1Returns the STAC API landing page: the catalog id, the conformance classes the API implements, and links to collections, search, queryables, the OpenAPI document and the docs. STAC clients such as pystac-client start here. Free, anonymous and cached for 10 minutes at CloudFront.
Responses
Section titled “Responses”Landing page.
STAC API landing page.
object
Always Catalog.
Catalog id.
Catalog title.
Catalog description.
STAC version of the API.
Conformance class URIs, also served at /v1/conformance.
Version of schema v1 behind the API, as in GET /v1/schema.
Links to every top-level resource.
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.
Example
{ "type": "Catalog", "id": "satellitedata-net", "title": "satellitedata.net", "description": "Free unified API for Sentinel and Landsat pixels.", "stac_version": "1.1.0", "conformsTo": [ "https://api.stacspec.org/v1.0.0/core", "https://api.stacspec.org/v1.0.0/collections", "https://api.stacspec.org/v1.0.0/ogcapi-features", "https://api.stacspec.org/v1.0.0/item-search", "https://api.stacspec.org/v1.0.0/item-search#fields", "https://api.stacspec.org/v1.0.0/item-search#sort", "https://api.stacspec.org/v1.0.0-rc.2/item-search#filter", "http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/core", "http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/geojson", "http://www.opengis.net/spec/ogcapi-features-3/1.0/conf/filter", "http://www.opengis.net/spec/cql2/1.0/conf/basic-cql2", "http://www.opengis.net/spec/cql2/1.0/conf/cql2-text", "http://www.opengis.net/spec/cql2/1.0/conf/cql2-json" ], "sdn:schemaVersion": "1.0.0", "links": [ { "href": "https://api.satellitedata.net/v1", "rel": "self", "type": "application/json" }, { "href": "https://api.satellitedata.net/v1", "rel": "root", "type": "application/json" }, { "href": "https://api.satellitedata.net/v1/conformance", "rel": "conformance", "type": "application/json" }, { "href": "https://api.satellitedata.net/v1/collections", "rel": "data", "type": "application/json" }, { "href": "https://api.satellitedata.net/v1/search", "rel": "search", "type": "application/geo+json", "method": "GET" }, { "href": "https://api.satellitedata.net/v1/search", "rel": "search", "type": "application/geo+json", "method": "POST" }, { "href": "https://api.satellitedata.net/v1/openapi.json", "rel": "service-desc", "type": "application/vnd.oai.openapi+json;version=3.1" }, { "href": "https://docs.satellitedata.net/", "rel": "service-doc", "type": "text/html" }, { "href": "https://api.satellitedata.net/v1/schema", "rel": "describedby", "type": "application/json", "title": "Schema v1" } ]}Headers
Section titled “Headers”Request id for support and logs.
Example
01JQ7Z3M8R5V2W6X9Y0A1B2C3DEntity tag; includes the render version.
Example
"r3-9f2c1a"Caching policy for CloudFront and browsers.
Example
public, max-age=3600, s-maxage=2592000, stale-if-error=604800A per-minute, concurrency, monthly or per-IP limit was hit. Retry-After says when to retry.
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
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
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
17Remaining units and seconds to reset in the current window (IETF RateLimit header draft).
Example
"units";r=287;t=41Quota policy of the caller (IETF RateLimit header draft).
Example
"units";q=300;w=60An 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
Units the request would have cost, computed before execution.
OAuth 2.0 error code (RFC 6749 section 5.2). Present only on /oauth/token responses.
OAuth 2.0 error description. Present only on /oauth/token responses.
Copy of detail for openEO clients, which read message. Present only on /v1/openeo routes.
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
01JQ7Z3M8R5V2W6X9Y0A1B2C3D