Skip to main content
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.
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, Form Templates, Workspaces).
They use the same base URL and the same Bearer-token authentication as the current API:

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

​
Form Templates (previously flows)

​
Workspaces (previously companies)

​
Key differences

Apart from the path, the only behavioral change is in the list endpoints.
  • 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}, GET /attachments/{id}, and GET /signatures/{id} are documented in their own sections above and are not part of the previous API version.