Open Geospatial Consortium (OGC) Sortables API
list of record properties by which responses can be sorted
list of record properties by which responses can be sorted
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/ogc-sortables-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Ogc Sortables API
version: 1.0.0
contact:
name: CubeWerx Inc.
email: pvretano@cubewerx.com
url: https://www.cubewerx.com
license:
name: CC-BY 4.0 license
url: https://creativecommons.org/licenses/by/4.0/
description: 'Operations tagged Sortables across 3 of this provider''s published API definitions: ogc-records-part1-1-0-openapi-ogcapi-records-1-example-all-in-one.yaml, ogc-records-part1-1-0-openapi-ogcapi-records-1-example-ref-buildingblocks-bundle.yaml, ogc-records-part1-1-0-openapi-ogcapi-records-1-example-ref-schema-repo.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://example.org/data
description: Production server
- url: https://example.org/data-dev
description: Development server
security:
- openIdConnect: []
tags:
- name: Sortables
description: list of record properties by which responses can be sorted
paths:
/collections/{catalogId}/sortables:
get:
tags:
- Sortables
summary: get the list of sortable properties
description: 'Fetch the list of properties which can be used to sort the getRecords
response.'
operationId: getSortables
parameters:
- $ref: '#/components/parameters/catalogId'
- $ref: '#/components/parameters/language'
- $ref: '#/components/parameters/profile'
responses:
'200':
$ref: '#/components/responses/Sortables'
4XX:
$ref: '#/components/responses/BadRequest'
'404':
$ref: '#/components/responses/NotFound'
'406':
$ref: '#/components/responses/NotAcceptable'
5XX:
$ref: '#/components/responses/ServerError'
servers:
- url: https://example.org/data
description: Production server
- url: https://example.org/data-dev
description: Development server
components:
schemas:
exception:
description: 'Imported from OGC API - Features - Part 1: Core
See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/exception.yaml'
type: object
required:
- code
properties:
code:
type: string
description:
type: string
responses:
ServerError:
description: A server error occurred.
content:
application/json:
schema:
$ref: '#/components/schemas/exception'
text/html:
schema:
type: string
NotAcceptable:
description: 'Content negotiation failed. For example, the `Accept` header submitted
in the request did not support any of the media types supported by the
server for the requested resource.'
content:
application/json:
schema:
$ref: '#/components/schemas/exception'
text/html:
schema:
type: string
NotFound:
description: 'The requested resource does not exist on the server. For example,
a path parameter had an incorrect value.'
content:
application/json:
schema:
$ref: '#/components/schemas/exception'
text/html:
schema:
type: string
Sortables:
description: A list of properties by which the server response may be sorted.
content:
application/json:
schema:
type: object
description: A JSON Schema document that defines all the sortables.
text/html:
schema:
type: string
BadRequest:
description: A client error occurred.
content:
application/json:
schema:
$ref: '#/components/schemas/exception'
text/html:
schema:
type: string
parameters:
catalogId:
name: catalogId
in: path
description: local identifier of a catalog
required: true
schema:
type: string
profile:
name: profile
in: query
description: "One or more identifiers that provide information about additional\nsemantics (constraints, conventions, extensions), in addition to \nthose defined by the media type, that are associated with the\ntarget resource."
required: false
schema:
type: array
items:
type: string
explode: false
style: form
language:
name: language
in: query
description: 'Optional way to query for specific languages for environments that can''t
send HTTP headers in a simple way (e.g. a Web Browser).
The parameter accepts a comma-separated list of language identifiers,
optionally with priority per language.
This parameter value follows the specification of the `Accept-Language`
HTTP header.'
schema:
type: array
items:
type: string
description: 'The language tag as per RFC 5646, with optional priority parameter
`q` (0 - 1).'
pattern: ^((?:(en-GB-oed|i-ami|i-bnn|i-default|i-enochian|i-hak|i-klingon|i-lux|i-mingo|i-navajo|i-pwn|i-tao|i-tay|i-tsu|sgn-BE-FR|sgn-BE-NL|sgn-CH-DE)|(art-lojban|cel-gaulish|no-bok|no-nyn|zh-guoyu|zh-hakka|zh-min|zh-min-nan|zh-xiang))|((?:([A-Za-z]{2,3}(-(?:[A-Za-z]{3}(-[A-Za-z]{3}){0,2}))?)|[A-Za-z]{4}|[A-Za-z]{5,8})(-(?:[A-Za-z]{4}))?(-(?:[A-Za-z]{2}|[0-9]{3}))?(-(?:[A-Za-z0-9]{5,8}|[0-9][A-Za-z0-9]{3}))*(-(?:[0-9A-WY-Za-wy-z](-[A-Za-z0-9]{2,8})+))*(-(?:x(-[A-Za-z0-9]{1,8})+))?)|(?:x(-[A-Za-z0-9]{1,8})+))(?:;q=(?:1|1\.0+|0|0\.[0-9]+))?$
explode: false
style: form
securitySchemes:
openIdConnect:
type: openIdConnect
openIdConnectUrl: https://accounts.google.com/.well-known/openid-configuration
x-refined-from:
- ogc-records-part1-1-0-openapi-ogcapi-records-1-example-all-in-one.yaml
- ogc-records-part1-1-0-openapi-ogcapi-records-1-example-ref-buildingblocks-bundle.yaml
- ogc-records-part1-1-0-openapi-ogcapi-records-1-example-ref-schema-repo.yaml