List Collections
const url = 'https://example.com/collections?offset=0&limit=50';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/collections?offset=0&limit=50'List available OGC collections (catalog + per-dataset feature collections).
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Pagination offset for per-dataset collections
Pagination offset for per-dataset collections
Max per-dataset collections to return
Max per-dataset collections to return
Responses
Section titled “ Responses ”Successful Response
Response for /collections listing all available OGC collections.
object
object
Link object in OGC API Records.
object
Example
{ "links": []}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