Vertical Response Integration

OAuth Connection to Vertical Response

Vertical Response uses an OAuth 2.0 authorisation-code flow rather than a static API key, so the connection setup redirects you from LeadSync to vrapi.verticalresponse.com/api/v1/oauth/authorize, you log in and approve the LeadSync app, and Vertical Response sends you back with a one-time code. LeadSync exchanges that code for a long-lived access token and stores it on the connection -- no API keys to copy and paste, no rotation chores.

Every subsequent API call to vrapi.verticalresponse.com/api/v1/ goes out as a Bearer token request. If the token is ever revoked from inside Vertical Response (for example, you remove the LeadSync app), new leads start failing with 401s and an error appears on your LeadSync Logs tab -- reconnect from the LeadSync settings screen and saved leads resume immediately.

List Selection and Custom Field Discovery

During setup, LeadSync calls GET /lists to enumerate every contact list on your Vertical Response account, so you can pick a destination list per lead source on a clean dropdown rather than typing in IDs. Each LeadSync connection is bound to one list -- if you want different ad campaigns to feed different lists, build one connection per list.

For field mapping, LeadSync calls GET /contacts/fields?type=all, which returns both Vertical Response's standard fields (email, first_name, last_name, etc.) and any custom contact fields you have created. Custom fields are flagged internally with a custom- ID prefix so the mapping logic knows to nest them correctly in the contact payload at send time.

Adding Contacts and Form Encoding

When a lead arrives, LeadSync POSTs to lists/{list_id}/contacts with the email plus every mapped field. Standard fields are sent at the top level of the body; custom fields are sent under a custom object keyed by the Vertical Response field IDs LeadSync stored at setup. The body uses application/x-www-form-urlencoded encoding -- a Vertical Response API quirk worth knowing if you compare to other email platforms which use JSON.

A repeat submission from the same email address updates the existing contact rather than creating a duplicate, so contact counts and segment membership stay accurate even if a lead fills your form twice. Email is the required identifier -- any lead missing the email mapping is skipped and logged.

Frequently Asked Questions

No. Vertical Response uses OAuth 2.0, so the connection wizard redirects you to vrapi.verticalresponse.com to log in and approve the LeadSync app. Once you approve, LeadSync stores the access token automatically and uses it on every API call.

On the connection setup screen, LeadSync loads every list on your Vertical Response account and shows them in a dropdown. Pick the list you want for this lead source. To send leads to multiple lists, create multiple connections (one per list) and assign different ad campaigns to each.

Yes. LeadSync loads your Vertical Response standard fields and every custom contact field you have created. They all appear on the field mapping screen so you can map any lead form question to any contact field in one place.

No. Vertical Response uses email as the unique identifier on a list, so a repeat submission updates the existing contact's field values rather than creating a duplicate row. Your list counts stay accurate.

Within seconds. LeadSync receives the lead webhook from your ad platform immediately, formats the API payload, and POSTs to Vertical Response. End-to-end is typically 2-5 seconds from form submission to contact appearing in your list.

New leads will fail with 401 Unauthorized errors and the failures are logged on your LeadSync Logs tab. Open the Vertical Response connection in LeadSync, click Reconnect to restart the OAuth flow, and saved leads resume immediately.

Yes. Build an autoresponder or scheduled campaign in Vertical Response that triggers on list addition or contact creation, then point your LeadSync connection at the same list. The automation fires for every new lead LeadSync writes.

Yes. Vertical Response requires email for every contact, so LeadSync skips any lead that arrives without the email field mapped from the form. The skip is logged on your LeadSync Logs tab so you can spot misconfigured forms quickly.

Available Integrations

How It Works

OAuth Connection to Vertical Response

List Selection and Custom Field Discovery

Adding Contacts and Form Encoding

Frequently Asked Questions

Start Syncing Leads to Vertical Response