Skip to main content
The Formable API authenticates requests with a Bearer token in the Authorization header. Create an API key in Settings, then send it on every request.

Get an API key

API keys belong to an organization. Create one in the Formable app, then copy the key when it’s shown. For detailed steps, see Set up a developer account.
1

Create an organization

Go to Settings and create an organization if you don’t have one yet. You need an organization before you can generate keys or register webhooks.
2

Generate a key

In the API keys section, click Generate key, give it a name, and confirm.
3

Copy the key

Copy the full key immediately and store it as an environment secret. Formable shows it once — after you close the dialog, only a short prefix (for example fmbl_a1b2c3d4...) remains visible.
Never expose API keys in browser or mobile code. Call the API from your backend, and only pass short-lived signing and redline URLs to the client.
You can rename or delete keys from the same Settings page. Deleting a key revokes it immediately. Each account can have up to 10 active keys.

Use the key

Include the key in the Authorization header of every API request.
The Node, Python, PHP, Java, Go, Ruby, and .NET SDKs send this header for you. Keys start with fmbl_. Treat them like passwords: store them in a secrets manager, rotate by creating a new key and deleting the old one, and never commit them to source control.

Base URL

All endpoints are served under this base URL, so a full path looks like https://api.formabledocs.com/v1/signature-requests.

Authorization errors

Requests fail with a 401 when the bearer token is missing, malformed, revoked, or expired:
A 403 means the token is valid but your organization isn’t authorized for the resource — for example, creating an edit URL for a template that belongs to another organization.