Get Collections
const url = 'https://example.com/stac/collections';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://example.com/stac/collectionsList all STAC Collections.
Responses
Section titled “ Responses ”Successful Response
STAC collections list response.
object
List of STAC collections.
A single STAC Collection response (permissive — allows extra STAC fields).
object
STAC object type.
STAC specification version.
Stable collection identifier.
Collection description.
SPDX license identifier or ‘proprietary’.
Spatial and temporal extent of items in the collection.
object
Collection navigation links.
A single STAC link object.
Top-level collection navigation links.
A single STAC link object.
Example
{ "collections": [ { "type": "Collection", "stac_version": "1.0.0", "description": "", "license": "proprietary" } ]}Bad request — invalid standards parameters
Unauthenticated — a credential was supplied and could not be resolved (expired, revoked, or malformed). Sending no credential at all is not an error on these operations; they answer anonymously with the public subset. Neither is sending an unresolvable credential alongside a capability that authorizes the request on its own — a valid X-Embed-Token or a valid signed tile template (sig, exp, scope). Those are served and the unrelated credential is ignored.
Too many requests — retry after the advertised interval
Headers
Section titled “Headers ”Seconds until the request may be retried
Internal server error
Service unavailable — the database could not serve the request