Smaily

Smaily is an email marketing and automation platform for building subscriber lists, sending campaigns and transactional messages, and running automation workflows. Its HTTP API exposes organizations, segments, subscribers, campaigns, templates, automations, and A/B tests. Nexla connects to the Smaily API to ingest this data and to push subscriber and campaign operations back into your Smaily account.

Power end-to-end data operations for your Smaily API with Nexla. Our bi-directional Smaily connector is purpose-built for Smaily, 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 Smaily or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Smaily 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 a Smaily credential, you need an API user (username and password) and your account subdomain. The Smaily API uses HTTP Basic authentication, and the base URL is derived from your account subdomain in the form https://SUBDOMAIN.sendsmaily.net/api.

To create an API user in Smaily, follow these steps:

1. Sign in to your Smaily account.

2. Click your account name in the upper-right corner of the page, and choose Preferences from the dropdown menu.

3. Click the Integrations tab.

4. Under API Passwords, click Create a new user.

5. Smaily generates your account subdomain, an API username, and an API password. Copy the API password immediately — it is shown only once. If you lose it, create a new API user to obtain a new password.

6. Construct your base URL from the subdomain shown, in the form https://SUBDOMAIN.sendsmaily.net/api (for example, if your subdomain is example, the base URL is https://example.sendsmaily.net/api).

For more details, see the Smaily API documentation and the Create an API user guide.

Authenticate

Credentials required

Field	Required	Secret	Description
Username	Yes	No	API username generated in Smaily Preferences > Integrations.
Password	Yes	Yes	API password generated alongside the username in Smaily.
Base URL	Yes	No	API base URL.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

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 Smaily API username in the Username field. This is the API username generated under Preferences > Integrations in Smaily.

4. Enter your Smaily API password in the Password field. This is the API password generated alongside the username, and it is treated as sensitive information.

5. Enter your Smaily API base URL in the Base URL field, in the form https://SUBDOMAIN.sendsmaily.net/api, where SUBDOMAIN is your account subdomain.

   The Smaily API uses HTTP Basic authentication with the API username and password. If your API password is compromised, create a new API user in Smaily to rotate the credentials.

   For detailed information about authentication, base URLs, and available endpoints, see the Smaily API documentation.

6. 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.

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 Smaily connector tile, then select the credential that will be used to connect to Smaily, and click Next; or, create a new Smaily 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 Smaily 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.

[Rest API] List Users

Retrieve the list of users belonging to an organization.

For detailed information about this endpoint and its response fields, see the Smaily API documentation.

[Rest API] List Segments

Retrieve all segments (lists), sorted alphabetically by name.

For detailed information about this endpoint and its response fields, see the Smaily API documentation.

[Rest API] List Campaigns

Retrieve campaigns, with optional filters by status and tags.

For detailed information about this endpoint and its response fields, see the Smaily API documentation.

[Rest API] List Templates

Retrieve email templates.

For detailed information about this endpoint and its response fields, see the Smaily API documentation.

[Rest API] List Automations

Retrieve automation workflows, with optional status filter.

For detailed information about this endpoint and its response fields, see the Smaily API documentation.

[Rest API] List Subscribers Of Segment

Retrieve subscribers belonging to a given segment.

• Provide the Segment ID whose subscribers should be listed. This parameter is required for this endpoint.

For detailed information about this endpoint and its response fields, see the Smaily API documentation.

[Rest API] Subscriber Action Log

Retrieve subscriber action/activity log entries from the last 30 days.

For detailed information about this endpoint and its response fields, see the Smaily API documentation.

[Rest API] List A/B Tests

Retrieve A/B tests, with optional filters by status and tags.

For detailed information about this endpoint and its response fields, see the Smaily 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

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

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 Smaily 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 Smaily destination, and select the Send to Destination option from the menu. Select the Smaily connector from the list of available destination connectors, then select the credential that will be used to connect to Smaily, and click Next; or, create a new Smaily 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 Smaily 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.

[Rest API] Create or Update Subscribers

Create or update one or more subscribers. Supports bulk operations.

Records from your Nexset are sent as JSON in the request body. For detailed information about the request body format and available fields, see the Smaily API documentation.

[Rest API] Unsubscribe Contact

Unsubscribe a campaign recipient; reflected in campaign statistics.

Records from your Nexset are sent as JSON in the request body. For detailed information about the request body format and available fields, see the Smaily API documentation.

[Rest API] Delete Subscriber

Permanently forget one or more subscribers, purging their data and statistics.

This operation is irreversible and permanently removes subscriber data. Records from your Nexset are sent as JSON in the request body. For detailed information about the request body format and available fields, see the Smaily API documentation.

[Rest API] Launch Campaign

Create and/or launch an email campaign.

Records from your Nexset are sent as JSON in the request body. For detailed information about the request body format and available fields, see the Smaily API documentation.

[Rest API] Send Message

Send a transactional message via an automation workflow.

Records from your Nexset are sent as JSON in the request body. For detailed information about the request body format and available fields, see the Smaily API documentation.

Manual configuration

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

Smaily APIs expect JSON format for these operations. Ensure that each record matches the request body structure expected by the target Smaily endpoint.

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 Smaily endpoint, open the destination resource menu, and select Activate.

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