Widgets
Submit Saved Form
Submit a saved signup form and create or update a subscriber.
POST
Submit Saved Form
Submit Saved Form
You can submit a saved signup form created in the dashboard without an API key. The endpoint acceptsapplication/x-www-form-urlencoded form posts and JSON.
The form’s stored settings are the source of truth for audience targeting (lists, tags) and success behavior (success message or redirect URL). When you change those settings in the dashboard, deployed embeds pick them up automatically - no re-embedding needed. List, tag, and redirect values in the request are ignored.
Request
The saved form ID. You can find it in the form’s embed code on the Forms
screen.
The subscriber’s email address.
The subscriber’s first name.
The subscriber’s last name.
The subscriber’s phone number when the saved form includes a phone field. It
is normalized onto the base subscriber profile without changing SMS consent.
Value for a custom field configured on the saved form. The
fieldKey is
stored as a subscriber custom attribute, for example
customAttributes[nickname]=Ace.JSON alternative for custom integrations. Saved forms only accept keys that
are configured as custom fields on the form.
Honeypot field. Leave it empty.
Generated saved-form HTML renders built-in name fields first, then email, then
configured custom fields before the submit button. Custom fields cannot
currently be interleaved with built-in fields.
Existing company-scoped saved form submission URLs continue to work.
Responses
Native HTML form posts that accepttext/html receive a hosted confirmation page that mirrors the form’s success screen (checkmark, heading, and message) instead of JSON. Forms configured to redirect respond with a 303 to the stored redirect URL.
Submit Saved Form