Get Collection Queryables
const url = 'https://example.com/collections/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/queryables';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/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/queryablesQueryable properties for one feature collection (OGC Features Part 3).
feat(#1614): derived from the live table schema (never the stored
column_info snapshot) so the advertised set always matches what filter=
on /items validates against. additionalProperties: false is what makes
rejecting filters on unlisted properties spec-conformant.
Authorizations
Section titled “ Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”Query Parameters
Section titled “ Query Parameters ”Responses
Section titled “ Responses ”Successful Response
Example generated
exampleDataset table is cold and being rehydrated (multi-tenant); poll the job and retry.
object
Example generated
{ "status": "example", "job_id": "example"}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