---
title: "retrieve a process description"
method: GET
path: "/processes/{processID}"
tags: ["ProcessDescription"]
---

# retrieve a process description

`GET /processes/{processID}`

The process description contains information about inputs and outputs and a link to the execution-endpoint for the process. The Core does not mandate the use of a specific process description to specify the interface of a process. That said, the Core requirements class makes the following recommendation:

Implementations SHOULD consider supporting the OGC process description.

For more information, see [Section 7.8](http://docs.ogc.org/DRAFTS/18-062.html#sc_process_description).

## Parameters

- `https://raw.githubusercontent.com/opengeospatial/ogcapi-processes/master/core/openapi/parameters/processIdPathParam.yaml` — unresolved $ref

## Other responses

- `200` — unresolved $ref
- `404` — unresolved $ref

## Changes

- **2022-06-24** `6e199f8a91c5` — 3 breaking, 1 warning, 2 info
  - removed the media type `application/json` for the response with the status `200`
  - removed the media type `application/json` for the response with the status `404`
  - removed the media type `text/html` for the response with the status `404`
  - deleted the `path` request parameter `processID`
  - …2 more

[Change history](https://skmtc.dev/bbox-services/apis/ogc-api-processes-part-1-core/changes/processes/:processID/get.md)

---

[API](https://skmtc.dev/bbox-services/apis/ogc-api-processes-part-1-core.md) · [All operations](https://skmtc.dev/bbox-services/apis/ogc-api-processes-part-1-core/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/bbox-services/ogc-api-processes-part-1-core/revisions/6e199f8a91c5/schema)