JavaScript SDK
The official Loops SDK for JavaScript, with full TypeScript support.
Installation
You can install the package from npm:
Minimum Node version required: 18.0.0.
You will need a Loops API key to use the package.
In your Loops account, go to the API Settings page and click Generate key.
Copy this key and save it in your application code (for example as LOOPS_API_KEY
in an .env
file).
Usage
Handling rate limits
If you import RateLimitExceededError
you can check for rate limit issues with your requests.
You can access details about the rate limits from the limit
and remaining
attributes.
Default contact properties
Each contact in Loops has a set of default properties. These will always be returned in API results.
id
email
firstName
lastName
source
subscribed
userGroup
userId
Custom contact properties
You can use custom contact properties in API calls. Please make sure to add custom properties in your Loops account before using them with the SDK.
Methods
- testApiKey()
- createContact()
- updateContact()
- findContact()
- deleteContact()
- createContactProperty()
- getContactProperties()
- getMailingLists()
- sendEvent()
- sendTransactionalEmail()
testApiKey()
Test that an API key is valid.
Parameters
None
Example
Response
Error handling is done through the APIError
class, which provides statusCode
and json
properties containing the API’s error response details. For implementation examples, see the Usage section.
createContact()
Create a new contact.
Parameters
Name | Type | Required | Notes |
---|---|---|---|
email | string | Yes | If a contact already exists with this email address, an error response will be returned. |
properties | object | No | An object containing default and any custom properties for your contact. Please add custom properties in your Loops account before using them with the SDK. Values can be of type string , number , null (to reset a value), boolean or date (see allowed date formats). |
mailingLists | object | No | An object of mailing list IDs and boolean subscription statuses. |
Examples
Response
Error handling is done through the APIError
class, which provides statusCode
and json
properties containing the API’s error response details. For implementation examples, see the Usage section.
updateContact()
Update a contact.
Note: To update a contact’s email address, the contact requires a userId
value. Then you can make a request with their userId
and an updated email address.
Parameters
Name | Type | Required | Notes |
---|---|---|---|
email | string | Yes | The email address of the contact to update. If there is no contact with this email address, a new contact will be created using the email and properties in this request. |
properties | object | No | An object containing default and any custom properties for your contact. Please add custom properties in your Loops account before using them with the SDK. Values can be of type string , number , null (to reset a value), boolean or date (see allowed date formats). |
mailingLists | object | No | An object of mailing list IDs and boolean subscription statuses. |
Example
Response
Error handling is done through the APIError
class, which provides statusCode
and json
properties containing the API’s error response details. For implementation examples, see the Usage section.
findContact()
Find a contact.
Parameters
You must use one parameter in the request.
Name | Type | Required | Notes |
---|---|---|---|
email | string | No | |
userId | string | No |
Examples
Response
This method will return a list containing a single contact object, which will include all default properties and any custom properties.
If no contact is found, an empty list will be returned.
deleteContact()
Delete a contact, either by email address or userId
.
Parameters
You must use one parameter in the request.
Name | Type | Required | Notes |
---|---|---|---|
email | string | No | |
userId | string | No |
Example
Response
Error handling is done through the APIError
class, which provides statusCode
and json
properties containing the API’s error response details. For implementation examples, see the Usage section.
createContactProperty()
Create a new contact property.
Parameters
Name | Type | Required | Notes |
---|---|---|---|
name | string | Yes | The name of the property. Should be in camelCase, like planName or favouriteColor . |
ttype | string | Yes | The property’s value type. Can be one of string , number , boolean or date . |
Examples
Response
Error handling is done through the APIError
class, which provides statusCode
and json
properties containing the API’s error response details. For implementation examples, see the Usage section.
getContactProperties()
Get a list of your account’s contact properties.
Parameters
You must use one parameter in the request.
Name | Type | Required | Notes |
---|---|---|---|
list | string | No | Use “custom” to retrieve only your account’s custom properties. |
Example
Response
This method will return a list of contact property objects containing key
, label
and type
attributes.
getMailingLists()
Get a list of your account’s mailing lists. Read more about mailing lists
Parameters
None
Example
Response
This method will return a list of mailing list objects containing id
, name
, description
and isPublic
attributes.
If your account has no mailing lists, an empty list will be returned.
sendEvent()
Send an event to trigger an email in Loops. Read more about events
Parameters
Name | Type | Required | Notes |
---|---|---|---|
email | string | No | The contact’s email address. Required if userId is not present. |
userId | string | No | The contact’s unique user ID. If you use userId without email , this value must have already been added to your contact in Loops. Required if email is not present. |
eventName | string | Yes | |
contactProperties | object | No | An object containing contact properties, which will be updated or added to the contact when the event is received. Please add custom properties in your Loops account before using them with the SDK. Values can be of type string , number , null (to reset a value), boolean or date (see allowed date formats). |
eventProperties | object | No | An object containing event properties, which will be made available in emails that are triggered by this event. Values can be of type string , number , boolean or date (see allowed date formats). |
mailingLists | object | No | An object of mailing list IDs and boolean subscription statuses. |
Examples
Response
Error handling is done through the APIError
class, which provides statusCode
and json
properties containing the API’s error response details. For implementation examples, see the Usage section.
sendTransactionalEmail()
Send a transactional email to a contact. Learn about sending transactional email
Parameters
Name | Type | Required | Notes |
---|---|---|---|
transactionalId | string | Yes | The ID of the transactional email to send. |
email | string | Yes | The email address of the recipient. |
addToAudience | boolean | No | If true , a contact will be created in your audience using the email value (if a matching contact doesn’t already exist). |
dataVariables | object | No | An object containing data as defined by the data variables added to the transactional email template. Values can be of type string or number . |
attachments | object[] | No | A list of attachments objects. Please note: Attachments need to be enabled on your account before using them with the API. Read more |
attachments[].filename | string | No | The name of the file, shown in email clients. |
attachments[].contentType | string | No | The MIME type of the file. |
attachments[].data | string | No | The base64-encoded content of the file. |
Examples
Response
Error handling is done through the APIError
class, which provides statusCode
and json
properties containing the API’s error response details. For implementation examples, see the Usage section.
Version history
v4.0.0
(Jan 16, 2024)- Added
APIError
to more easily understand API errors. See usage example. - Added support for two new contact property endpoints: List contact properties and Create contact property.
- Deprecated and removed the
getCustomFields()
method (you can now uselistContactProperties()
instead).
- Added
v3.4.1
(Dec 18, 2024) - Support for a newdescription
attribute ingetMailingLists()
.v3.4.0
(Oct 29, 2024) - Added rate limit handling withRateLimitExceededError
.v3.3.0
(Sep 9, 2024) - AddedtestApiKey()
method.v3.2.0
(Aug 23, 2024) - Added support for a newmailingLists
attribute infindContact()
.v3.1.1
(Aug 16, 2024) - Support for a newisPublic
attribute ingetMailingLists()
.v3.1.0
(Aug 12, 2024) - The SDK now acceptsnull
as a value for contact properties increateContact()
,updateContact()
andsendEvent()
, which allows you to reset/empty properties.v3.0.0
(Jul 2, 2024) -sendTransactionalEmail()
now accepts an object instead of separate parameters (breaking change).v2.2.0
(Jul 2, 2024) - Deprecated. Added newaddToAudience
option tosendTransactionalEmail()
.v2.1.1
(Jun 20, 2024) - Added support for mailing lists increateContact()
,updateContact()
andsendEvent()
.v2.1.0
(Jun 19, 2024) - Added support for new List mailing lists endpoint.v2.0.0
(Apr 19, 2024)- Added
userId
as a parameter tofindContact()
. This includes a breaking change for thefindContact()
parameters. userId
values must now be strings (could have also been numbers previously).
- Added
v1.0.1
(Apr 1, 2024) - Fixed types forsendEvent()
.v1.0.0
(Mar 28, 2024) - Fix for ESM types. Switched to named export.v0.4.0
(Mar 22, 2024) - Support for neweventProperties
insendEvent()
. This includes a breaking change for thesendEvent()
parameters.v0.3.0
(Feb 22, 2024) - Updated minimum Node version to 18.0.0.v0.2.1
(Feb 6, 2024) - Fix for ESM imports.v0.2.0
(Feb 1, 2024) - CommonJS support.v0.1.5
(Jan 25, 2024) -getCustomFields()
now returnstype
values for each contact property.v0.1.4
(Jan 25, 2024) - Added support foruserId
insendEvent()
request. Added missing error response type forsendEvent()
requests.v0.1.3
(Dec 8, 2023) - Added support for transactional attachments.v0.1.2
(Dec 6, 2023) - Improved transactional error types.v0.1.1
(Nov 1, 2023) - Initial release.
Contributing
Bug reports and pull requests are welcome at github.com/Loops-so/loops-js. Please read our Contributing Guidelines.
Was this page helpful?