Encharge is a behavior-based marketing automation platform for SaaS businesses and digital brands. Teams automate personalized customer journeys with a visual flow builder, advanced segmentation, and built-in email delivery, managing contacts, tags, segments, behavioral events, and custom fields via its API. It integrates with 250+ apps across email, SMS, and in-app messaging.
Power end-to-end data operations for your Encharge API with Nexla. Our bi-directional Encharge connector is purpose-built for Encharge, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Encharge or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Encharge workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
To connect Nexla to Encharge, you will need an active Encharge account and access to its API credentials. Encharge provides two types of API keys depending on the operations you want to perform:
REST API Key: Used for reading data from Encharge (e.g., listing people, accounts, segments, tags, fields, schemas, and custom objects) and for most write operations via the REST API.
Ingest API Write Key: Used specifically for writing behavioral event data via the Encharge Ingest API (e.g., the Track Event destination endpoint).
The Encharge REST API key authenticates requests to the core Encharge REST API at https://api.encharge.io. All data source operations and most destination operations use this key.
Navigate to Settings in the left-hand navigation menu.
Select API Tokens (or API Keys) from the Settings menu.
Your REST API key is displayed on this page. Copy the key value for use in Nexla.
For complete details on Encharge API authentication, refer to the Encharge API Documentation. The REST API key is passed as the X-Encharge-Token request header in all API calls.
The Encharge Ingest API write key is required only if you plan to use the Track Event destination endpoint. This key authenticates event-tracking writes to the Ingest API at https://ingest.encharge.io.
Navigate to Settings in the left-hand navigation menu.
Select API Tokens from the Settings menu.
Locate the Ingest API Write Key (sometimes labeled as the write key or site write key). Copy the key value for use in Nexla.
The Ingest API write key is a separate credential from the REST API key. It is scoped specifically to write operations on the Ingest API. For complete information on the Encharge Ingest API, refer to the Ingest API documentation.
Authenticate using your Encharge REST API key. Obtain your key from the Encharge dashboard under Settings > API Tokens. Used for source endpoints and REST-API sink endpoints.
Field
Required
Secret
Description
API Key Value
Yes
Yes
An encoded string value used as a secret token to authenticate API requests
Authenticate write operations to the Ingest API using a write-scoped API key. Required for event-tracking sinks. Obtain the write key from dashboard Settings > API Tokens.
Field
Required
Secret
Description
Ingest Write Key
Yes
Yes
Encharge Ingest API write key. Used to authenticate event-tracking and other Ingest-API sink calls.
To create a new Encharge credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Encharge supports two authentication methods in Nexla: API Key Authentication for REST API operations, and Ingest API Write Key Authentication for event-tracking destination operations. Select the method appropriate for your use case.
Encharge Authentication Methods
API Key Authentication
Ingest API Write Key Authentication
Authenticate using your Encharge REST API key. This method is used for all data source operations (reading people, accounts, segments, tags, fields, and custom objects) and for most destination operations (creating/updating people, managing tags, and creating custom objects). The API key is passed as the X-Encharge-Token header in all requests to the Encharge REST API.
Enter your Encharge REST API key in the **API Key Value** field. This key authenticates Nexla with the Encharge REST API and should be kept secure. You can obtain this key from **Settings > API Tokens** in your Encharge account.
Authenticate write operations to the Encharge Ingest API using a write-scoped API key. This method is required specifically for the Track Event destination endpoint, which sends behavioral events to Encharge via the Ingest API at https://ingest.encharge.io. Events submitted through this endpoint trigger automation flows and update contact scoring in Encharge.
Enter your Encharge Ingest API write key in the **Ingest Write Key** field. This key authenticates Nexla with the Encharge Ingest API for event-tracking operations. You can obtain this key from **Settings > API Tokens** in your Encharge account.
Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Encharge connector tile, then select the credential that will be used to connect to the Encharge instance, and click Next; or, create a new Encharge credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Encharge endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
List People
Returns a list of all people (contacts) in your Encharge account. Use this endpoint to export your full contact database for analysis, synchronization with other systems, or CRM workflows.
This endpoint retrieves all people records stored in your Encharge account. No additional parameters are required — select this endpoint and Nexla will fetch all available contacts.
Each returned record represents a single person and includes all attributes stored in Encharge, such as email address, name, tags, segment membership, and any custom fields defined in your account.
For complete information on the Encharge People API, refer to the Encharge API Reference.
List Accounts
Returns a list of all accounts in your Encharge system. Use this endpoint to retrieve company-level records for B2B workflows, CRM synchronization, or account-based marketing analysis.
This endpoint retrieves all account records from Encharge. No additional parameters are required — select this endpoint to fetch all available account data.
Each record represents a single account and includes account attributes such as the account name, domain, associated people, and any custom account fields configured in Encharge.
List Account Tags
Returns a list of all tags available for tag management in your Encharge account. Use this endpoint to audit your tag library, synchronize tags with external systems, or build tag-based reporting.
This endpoint retrieves all tags defined in your Encharge account. No additional parameters are required.
Tags in Encharge are labels applied to people records to categorize contacts, trigger automation flows, and drive segmentation. The returned data includes each tag name and associated metadata.
List Segments
Returns a list of all segments in your Encharge account. Use this endpoint to review your audience segments, monitor segment definitions, or integrate segment metadata with external analytics tools.
This endpoint retrieves all segment definitions from Encharge. No additional parameters are required.
Segments in Encharge are dynamic or static groupings of contacts based on behavior, attributes, or events. The returned records include segment names, IDs, and configuration details that can be used with other endpoints such as List Segment People.
Segment IDs returned by this endpoint can be used as input for the List Segment People and List Custom Objects in Segment endpoints.
List Fields
Returns a list of all custom fields defined in your Encharge account. Use this endpoint to audit your contact data model, build field mappings for integrations, or understand the structure of your people records.
This endpoint retrieves all custom field definitions from Encharge. No additional parameters are required.
Custom fields extend the default Encharge person record with additional attributes specific to your business — for example, plan type, trial start date, or company size. The returned data includes field names, types, and identifiers.
List Schemas
Returns a list of all data schemas (custom object types) available in your Encharge account. Use this endpoint to discover what custom object types are defined before using the List Custom Objects or Create Custom Object endpoints.
This endpoint retrieves all custom object schema definitions from Encharge. No additional parameters are required.
Custom object schemas define the structure of non-person data in Encharge — for example, companies, invoices, or subscriptions. The schema name returned here (e.g., company, invoice) is used as a required parameter in the List Custom Objects and List Custom Objects in Segment endpoints.
Use the object names returned by this endpoint as the Object Name parameter value when configuring the List Custom Objects or List Custom Objects in Segment endpoint templates.
List Segment People
Returns a list of all people (contacts) that belong to a specific Encharge segment. Use this endpoint to export audience subsets for targeted analysis, campaign reporting, or synchronization with downstream tools.
Enter the ID of the segment whose members you want to retrieve in the Segment ID field. This is a required parameter.
Segment IDs can be obtained by first running the List Segments endpoint, which returns a list of all segments in your account along with their IDs.
This endpoint supports paginated retrieval using offset-based pagination, automatically fetching all pages of results until the full segment membership list has been retrieved.
Large segments may return many records across multiple pages. Nexla handles pagination automatically — no additional configuration is required to retrieve all records.
Get Account Info
Returns information about the current Encharge account, including the total people count, account status, timezone, site URL, active services, and account ID. Use this endpoint to monitor account health or retrieve account metadata for reporting.
This endpoint retrieves account-level metadata for the authenticated Encharge account. No additional parameters are required.
The response is a single JSON object (not an array) containing account details. This makes it particularly useful as a quick health check or for populating account-level metadata in dashboards.
List Tag Counts
Returns all tags in your Encharge account along with the count of people tagged with each tag. Use this endpoint to analyze tag distribution, monitor audience size by tag, and generate tag-based engagement reports.
This endpoint retrieves all tags and their associated people counts from Encharge. No additional parameters are required.
Each record in the response includes a tag name and a count of how many contacts currently carry that tag, making this endpoint ideal for building dashboards that track audience segmentation and tag usage over time.
List Email Domains
Returns all email sending domains configured for your Encharge account, including their verification status. Use this endpoint to monitor domain configuration, audit sending infrastructure, or verify that domains are properly authenticated for email delivery.
This endpoint retrieves all email domains registered in your Encharge account settings. No additional parameters are required.
The response includes each domain name and its verification status (e.g., verified or pending). Domains must be verified in Encharge before they can be used for email sending.
List Custom Objects
Returns a list of custom object records (such as companies or invoices) for a given object schema in Encharge. Use this endpoint to export structured business data associated with your contacts for analysis or downstream integration.
Enter the name of the custom object schema whose records you want to retrieve in the Object Name field. This is a required parameter. The object name must match an existing schema in your Encharge account (e.g., company, invoice).
Available schema names can be discovered by first running the List Schemas endpoint.
This endpoint supports paginated retrieval using offset-based pagination with a default page size of 100 records per request. Nexla handles pagination automatically to retrieve all available records.
Custom objects in Encharge allow you to store non-person data (such as company records, subscription details, or invoices) and associate them with people and segments. The object schema name is case-sensitive and must exactly match the schema name as defined in Encharge.
List Custom Objects in Segment
Returns custom object records (such as companies) that belong to a specific Encharge segment. Use this endpoint to retrieve structured business data filtered by segment membership for targeted analysis or reporting.
Enter the name of the custom object schema in the Object Name field. This is a required parameter. The object name must match an existing schema in your Encharge account (e.g., company, invoice).
Available schema names can be discovered by first running the List Schemas endpoint.
Enter the ID of the segment to filter custom objects by in the Segment ID field. This is a required parameter.
Segment IDs can be obtained by first running the List Segments endpoint.
This endpoint supports paginated retrieval with a default page size of 100 records. Nexla handles pagination automatically.
List Email Template Versions
Returns the version history of a specific email template in Encharge. Use this endpoint to track template changes over time, audit content revisions, or export version data for compliance and governance workflows.
Enter the ID of the email template whose version history you want to retrieve in the Email Template ID field. This is a required parameter.
The endpoint returns each saved version of the specified email template, including version content and metadata. It supports paginated retrieval with a default page size of 50 records per request.
Email template IDs can be found in the Encharge dashboard under your email templates, or through the Encharge API. Refer to the Encharge API Reference for additional details on email template management.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Encharge data sources can also be manually configured to ingest data from any valid Encharge API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Encharge REST API endpoints follow the base URL pattern https://api.encharge.io/v1/. Path to Data varies by endpoint — for example, $.data[*] for people, $.segments[*] for segments, $.tags[*] for tags, $.tagCounts[*] for tag counts, $.objects[*] for custom objects and schemas, and $.items[*] for fields. You do not need to include the X-Encharge-Token authentication header — this is handled automatically by Nexla based on your credential configuration.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Encharge data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Encharge destination, and select the Send to Destination option from the menu. Select the Encharge connector from the list of available destination connectors, then select the credential that will be used to connect to the Encharge organization, and click Next; or, create a new Encharge credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Encharge endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create or Update Person
Creates or updates a person (contact) record in Encharge. Records are upserted based on the id, userId, or email field in the incoming data — if a matching person is found, their record is updated; otherwise, a new person is created. Use this endpoint to synchronize contact data from external systems into Encharge.
Ensure that each record in the Nexset includes at least one of the following identifier fields: email, userId, or id. These fields are used by Encharge to match incoming records to existing contacts. If none of these identifiers are present, Encharge will create a new person record for the incoming data.
The full incoming record body is sent as the person payload to Encharge. Any fields in the Nexset that correspond to standard or custom Encharge person attributes will be mapped and saved automatically.
This endpoint sends one record per API call (batch mode is disabled). For high-volume data loads, consider using the manual configuration with record batching enabled.
Adds one or more tags to an existing person in Encharge. Tags are used in Encharge to categorize contacts, trigger automation flows, and build audience segments. Use this endpoint to apply tags from external systems or workflow outputs to Encharge contacts.
Ensure that each record in the Nexset includes the following required fields:
tag: The name of the tag (or a comma-separated list of tag names for multiple tags) to add to the person.
At least one person identifier: email, userId, or id. Encharge uses this identifier to locate the person to whom the tag(s) will be added.
To add multiple tags to a single person in one call, include all tag names as a comma-separated value in the tag field (e.g., paid-customer,onboarded,active).
This endpoint sends one record per API call. The tag is added to the person's existing tag list — any tags already assigned to the person are preserved.
Removes one or more tags from an existing person in Encharge. Use this endpoint to programmatically clean up tags, update contact classification, or respond to downstream events that should modify a contact's tag assignments.
Ensure that each record in the Nexset includes the following required fields:
tag: The name of the tag (or a comma-separated list of tag names for multiple tags) to remove from the person.
At least one person identifier: email, userId, or id. Encharge uses this identifier to locate the person from whom the tag(s) will be removed.
To remove multiple tags from a single person in one call, include all tag names as a comma-separated value in the tag field.
This endpoint sends one record per API call (DELETE method). Only the specified tags are removed — all other tags on the person's record are preserved.
Creates a custom object record (such as a company, invoice, or other structured entity) under a specified object schema in Encharge. Use this endpoint to populate Encharge with structured business data from external systems for use in segmentation, personalization, and automation workflows.
Enter the name of the custom object schema to write into in the Object Name field. This is a required parameter. The object name must exactly match an existing schema defined in your Encharge account (e.g., company, invoice).
Available object schema names can be found in your Encharge account by using the List Schemas source endpoint, or by navigating to the custom objects section of the Encharge dashboard.
The object name is case-sensitive and must match the schema name exactly as it was defined in Encharge.
The full incoming record body is sent as the custom object payload to Encharge. Ensure that the Nexset fields match the attributes defined in the target object schema.
Tracks a behavioral event for a person via the Encharge Ingest API. Events submitted through this endpoint trigger automation flows, update contact scoring, and enable event-based segmentation in Encharge. Use this endpoint to send product usage events, purchase events, or custom behavioral signals from external systems into Encharge.
This endpoint requires the Ingest API Write Key Authentication credential type. The Track Event endpoint sends data to a separate Encharge Ingest API (https://ingest.encharge.io/v1) rather than the standard REST API, and uses a different authentication key. Ensure you have created an Ingest API Write Key credential before configuring this destination.
Structure each record in the Nexset to include the required Encharge Ingest API event fields:
name: The name of the event to track (e.g., Signed Up, Upgraded Plan, Feature Used). Use identify as the event name to create or update a person record rather than track a behavioral event.
userId or email: An identifier for the person associated with the event.
Additional event properties (such as plan name, feature ID, or purchase amount) can be included as additional fields in the record and will be passed through to Encharge as event properties, where they can be used in automation triggers and segmentation rules.
Events tracked via this endpoint will trigger any Encharge automation flows that use the corresponding event as a trigger. For complete information on the Encharge Ingest API, refer to the Encharge Ingest API documentation.
Encharge destinations can also be manually configured to send data to any valid Encharge API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Encharge APIs accept data in JSON format (application/json). Encharge REST API endpoints follow the base URL pattern https://api.encharge.io/v1/, while the Track Event endpoint uses the separate Ingest API at https://ingest.encharge.io/v1 with its own Ingest API Write Key credential. For update/upsert operations, include the ID of the object to be updated at the end of the URL. You do not need to include the X-Encharge-Token authentication header — this is handled automatically by Nexla based on your configured credential.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to Encharge, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Encharge until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
