Skip to main content

Overview

The A/B Test Campaigns API lets you split a contact list into test groups, send different email variants to each group, and automatically deliver the winning version — determined by open rate or click rate — to the remaining contacts after the test period. Base URL: https://api.effilink.co
Endpoint: POST /v5/campaign/mail/sends_abtest
You can define up to 4 additional test versions (5 total including the main version). Each version can vary its subject line, content, or both.

Request Parameters

string
required
The name of the A/B test task. Maximum 200 bytes. Must be unique within your team.
string
required
The subject line for the main (control) version of the email.
string
required
The HTML body content for the main (control) version of the email.
string
required
The display name shown to recipients in the “From” field.
string
required
The verified sender email address. Must be an address already verified in your EffiLink account.
string
The reply-to email address. If omitted, replies go to senderMail.
string
Scheduled send time in ISO 8601 UTC format (e.g., 2025-06-01T10:00:00Z). Must not be more than 1 hour in the past or more than 30 days in the future. Omit to send immediately.
array[string]
required
An array of target contact list names. The combined total of contacts across all lists must be at least 10.
array[string]
An array of exclusion contact list names. Recipients on these lists will be excluded from the send.
array[object]
required
An array of test variant objects, defining 1 to 4 additional versions beyond the main version (5 total maximum). At least one version must be provided.
Each version must have at least one of subject or content set. A version with both fields empty is invalid.
integer
required
The duration of the A/B test in hours, after which the winning version is determined and sent to remaining contacts. Accepted range: 1–100.
integer
required
The percentage of the total contact list assigned to each individual test version. All test versions share the same percentage value, and the total allocation (percent × number of versions) must not exceed 100%. The remaining contacts receive the winning version after the test period.For example, with 2 versions (main + 1 variant) at percent: 20, each version reaches 20% of the list (40% total). The winning version is then sent to the remaining 60%.
string
The metric used to determine the winning version after the test period. Defaults to open.

Response

integer
HTTP-style status code. 200 on success.
string
A human-readable status message. Empty string on success.

Error Codes


How A/B Testing Works

  1. Divide — EffiLink splits your contact list into test groups. Each version (including the main) receives percent% of the total list.
  2. Test — All versions are sent simultaneously at sendDate. The test runs for timeLimit hours.
  3. Winner — After the test period, the version with the best abTestType metric (open rate or click rate) is declared the winner.
  4. Deliver — The winning version is sent automatically to all remaining contacts who did not receive a test version.
For statistically meaningful results, ensure your test group sizes are large enough. With percent: 10 and a list of 1,000 contacts, each variant receives only 100 recipients — consider using larger lists or higher percentages for low-volume tests.

Example Request

In this example:
  • Main version (subject: "Check out our latest products") → sent to 20% of the list.
  • Variant A (subject: "New arrivals you'll love this June") → sent to another 20%.
  • After 24 hours, the version with the higher open rate is sent to the remaining 60%.

Example Response