API routing calls your server while someone fills in the form. Your server looks at the answers, for example to check a customer ID in your CRM, and replies with where to send them next.
Open API routing
In the Outline panel, open API routing.
Choose when it runs
Run it after a particular page, or After submission (chooses the end
page).
Add your endpoint
Enter your URL (https://…), any headers (for example Authorization: Bearer …), the response path to read (default next) and a timeout
between 3 and 30 seconds.
Verify requests
Copy the signing secret. Every request carries an X-Finerlise-Signature: sha256=… header that you can check. See the API routing
reference.
Return JSON. Finerlise reads the value at your response path, for example { "next": "Book a call" }.
Reply with an error to keep the respondent on the current page and show them your message (up to 280 characters):
{ "error": "We couldn't find that customer ID." }
If your server is slow, unreachable or replies with something Finerlise can’t read, the form carries on as if no routing was set, so respondents are never stuck.
Add an API response block (/api) to save a value from your server’s reply with the submission, for example a customer tier. Set its API response key to a key in the reply’s fields object:
{
"next": "Book a call",
"fields": { "tier": "gold", "account_manager": "Sam" }
}
Values can be text, numbers or true/false, up to 500 characters each.
