---
title: "Supported secondary web service protocols"
method: GET
path: "/service_types"
tags: ["Capabilities", "Secondary Services"]
---

# Supported secondary web service protocols

`GET /service_types`

Lists supported secondary web service protocols such as
[OGC WMS](http://www.opengeospatial.org/standards/wms),
[OGC WCS](http://www.opengeospatial.org/standards/wcs),
[OGC API - Features](https://www.ogc.org/standards/ogcapi-features)
or [XYZ tiles](https://wiki.openstreetmap.org/wiki/Slippy_map_tilenames).
The response is an object of all available secondary web service protocols
with their supported configuration settings and expected process parameters.

* The configuration settings for the service SHOULD be defined upon
  creation of a service and the service will be set up accordingly.
* The process parameters SHOULD be referenced (with a `from_parameter`
  reference) in the user-defined process that is used to compute web service
  results.
  The appropriate arguments MUST be provided to the user-defined process,
  usually at runtime from the context of the web service.
  For example, a map service such as a WMS would
  need to inject the spatial extent into the user-defined process so that the
  back-end can compute the corresponding tile correctly.

To improve interoperability between back-ends common names for the
services SHOULD be used, e.g. the abbreviations used in the official
[OGC Schema Repository](http://schemas.opengis.net/) for the respective
services.

Service names MUST be accepted in a *case insensitive* manner throughout the API.

## Response `200`

An object with a map containing all service names as keys and an object that defines supported configuration settings and process parameters.

- object — Map of supported secondary web services.

## 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)

## Changes

- **2025-09-08** `14b9824d2788` — 2 info
  - added the required property `additionalProperties/process_parameters/items/schema/oneOf[subschema #1: Single Data Type]/oneOf[subschema #3: Datacube]/dimensions/items/type` to the response with the `200` status
  - added the required property `additionalProperties/process_parameters/items/schema/oneOf[subschema #2: Multiple data types]/items/oneOf[subschema #3: Datacube]/dimensions/items/type` to the response with the `200` status
- **2023-07-07** `a5a4894f6ec8` — 2 info
  - added `#/components/schemas/json_schema` to the `additionalProperties/configuration/additionalProperties/` response property `allOf` list for the response status `200`
  - removed `#/components/schemas/process_json_schema` from the `additionalProperties/configuration/additionalProperties/` response property `allOf` list for the response status `200`
- …earlier changes not shown

[Full history](https://skmtc.dev/open-eo/apis/openeo-api/changes/service_types/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/0c5e31955a19/schema)