Import / Export

Learn how to bulk import subscribers from files or API, and export your subscriber data for external use.

Importing Subscribers

Add subscribers to your newsletter in bulk using CSV files, individual entries, or through the API. On the Subscribers page, click Add subscribers and choose Import from a file (CSV/TXT), Add one subscriber or Add through the API. The Add subscribers page that opens asks "How do you want to add subscribers?" with three cards — Import a file, Add one subscriber and Use the API — and you can switch between them there.

Upload a CSV or TXT file to import multiple subscribers at once. The page walks you through five numbered steps: Upload your file, Check the columns, Add to groups (optional), Did these people agree to get your emails? and Review and import.

File Requirements:

  • Email column (required): a column whose header contains the word "email", for example email or E-mail address. Without one the page shows No email column found and the import can't start
  • Name columns (optional): any column whose header contains "name" — first and last names are joined into one full name
  • Custom fields: a column whose header is exactly the Merge tag of a custom field you've created. Any other column is skipped and shown as Not imported
  • Format: Comma-separated values, one subscriber per row, column names in the first row without extra spaces. Drop the file on the box that says Drop your CSV or TXT file here, or click it to choose one

Template Examples:

Basic Template
email*,name*,custom_field1,custom_field2
[email protected]*,John Doe*,Value1,Value2
[email protected]*,Jane Smith*,Value3,Value4
Advanced Template
email*,firstname*,lastname*,custom_field1,custom_field2
[email protected]*,John*,Doe*,Value1,Value2
[email protected]*,Jane*,Smith*,Value3,Value4

The examples mark the main columns with asterisks (*); only the email column is required. The system automatically recognizes and combines name-related columns (name, firstname, lastname) into a single full name field.

Upload your file: Download template gives you a ready-made file with the email and name columns plus the merge tag of each of your custom fields, and See example files shows the two examples above.

Check the columns: once a file is chosen, a table lists every column in it with two sample values and what it will be imported as — Email, Name, one of your custom fields, or Not imported — and sums up how many columns will be imported. If a column you want is skipped, rename its header to a field's merge tag, or create the field first (Open Fields takes you to the Fields view).

Import Options:

  • Add to groups (optional): Select existing groups; everyone in the file joins them
  • Did these people agree to get your emails?: Choose Yes, they signed up to add them straight away, with no confirmation email, or Ask them to confirm first to send a confirmation email so they join only once they click the link in it. With the second choice you also pick the Confirmation email to send; Edit confirmation emails opens your list of confirmation emails

Review and import: a summary shows the File, Rows found, Columns, Groups and Confirmation email. Click Import subscribers (with the number of rows in brackets) to start. When it finishes you see how many subscribers were imported, how many duplicates were left out, and a List cleaned message if addresses were skipped.

Free list cleaning. As it imports, Yaplet automatically drops rows it can already tell won't deliver — duplicate, invalid-format, disposable/temporary-domain, and system/role addresses (like no-reply@, postmaster@, or abuse@). Duplicates are skipped — the existing subscriber is left unchanged. You get a List cleaned summary with a per-reason breakdown, for example "Skipped 42 addresses that can't be delivered to: 30 invalid, 5 disposable, 7 system/no-reply." The same gate runs on the bulk-upsert API, which returns the skipped counts in its response.
Addresses already known to be dead. Yaplet keeps a record of addresses that have permanently bounced anywhere on the platform — mailboxes that no longer exist. If your file contains one, the subscriber is still added, but arrives already marked Bounced and is never emailed. The mail provider would refuse the message anyway, and the attempt would only cost you sending reputation. Only permanent bounces work this way — unsubscribes and spam complaints are decisions about one specific sender and never travel between accounts. Nothing is revealed to you about any other Yaplet account, or to them about yours.
A "no" stays a "no". Importing a contact that unsubscribed, bounced or complained doesn't subscribe it again — even if you deleted it first. Yaplet remembers which addresses in your account said no, so the re-imported contact arrives with its old status (unsubscribed, complaint or bounced) and isn't emailed. Only the person can subscribe again — see Confirmation Emails.
Yaplet can't confirm a real mailbox exists — only that an address is well-formed and not disposable. Importing an unconfirmed, purchased, or stale list causes bounces and spam complaints, and high rates will automatically pause your sending (see Email Deliverability). When a large share of a list is unusable, Yaplet flags it and suggests running the list through a verification service — such as ZeroBounce, Kickbox, or MillionVerifier — before you send. Only import lists you own and have permission to email.
Yaplet keeps the list clean after import, too: a background check removes contacts whose domain no longer accepts mail. After a file import, members with Newsletter access get one dashboard notification per import saying undeliverable addresses were removed. Contacts added through the API or a workflow are checked and removed the same way, but without a notification.
When you choose Ask them to confirm first, subscribers show as Not confirmed and won't receive any newsletter emails until they click the confirmation link in their email.
name
string
The subscriber's full name. Optional - if not provided, will use the email username portion.
verification_id
string
ID of one of your own confirmation emails (the ones under Subscribers → Confirmation emails) — any other ID fails the whole call with 400 "Unknown verification_id". A new or removed contact gets that confirmation email, and its state is set to "NEW". A contact that unsubscribed gets a new confirmation email at most once every 30 days and stays unsubscribed until the person confirms it. Contacts that bounced or complained never get one. Optional - if omitted, a new contact is marked as verified automatically.
state
string
Contact status. Valid values: "VERIFIED", "UNVERIFIED", "REMOVED". "VERIFIED" works only for a new or removed contact: it is saved as "NEW" and goes through Yaplet's usual background check, which verifies it (or first sends the confirmation email named in verification_id). Contacts that bounced or complained keep their state — their other fields still update. An unsubscribed contact can't be brought back with state, only by the person confirming a new confirmation email (see verification_id). Optional - defaults based on verification settings.
fields
object
Custom field data as key-value pairs. Values are merged with existing fields (not replaced). Field types are automatically converted (dates, numbers). For a number field, send null or "" to clear it; any other value that isn't a number is skipped, and the subscriber keeps their current value. Optional.
group_add
string[]
Array of group IDs to add the contact to. Groups must exist and belong to your organization. Optional.
group_remove
string[]
Array of group IDs to remove the contact from. Groups must exist and belong to your organization. Optional.

