# List operations

> The operations one integration exposes, by id and title.

Source: https://docs.generalinput.com/api/integrations/list-operations



<Endpoint method="GET" path="/v1/integrations/:service/operations" />

<Access scope="docs:read" />

One row per documented call on the service. Take an `id` to [get the operation](/api/integrations/get-operation) for its reference.

## Path parameters [#path-parameters]

| Name      | Notes                 |
| --------- | --------------------- |
| `service` | The integration slug. |

## Response [#response]

```json
{
  "operations": [
    {
      "id": "4c21e1ee-4d54-4413-a4f2-80a80dff4c99",
      "title": "Send a Message",
      "description": "Sends a message to a channel, DM, or group conversation."
    }
  ]
}
```

Operation ids are UUIDs and are stable across services: the same id resolves through [`GET /v1/operations/:opId`](/api/integrations/get-operation-by-id) without the service prefix.

## Errors [#errors]

| Status | When                           |
| ------ | ------------------------------ |
| `404`  | No integration with that slug. |