Lasso API and Integrations

Lasso API and Integrations

In this article:

Need-to-Knows about Lasso API and Integrations

Lasso can be integrated with various external applications using the API (Application Programming Interface). The API allows systems to communicate with each other via webhooks that send information from one system to another. With an integration in place, leads submissions and updates to existing data within Lasso can be made from other applications.

There are two versions of Lasso's API - the included version that is provided at no cost (Lasso API) and the add-on version for which there is a monthly fee (Lasso Pro API). Access to the API is provided via API Key in the Project Admin Center:

  • Lasso API - The Lasso API key allows you to connect your registration page with Lasso and submit registrations.
  • Lasso Pro API - The Lasso Pro API key allows access to Lasso's pre-built integrations, and provides added features of appending data in Lasso and updating external applications.

To obtain the API Key, you will need to generate an API Integration Token. This can be done in the Project Admin Center, and is available only to users with a Project Admin role and the Integrations permission.


Specific Vendor Integrations:

Why Use the API?

What can be done using the Lasso API?

  • Submit leads to your Lasso database.

What can be done using the Lasso Pro API?

  • Submit leads to your Lasso database.
  • Retrieve leads from an external application.
  • Update leads with registrant contact information (name, email, phone, address) and sales details (rating, source, secondary source, questions/answers).
  • Record history or notes such as when a chat is recorded or a contract is signed.

What are the Advantages of the Lasso Pro API?

The Lasso API can be used to submit leads to Lasso. The Lasso Pro API offers expanded functionality including:

  • Connecting systems that come before Lasso in the selling process. Some examples of these systems may be your corporate or community websites or an existing internal database of leads. 
    • Manage duplicate records before they enter Lasso. Search for registrants, insert new records, update contact information, modify sales details, append notes, history, question answers for existing registrants.
    • Capture registrations in a multi-part process. Take in only a minimal set of information to create a new registrant and then add more as your prospects browse your website or make selections.
  • Connecting systems that come after Lasso in the selling process. Some examples of these may be contract processing, selections management, ERP or accounting systems.
    • Avoid manual duplicate entry. Pushing records from one system to another can be automated using the API.
    • Keep contact information in sync with Lasso. Contact information that is updated in Lasso can be provided to an external system via the webhook.
    • Update sales details and enter history items when they happen in an external system. This can be used to segment registrants in a custom list and hook into Lasso's sales process.

Set Up Integration with Lasso

Access API Integration Tokens

1 – On the Lasso Home Page, scroll to Project Admin and click More….

2 – Select API Integration Tokens.

Generate an API Token

3 – Click Generate New API Token.

4 – In the Generate Token for Project field, select the project.

5 – In the Vendor field, select the application.

6 – Please read the Notice below the Generate button. This is what you will be charged for the integration. If you have questions about the fee, please contact your Lasso Client Director.

7 – If you have read the Notice regarding the fee and are ready to move ahead, click Generate.

Note: Only one API token per project/vendor combination can be generated. This will be noted below the Generate button if you are attempting to generate an API token using an existing project/vendor combination.

Once you generate the API token, the project/vendor combination will be added to the list. Depending on the vendor, you may need to configure a webhook for the integration. You can filter the webhook by rating if using the Lasso Pro API webhook. Please see specific vendor integrations for instructions.

Developer Notes


Creating a Registrant

The following route can be used to create new registrants. Typically, this contains their name and contact information such as email and phone number. Additional information can be entered into the registrant's profile such as contact history, notes, or answers to specific questions.

POST /registrants

Some features to consider aside from the above are the ability to assign new registrants to sales reps and the ability to send emails to registrants when they’re created. To use these features, please see rotationId and thankYouEmailTemplateId in the Create a registrant documentation in the API Documentation.

Updating a Registrant

One of the most common cases when creating an integration is syncing contact information changes made externally with the CRM. To help accomplish this, we have two routes in the API which can be used together to update registrants' contact details. The Lasso Pro API is needed to update registrants.

Note: If you don’t know your registant's ID, please see below on using external IDs.

Start by getting the contact details with a call to:
GET /registrants/{registrantId}/person/contact-information

Retrieve all of a registrant's contact information.

Update the details as necessary and then call the following to overwrite the CRM's information:

PUT /registrants/{registrantId}/person/contact-information

Using External IDs

External IDs can be recorded for Lasso registrants on creation or by calling the following on an existing registrant:
POST /registrants/{registrantId}/integrations

An external ID can be used in the registrant search route to retrieve registrants. The registrant data that is returned will contain their registrant ID and project ID. The registrant ID is required for most API calls and the project ID can be used to select the correct API key for writing.

External IDs will also be passed as part of the information posted when a registered webhook is called. This will help you to determine which record has been updated.

Receiving Registrant Updates via Webhook

A webhook endpoint can be registered with Lasso. Registered URLs will be called when a qualifying event is triggered. The webhook endpoint will be POSTed to with a JSON payload. The payload will contain metadata about the request including the external ID of the registrant. A current copy of the registrant will be provided in the entity attribute. For more details on the payload or to see a list of qualifying events, see the event system documentation.

Developer Documentation

  • API Documentation - API routes, authorization, webhook and model definitions.
  • API Change Log - When changes, updates, or bug fixes are made, they will be posted to the changelog

Whitelist Lasso IP Addresses

To whitelist HTTP/HTTPS traffic that is originating from Lasso and communicating with the Lasso API, please use the following IP addresses:


Disable API Integration Token

Note: A token cannot be deleted, only disabled. This is a safety precaution, in case it needs to be enabled again at a future date.

1 – On the Lasso Home Page, scroll to Project Admin and click More….

2 – Select API Integration Tokens.

3 – Find the token you want to disable and click Disable Token.

4 – Click Confirm Disable.