---
title: "OGC specifications this API conforms to"
method: GET
path: "/conformance"
tags: ["Capabilities"]
---

# OGC specifications this API conforms to

`GET /conformance`

Lists all conformance classes specified in OGC standards that the server conforms to.
This endpoint is only required if full compliance with OGC API standards is desired. Therefore, openEO back-ends MAY implement it for compatibility with OGC API clients and openEO clients don't need to request it.

## Response `200`

The URIs of all conformance classes supported by the server.

- object
  - `conformsTo` string[], required

## Other responses

- `5XX` — The request can't 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)

## Changes

- **2022-11-03** `86d3896dd3c8` — 1 info
  - the endpoint scheme security `Bearer` was removed from the API

[Change history](https://skmtc.dev/open-eo/apis/openeo-api/changes/conformance/get.md)

---

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