Mailosaur
Mailosaur is an email and SMS testing platform used to validate transactional emails, SMS, and voice messages in development and QA environments. It provides virtual SMTP servers, message capture and search, and virtual security devices for one-time password (OTP) testing, all accessible through a REST API.
Power end-to-end data operations for your Mailosaur API with Nexla. Our bi-directional Mailosaur connector is purpose-built for Mailosaur, 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 Mailosaur or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Mailosaur workflows fast, secure, and fully governed.
Features
Type: API
- 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 Mailosaur credential, you need a Mailosaur account and an API key. Mailosaur authenticates API requests using HTTP Basic Auth, with your API key supplied as the credential value and requests sent to the base URL https://mailosaur.com/api.
To obtain your Mailosaur API key, follow these steps:
-
Sign in to your Mailosaur account at mailosaur.com.
-
Open the Mailosaur Dashboard and navigate to the API keys section under your account settings.
-
Create a new API key (or copy an existing one). Mailosaur supports both account-level and server-level API keys, so choose a key with access to the servers and messages you intend to work with in Nexla.
-
Copy the API key and store it securely. You will provide it when configuring your Nexla credential.
Mailosaur transmits the API key as the HTTP Basic Auth username value, and all API traffic must occur over HTTPS. Treat your API key as sensitive information, and revoke and regenerate it from the dashboard if it is ever exposed. For more details, see the Mailosaur API Reference.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| Username Or API Key | Yes | Yes | Your username or personal API Key |
| Password | Yes | Yes | Your password |
| Base URL | Yes | No | The base URL for the Mailosaur API. |
Create a credential in Nexla
-
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.
-
In the Username Or API Key field, enter your Mailosaur API key (or username). Mailosaur uses HTTP Basic Auth with the API key supplied as the username value.
-
In the Password field, enter your password. When authenticating with an API key, Mailosaur does not require a password, so this may be left as configured for your account's authentication method.
-
In the Base URL field, enter the base URL for the Mailosaur API. This defaults to
https://mailosaur.com/api. -
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.
Your API key grants access to your Mailosaur servers and captured messages and should be kept confidential. If your API key is compromised, revoke it in the Mailosaur Dashboard and generate a new one.
For detailed information about authentication and available endpoints, see the Mailosaur API Reference.
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 Mailosaur connector tile, then select the credential that will be used to connect to Mailosaur, and click Next; or, create a new Mailosaur 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 Mailosaur 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.
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
Mailosaur data sources can also be manually configured to ingest data from any valid Mailosaur 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 Mailosaur 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 Mailosaur destination, and select the Send to Destination option from the menu. Select the Mailosaur connector from the list of available destination connectors, then select the credential that will be used to connect to Mailosaur, and click Next; or, create a new Mailosaur 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 Mailosaur 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.
Manual configuration
Mailosaur destinations can also be manually configured to send data to any valid Mailosaur 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.
Mailosaur APIs expect JSON format for create, update, forward, and reply operations. For operations that target a specific resource, include the ID of the object (such as a message, server, or device) in the request 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 Mailosaur endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Mailosaur endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.