---
title: "Metadata filters for a specific dataset"
method: GET
path: "/collections/{collection_id}/queryables"
tags: ["EO Data Discovery"]
---

# Metadata filters for a specific dataset

`GET /collections/{collection_id}/queryables`

Lists **all** supported metadata filters (also called "queryables") for
a specific collection.

This endpoint is compatible with the endpoint defined in the STAC API extension
[`filter`](https://github.com/stac-api-extensions/filter#queryables) and
[OGC API - Features - Part 3: Filtering](https://github.com/opengeospatial/ogcapi-features/tree/master/extensions/filtering).
For a precise definition please follow those specifications.

This endpoints provides a JSON Schema for each queryable that openEO
users can use in multiple scenarios:
1. For loading data from the collection, e.g. in the process `load_collection`.
2. For filtering items using CQL2 on the `/collections/{collection_id}/items` endpoint
   (if [STAC API - Features is implemented in addition to the openEO API](#tag/EO-Data-Discovery/STAC)).

Note: Providing the Bearer token is REQUIRED for private collections.

## Path parameters

- `collection_id` string, required — A unique identifier for the collection, which MUST match the specified pattern.

## Response `200`

A JSON Schema defining the queryables.

It is RECOMMENDED to dereference all "$refs".

## Other responses

- `4XX` — The request can not be fulfilled due to an error on client-side, i.e. the request is invalid. The client SHOULD NOT repeat the request without modifications. The response body SHOULD contain a JSON error object. MUST be any HTTP status code specified in [RFC 7231](https://www.rfc-editor.org/rfc/rfc7231.html#section-6.6). This request MUST respond with HTTP status codes 401 if authorization is required or 403 if the authorization failed or access is forbidden in general to the authenticated user. HTTP status code 404 SHOULD be used if the value of a path parameter is invalid. See also: * [Error Handling](#section/API-Principles/Error-Handling) in the API in general. * [Common Error Codes](errors.json)
- `5XX` — The request can not be fulfilled due to an error at the back-end. The error is never the client’s fault and therefore it is reasonable for the client to retry the exact same request that triggered this response. The response body SHOULD contain a JSON error object. MUST be any HTTP status code specified in [RFC 7231](https://www.rfc-editor.org/rfc/rfc7231.html#section-6.6). See also: * [Error Handling](#section/API-Principles/Error-Handling) in the API in general. * [Common Error Codes](errors.json)

---

[API](https://skmtc.net/open-eo/apis/openeo-api.md) · [All operations](https://skmtc.net/open-eo/apis/openeo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/open-eo/openeo-api/revisions/0c5e31955a19/schema)