---
title: "Conformance classes this API implements"
method: GET
path: "/conformance"
tags: ["Capabilities"]
---

# Conformance classes this API implements

`GET /conformance`

Lists all conformance classes specified in various standards that the
implementation conforms to. Conformance classes are commonly used in
all OGC API standards and the STAC API specification. openEO adds relatively
broadly defined conformance classes, especially for the extensions.
Otherwise, the implemented functionality can usually be retrieved from
the [capabilities](#tag/Capabilities/operation/capabilities) in openEO.

The general openEO conformance class is `https://api.openeo.org/1.3.0`.
See the individual openEO API extensions for their conformance classes.

The conformance classes listed at this endpoint and listed in the 
corresponding `conformsTo` property in `GET /` MUST be equal.

More details:
- [STAC API](https://github.com/radiantearth/stac-api-spec), especially the conformance class "STAC API - Collections"
- [OGC API standards](https://ogcapi.ogc.org/)

## Response `200`

The URIs of all conformance classes supported by the server.

- object
  - `conformsTo` string[], required — Lists all conformance classes specified in various standards that the implementation conforms to. Conformance classes are commonly used in all OGC API standards and the STAC API specification. The general openEO conformance class is `https://api.openeo.org/1.3.0`. See the individual openEO API extensions for their conformance classes.

## 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 usually does not respond with HTTP status codes 401 and 403 due to missing authorization. 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/versions/0c5e31955a19/schema)