Emma

Emma's all-in-one marketing platform gives you the tools you need to send campaigns that really connect.

Power end-to-end data operations for your Emma API with Nexla. Our bi-directional Emma connector is purpose-built for Emma, 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 Emma or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Emma 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

Prerequisites

Before creating an Emma credential, you need to obtain an API Key Value and Account ID from your Emma account. Both values are required to authenticate with the Emma API.

To obtain your API Key Value and Account ID, you need to have an Emma account with API access enabled. Once you have access to your account, you can generate an API key and find your Account ID from your Emma account settings. The API Key Value is used to authenticate all API requests to the Emma API. The API Key Value is sent in the Authorization header for all API requests. The Account ID is used to construct the API base URL for your account. For detailed information about API key setup and authentication, refer to the Emma API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key Value	Yes	Yes
Account Id	Yes	No

Create a credential in Nexla

1. To create a new Emma credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Emma

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Emma API Key Value in the API Key Value field. This is the API key you obtained from your Emma account settings. The API Key Value is sent in the Authorization header for all API requests to the Emma API.

   Keep your API Key Value secure and do not share it publicly. The API Key Value provides access to your Emma account and should be treated as sensitive information. The API Key Value is sent in the Authorization header for all API requests to the Emma API. For detailed information about obtaining and managing API keys, see the Emma API documentation.

4. Enter your Emma Account ID in the Account Id field. This is the unique identifier for your Emma account, used to construct the API base URL for your account (e.g., https://api.e2ma.net/{account_id}).

   The Account ID is the unique identifier for your Emma account. The Account ID is used to construct the API base URL for your account, which is used in all API requests. You can find your Account ID in your Emma account settings. For detailed information about finding your Account ID, see the Emma API documentation.

5. Click the Save button at the bottom of the overlay. 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.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Emma connector tile, then select the credential that will be used to connect to the Emma instance, and click Next; or, create a new Emma credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Emma 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.

Searches

This endpoint retrieves a list of saved searches. Use this endpoint when you need to access saved search information, search lists, or search data from your Emma account.

• This endpoint automatically retrieves all saved searches from your Emma account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to {api_url}/searches where {api_url} is your Emma API base URL (e.g., https://api.e2ma.net/{account_id}) from the credential configuration. The endpoint URL is automatically constructed based on your Emma API base URL.
• The endpoint does not use pagination and returns all saved searches in a single request.
• The endpoint will return all saved searches. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.

This endpoint returns all saved searches for your Emma account. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about retrieving searches, see the Emma API documentation.

Campaigns

This endpoint gets SMS campaigns for the account. Use this endpoint when you need to access SMS campaign information, campaign lists, or campaign data from your Emma account.

• This endpoint automatically retrieves all SMS campaigns from your Emma account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to {api_url}/sms/campaigns where {api_url} is your Emma API base URL (e.g., https://api.e2ma.net/{account_id}) from the credential configuration. The endpoint URL is automatically constructed based on your Emma API base URL.
• The endpoint does not use pagination and returns all SMS campaigns in a single request.
• The endpoint will return all SMS campaigns for your account. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.

This endpoint returns all SMS campaigns for your Emma account. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about retrieving SMS campaigns, see the Emma API documentation.

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.

Manual configuration

Emma data sources can also be manually configured to ingest data from any valid Emma 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.

Emma API endpoints typically follow the pattern https://api.e2ma.net/{account_id}/{endpoint_path}, where {account_id} is your Account ID from the credential configuration. The endpoint requires API Key authentication via the Authorization header, which is handled automatically by 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 Emma 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.

Use as a destination

Click the + icon on the Nexset that will be sent to the Emma destination, and select the Send to Destination option from the menu. Select the Emma connector from the list of available destination connectors, then select the credential that will be used to connect to the Emma organization, and click Next; or, create a new Emma credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Emma 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.

Exports

This endpoint creates an export of members. Use this endpoint when you need to export member data from your Emma account from your data sources.

• This endpoint automatically creates member exports in your Emma account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses POST requests to {api_url}/exports where {api_url} is your Emma API base URL (e.g., https://api.e2ma.net/{account_id}) from the credential configuration. The endpoint URL is automatically constructed based on your Emma API base URL.
• The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the export configuration data. The request body should follow the Emma API specification for creating exports, including required fields and field names.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create an export. If you need to create multiple exports, you can send multiple records, but each will be processed as a separate request.

The request body must be properly formatted JSON that matches the Emma API specification for creating exports. The endpoint requires API Key authentication via the Authorization header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating exports, including required fields, field names, and request formats, see the Emma API documentation.

Fields

This endpoint creates a new field. Use this endpoint when you need to create custom fields in your Emma account from your data sources.

• This endpoint automatically creates fields in your Emma account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses POST requests to {api_url}/fields where {api_url} is your Emma API base URL (e.g., https://api.e2ma.net/{account_id}) from the credential configuration. The endpoint URL is automatically constructed based on your Emma API base URL.
• The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the field data to create. The request body should follow the Emma API specification for creating fields, including required fields and field names.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a field. If you need to create multiple fields, you can send multiple records, but each will be processed as a separate request.

The request body must be properly formatted JSON that matches the Emma API specification for creating fields. The endpoint requires API Key authentication via the Authorization header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating fields, including required fields, field names, and request formats, see the Emma API documentation.

Manual configuration

Emma destinations can also be manually configured to send data to any valid Emma 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.

Emma API endpoints typically follow the pattern https://api.e2ma.net/{account_id}/{endpoint_path} and primarily use POST requests with JSON request bodies. The Authorization and Content-Type: application/json headers are handled automatically by your credential configuration.

Save & activate

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 send the data to the configured Emma endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Emma endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.