Formtorch now has a public REST API. You can read submissions and forms programmatically from any language or tool that speaks HTTP, authenticated with a long-lived API key generated from your workspace settings.

API keys

API keys are managed under Settings → API Keys. When you create a key, the full value is shown once, copy it into your environment before leaving the page. Formtorch stores only a secure hash, so the plaintext cannot be recovered later.

Each key shows an 8-character preview of the key prefix (e.g. ft_AbCdEfGh…) so you can identify keys without exposing the full value. The Last used timestamp updates on every authenticated request, making it easy to spot keys that are no longer active. You can revoke any key immediately from the same screen; the key stops working on the next request.

Include the key as a Bearer token on every API request:

Authorization: Bearer ft_…

REST API — /v1/

The API is available at https://api.formtorch.com/v1/. All responses are JSON. Errors follow a consistent shape:

{ "error": "Form not found.", "code": "not_found" }

Authentication failures return 401. Authorization failures (valid key, wrong workspace) return 403. Rate limit breaches return 429 with a Retry-After header.

Endpoints

• GET /v1/forms — list all forms in your workspace
• GET /v1/forms/:id — retrieve a single form
• GET /v1/forms/:id/submissions — list submissions for a form

These are read-first endpoints. Write endpoints are on the roadmap.

Pagination

All list endpoints use cursor-based pagination. Pass ?cursor=<value> from the previous response's next_cursor field to fetch the next page. The limit parameter controls how many records are returned per page, up to the maximum allowed by your plan.

Rate-limit headers

Every response includes:

• X-RateLimit-Limit — requests allowed in the current window
• X-RateLimit-Remaining — requests left in the current window
• X-RateLimit-Reset — Unix timestamp when the window resets

Plan enforcement

API access, maximum page size, and rate limits vary by plan. If you need higher throughput or larger page sizes, upgrading your plan raises all three limits automatically. Requests that exceed your plan's rate limit return 429 with a Retry-After header indicating when you can retry.

API access is available on the Starter and Pro plans. For endpoint reference, pagination details, and code examples, see the API docs.