Get Collection Items
const url = 'https://example.com/stac/collections/example/items?limit=10&offset=0';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/collections/example/items?limit=10&offset=0'List STAC Items within a collection.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Query Parameters
Section titled “Query Parameters ”Maximum number of items returned. Values above 200 are clamped to 200, per the STAC Item Search spec’s clamp-don’t-reject recommendation.
Maximum number of items returned. Values above 200 are clamped to 200, per the STAC Item Search spec’s clamp-don’t-reject recommendation.
Legacy offset-based pagination. Phase 269 H-24 lowered the max limit to 200 and recommends keyset cursors via the rel=next link for deep paging.
Legacy offset-based pagination. Phase 269 H-24 lowered the max limit to 200 and recommends keyset cursors via the rel=next link for deep paging.
Responses
Section titled “ Responses ”Successful Response
Typed OpenAPI representation of a STAC ItemCollection.
object
A GeoJSON Feature conforming to the STAC Item specification.
object
STAC specification version.
STAC extension schema URIs in use.
Stable item identifier.
A GeoJSON GeometryCollection (RFC 7946 §3.1.8).
fix(#430 codex r9): carries geometries instead of coordinates, so
it needs its own model — only generic-GEOMETRY datasets accept it on write
(enforced in the service), and any stored collection must serialize back
out on read.
Deliberately NON-recursive (codex r13, refuted): PostGIS cannot round-trip nested collections through the GeoJSON boundary in either direction — ST_GeomFromGeoJSON rejects them on write and ST_AsGeoJSON raises ‘GeoJson: geometry not supported’ on read — so a recursive model could never receive one and would only convert the write-side 422 into a raw database 500. The write schemas add a raw-payload guard for a clear 422.
object
A GeoJSON geometry object (RFC 7946).
object
A GeoJSON geometry object (RFC 7946).
object
Core STAC Item properties plus extension-defined fields.
object
A STAC asset attached to an Item.
Paging metadata emitted with STAC ItemCollections.
object
Example
{ "context": { "limit": 10, "matched": 0, "returned": 0 }, "features": [], "links": [], "numberMatched": 0, "numberReturned": 0, "type": "FeatureCollection"}Bad request — invalid query parameters or payload
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.
Not found
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