Forms API keys
Every API call is authenticated with a personal key. Keys belong to one account and never leave it; a key can read only the forms and responses of its owner.
Create a key
Open API keys and choose Create key. Give it a name so you recognize it later. The raw key appears once, in the creation dialog; copy it then. Only its SHA-256 hash is stored, so the key cannot be shown again.
Keys start with frm_ and an account can hold up to 10 of them.
Domains and call limits
Edit a key to add up to 10 allowed browser hosts, such as example.com or *.myapp.io. A request from another origin is refused with 403. A request without an Origin header, such as a server-to-server call, passes. The list guards against a leaked key used from a browser, not against a determined script.
A key can also carry a hard call limit. Once it is reached the key returns 429 without touching the account's monthly quota. Leave it empty for no per-key cap.
Use the key
Send the key as Authorization: Bearer <key> or in X-API-Key. The key is read-only: it cannot create, edit or delete forms or responses.
Revoke a key
Select Revoke on a key and confirm. Requests using it stop working immediately. Revoking frees a slot toward the 10-key cap.