# flow2act · Approval inbox

List pending tasks the signed-in person may decide. Integration keys cannot access the inbox.

GET /v1/gate-tasks also lists permitted tasks. GET /v1/approvals includes both approvals and acknowledgments; filter with kind=approval|acknowledgment before cursor pagination. The signed-in flow2act user needs the gate’s assigned approval group. A directory person profile alone grants no approval permission.

## GET /v1/approvals

Authentication: FLOW2ACT_ACCESS_TOKEN from flow2act sign-in
Required tenant header: X-Organization-Id.
Required user permissions: Active workspace membership required. The API checks current membership, roles, key scopes and resource permissions on every request. Documentation visibility grants no access.

## Request example (replace example IDs)

```sh
curl "https://api.flow2act.com/v1/approvals" \
  -H "authorization: Bearer $FLOW2ACT_ACCESS_TOKEN" \
  -H "x-organization-id: 10000000-0000-4000-8000-000000000001"
```

## Response excerpt

```json
{
  "items": [],
  "nextCursor": null
}
```

Source: /docs/approvals
Full schemas: /docs/openapi.json