> ## Documentation Index
> Fetch the complete documentation index at: https://docs.penbox.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Previous-generation Connect API routes (requests, flows, companies) that remain available for backward compatibility.

Before the current Forms API, the Connect API exposed an earlier generation of routes built around `requests`, `flows`, and `companies`. These routes are **still served** for backward compatibility but are no longer part of the main API list above.

<Warning>
  These endpoints are deprecated. They are maintained so existing integrations keep working, but they receive no new features and may be removed in a future major version. **New integrations should use the current endpoints** ([Forms](/api-reference/requests/list-requests), [Form Templates](/api-reference/flows/list-flows), [Workspaces](/api-reference/workspaces/list-workspaces)).
</Warning>

They use the same base URL and the same Bearer-token authentication as the current API:

```text theme={null}
https://connect.penbox.io/v1
```

```bash theme={null}
Authorization: Bearer YOUR_ACCESS_TOKEN
```

## Endpoint mapping

Each previous-version route has a direct equivalent in the current API. Request bodies, query filters, and per-item response shapes are identical — see the current endpoint for the full schema and the interactive "Try It" tool.

### Forms (previously `requests`)

| Previous route         | Current equivalent                                            |
| ---------------------- | ------------------------------------------------------------- |
| `GET /requests`        | [`GET /forms`](/api-reference/requests/list-requests)         |
| `GET /requests/count`  | [`GET /forms/count`](/api-reference/requests/count-requests)  |
| `POST /requests`       | [`POST /forms`](/api-reference/requests/create-request)       |
| `GET /requests/{id}`   | [`GET /forms/{id}`](/api-reference/requests/get-request)      |
| `PATCH /requests/{id}` | [`PATCH /forms/{id}`](/api-reference/requests/update-request) |

### Form Templates (previously `flows`)

| Previous route              | Current equivalent                                                            |
| --------------------------- | ----------------------------------------------------------------------------- |
| `GET /flows`                | [`GET /form_templates`](/api-reference/flows/list-flows)                      |
| `GET /flows/{slug}/options` | [`GET /form_templates/{slug}/options`](/api-reference/flows/get-flow-options) |
| `GET /flows/{slug}/steps`   | [`GET /form_templates/{slug}/steps`](/api-reference/flows/get-flow-steps)     |

### Workspaces (previously `companies`)

| Previous route   | Current equivalent                                             |
| ---------------- | -------------------------------------------------------------- |
| `GET /companies` | [`GET /workspaces`](/api-reference/workspaces/list-workspaces) |

## Key differences

<Note>
  Apart from the path, the only behavioral change is in the **list** endpoints.
</Note>

* **List responses are not paginated.** The previous list routes (`GET /requests`, `GET /flows`, `GET /companies`) return a **bare JSON array**. The current routes wrap results in a pagination envelope (`{ "meta": { ... }, "data": [ ... ] }`).
* **Resource naming.** The previous routes use the older resource names — `requests` (now forms), `flows` (now form templates), and `companies` (now workspaces). The shape of each item is otherwise unchanged.

Unchanged, current-generation routes such as [`GET /responses/{id}`](/api-reference/responses/get-response), [`GET /attachments/{id}`](/api-reference/attachments/get-attachment), and [`GET /signatures/{id}`](/api-reference/signatures/get-signature) are documented in their own sections above and are **not** part of the previous API version.