Code Example Explanation:

  • URL: https://yaplet.com/api/newsletter/contacts/bulk-upsert - The full API endpoint URL
  • Headers:
    • Content-Type: application/json - Required for JSON payload
    • Y-API-Key: your_api_key_here - Replace with your actual API key from the dashboard
  • Request Body: Contains a contacts array with subscriber objects
  • Replace placeholders:
    • your_api_key_here → Your actual API key
    • [email protected] → The subscriber's email
    • verification_variant_id → ID of one of your confirmation emails (if asking new subscribers to confirm)
    • group_id_1, group_id_2 → Actual group IDs from your organization
    • custom_field_1, custom_field_2 → Your custom field tag names
    • value_1, value_2 → The actual values for custom fields

API Notes:

  • Only the email field is required for each contact, everything else is optional
  • Without verification_id, new subscribers are set to verified status automatically — an unsubscribed contact sent again without one stays unsubscribed
  • With verification_id, new and removed contacts start in "NEW" state and move to "UNVERIFIED" once the confirmation email is sent, staying there until it is clicked
  • A contact that unsubscribed, bounced or complained is never switched back to subscribed or verified by the API — not even if you deleted it and send it again
  • The response lists the contacts with the state each one actually has after the call, so you can see which ones kept their state
  • Values from the fields object that are not included in the API call will not be updated/inserted
  • Group IDs that don't belong to your organization are ignored — the contact is still saved, it just isn't added to or removed from that group

Exporting Subscribers

Download your subscriber data as a CSV file for external use or backup.

Export Options

Export All

Location: Top-right Export menu → Export all subscribers
Scope: Downloads all subscribers in your organization, whatever filter is on
Use case: Complete subscriber backup or migration

Export Filtered

Location: Top-right Export menu → Export filtered subscribers (only shown while a filter, segment or group is applied) Scope: All subscribers matching current filters
Use case: Export subscribers from specific segments or groups

Export Selected

Location: Actions menu → Export CSV
Scope: Only selected subscribers from current view
Use case: Export filtered or manually selected subscribers

Export Behavior

Visible columns:

  • Only visible columns are included in the export
  • Use the Columns menu above the table to show/hide fields before exporting
  • Basic fields (Email, Name, Added At, State) and Engagement are visible by default
  • Engagement and the activity columns (Email provider, Last active, Last opened, Last clicked, Clicks, Emails received, Last emailed) can be included as export columns — the activity columns stay hidden until you switch them on in Columns. They're export-only, so they can't be used as import columns. A score or count of zero exports as 0, not an empty cell
  • Custom fields are hidden by default unless enabled

File Format:

  • Format: Comma-separated values (.csv)
  • Encoding: UTF-8
  • Headers: Column names in first row
  • Data: One subscriber per row
Before exporting, adjust your column visibility settings to include only the data fields you need in your CSV file.

Export Process

Choose Export Method

  • Click Export → Export all subscribers for the complete subscriber list
  • Or apply filters and choose Export → Export filtered subscribers
  • Or select subscribers, then use Actions → Export CSV

Configure Columns

Use the Columns menu to show/hide fields in the export

Confirm Export

Confirm the dialog that asks "Are you sure you want to export these subscribers?" — it reminds you that the file contains the currently visible columns

Download File

CSV file downloads automatically to your default download folder :::

Large exports (10,000+ subscribers) may take several minutes to process. You'll receive a notification when the export begins.

Bulk Operations and Export

When using Actions → Export CSV:

  • Select all: Exports all subscribers in current filtered view
  • Ticked subscribers: Exports only checked subscribers (up to 10,000)
  • Filtered Results: Export filtered subscribers applies the current Filter conditions to the export
Export filtered subscribers and Select all respect all active filters, segments, and group restrictions, so only the subscribers in your current view are included in the CSV. Export all subscribers ignores them and includes everyone.

© 2026 Yaplet. All rights reserved.