Navigation
SuperSend

Changelog

A complete history of API changes, new features, and deprecations.


Stay up to date with the latest changes to the SuperSend API. We follow semantic versioning and announce breaking changes in advance.

ℹ️

Subscribe to Updates

Get notified of API changes by watching our GitHub changelog or subscribing to our developer newsletter.

March 2026

March 26, 2026 - Sender reply forwarding rules (forward_rules)

Senders now support per-destination reply forwarding with optional Super Inbox label filters, in addition to the existing forward_to field.

Affected endpoints:

  • GET /v2/senders — list items may include forward_rules

  • GET /v2/senders/:id — response includes forward_rules

  • PATCH /v2/senders/:id — request body may include forward_rules (array or null) and forward_to

    • Behavior:

  • If forward_rules is null or empty, behavior matches legacy: replies forward using forward_to when it is set.

  • If forward_rules is a non-empty array, each rule is applied independently. Rules with label_ids: null forward all replies to that rule's emails. Rules with one or more label UUIDs forward only when the conversation has a matching label.

    • See Senders in the API reference (OpenAPI Sender and UpdateSenderRequest schemas) for field shapes.

    March 24, 2026 - Team notification email with per-category preferences

    PATCH /teams/:id now accepts two new fields:

  • notification_email (string, email, nullable) — When set, team-scoped email notifications are also delivered to this address in addition to the individual user's email. Set to null or "" to remove.

  • notification_email_preferences (object, nullable) — Per-category toggles controlling which notification types are sent to the team notification email. Keys: errorNotificationsEmail, successNotificationsEmail, warmingNotificationsEmail, newInboxActivityNotificationsEmail, linkedinInboxActivityNotificationsEmail, outOfContactsNotificationsEmail. All default to true. Only provided keys are updated (merge).

    • GET /teams/:id and GET /teams responses now include both fields.

    Documentation: Teams (see API changelog)

    March 23, 2026 - Sender provider values aligned with connect flow

    POST /sender (V1) accepts the same provider values the app uses for preset mailboxes and email APIs (e.g. zoho, namecheap, mailgun, aws, azure), so connect no longer fails Joi validation for those options.

    GET /senders — provider query filter accepts the expanded set (including ss-private-smtp, sendgrid, mailreef, infraforge, and the preset providers above). OpenAPI Sender.provider and list-filter docs are updated.

    Documentation: Senders (see API changelog)

    March 23, 2026 - Email validation now includes intelligence data

    POST /email-validation/verify response now bundles email intelligence fields alongside the SMTP deliverability result—risk score, confidence level, provider detection, bounce/reply history, and flag signals (role-based, free provider, disposable). No additional credit is charged; one verification credit unlocks both data sets, matching the in-app experience.

    Documentation: Email validation API

    Use cases: Clay columns, Make/Zapier, enrichment pipelines, internal scripts.

    March 19, 2026 - Mailbox purchase: recipient name required

    POST /mailboxes/purchase (and related purchase flows) now require first and last name for the mailbox recipient. Applies to quotes and checkout aligned with registrar requirements.

    Documentation: Managed Mailboxes

    March 18, 2026 - Campaign V2 documentation and OpenAPI alignment

    Campaign endpoints, request/response examples, and schemas in api/openapi.yaml were updated for consistency with live V2 behavior. See Campaigns.

    March 17, 2026 - Announcements (unauthenticated)

    GET /announcements returns active in-app announcements (manual and status-driven). Intended for the app shell; does not require authentication.

    March 14–16, 2026 - Optional email verification on contact create (validate_emails)

  • POST /contacts and POST /contacts/bulk accept optional validate_emails. When true, contacts are queued for verification (consumes email verification credits).

  • Default is false so imports and API creates do not incur surprise billing.

    • Documentation: Contacts

    March 12, 2026 - Campaign daily send ceiling (max_per_day)

    Campaigns support max_per_day: an optional maximum number of emails sent per day from all senders in the campaign. null means no campaign-level cap (sender limits still apply).

    Documentation: Campaigns

    March 10, 2026 - Team usage and org billing views

  • GET /teams/{id}/usage — usage for a single team (domains, mailboxes, senders, and related counts where applicable).

  • GET /billing/team-usage — organization-level usage across teams for cost allocation.

    • March 6, 2026 - Placement tests (V2 OpenAPI parity)

    Placement test endpoints are documented in the OpenAPI spec with V2 response patterns. See Placement Tests.

    March 3, 2026 - List Health: selector and API alignment

    List Health behavior and docs were aligned with V2 (including selector updates so teams do not pick unusable states). See Campaigns.

    March 2, 2026 - Contact status: customer

    Contact interest / status filters include customer for contacts marked as customers. See Contacts.

    February 2026

    February 28, 2026 - Campaign categories and create-campaign parity

    Campaign categories (folders) APIs and docs were finalized. Creating a campaign via V2 now ensures ContactConfig is created in line with V1 behavior.

    Documentation: Campaign Categories, Campaigns

    February 25, 2026 - Intelligence composite endpoints

    Aggregate Intelligence endpoints were added for capacity, deliverability, sender health, outbound summary, and domain health (supporting MCP tools and internal automation). See the Intelligence tag in api/openapi.yaml and MCP Server.

    February 24, 2026 - Conversations API (V2)

    Conversation endpoints for the unified inbox (email, LinkedIn, Twitter), including messages and participant metadata.

    Paths: GET/POST /conversations, GET /conversations/{id}, GET/POST /conversations/{id}/messages

    Documentation: Conversations

    February 23, 2026 - Managed domains and mailboxes (purchase)

  • POST /domains/purchase — purchase a managed domain.

  • POST /domains/purchase-with-mailboxes — purchase a domain bundled with mailboxes.

  • POST /mailboxes/purchase — purchase mailboxes on an existing domain.

    • Documentation: Managed Domains, Managed Mailboxes

    February 17, 2026 - Team settings: inbox_super_views

    GET and PATCH /teams/{id} include inbox_super_views for team-level inbox display settings (V2 parity).

    Documentation: Teams

    January 2026

    January 28, 2026 - Campaign Contact Lifecycle Metrics

    Added contact_metrics to V2 campaign endpoints for tracking contact lifecycle status.

    Affected Endpoints:

  • GET /v2/campaigns - List campaigns now includes contact_metrics for each campaign

  • GET /v2/campaigns/:id - Get campaign now includes contact_metrics

    • New Fields:

    json
    {
      "contact_metrics": {
        "total": 150,
        "not_started": 50,
        "in_progress": 75,
        "finished": 20,
        "paused": 5
      }
    }

    Use Cases:

  • Auto-refill integrations: Use not_started to know how many contacts are queued

  • Campaign progress tracking: Monitor in_progress vs finished ratios

  • Capacity planning: Track paused contacts awaiting action

    • January 27, 2026 - V2 Bulk Contacts Endpoint

    Added POST /v2/contacts/bulk for bulk importing contacts with V2 standardized responses.

    Features:

  • JSON array or CSV file upload support

  • Up to 50,000 contacts per request

  • Asynchronous processing with upload tracking

  • Proper V2 error codes and response format

    • bash
    curl -X POST 'https://api.supersend.io/v2/contacts/bulk' \
      -H "Authorization: Bearer YOUR_API_KEY" \
      -H "Content-Type: application/json" \
      -d 700 dark:text-green-400">'{"contacts": [...], "TeamId": "...", "CampaignId": "..."}'

    January 19, 2026 - V2 API General Availability

    The V2 API is now generally available! This release brings significant improvements to consistency, error handling, and developer experience.

    New Features:

  • Consistent response format across all endpoints

  • Improved pagination with has_more field

  • Better error codes with documentation links

  • Team usage analytics endpoint

  • Sender profile management

    • Breaking Changes from V1:

  • Response structure changed (see Migration Guide)

  • Some field names updated for consistency

  • Authentication header format standardized

    • json
    // V2 Response Format
    {
      "success": true,
      "data": { ... },
      "request_id": "req_abc123"
    }

    December 2025

    December 12, 2025 - Email Analytics

  • New email.clicked event includes link URL

    • November 2025

    November 28, 2025 - Campaign Improvements

  • Added A/B testing for email subjects

  • Added scheduling options for campaigns

    • November 15, 2025 - Sender Profiles

  • Introduced sender profile management

  • DKIM and SPF verification status

    • November 8, 2025 - Security Updates

  • Added webhook signature verification

    • October 2025

    October 25, 2025 - V2 API Beta

    The V2 API entered public beta with the following endpoints:

  • POST /v2/contacts

  • GET /v2/contacts

  • GET /v2/contacts/{id}

  • PATCH /v2/contacts/{id}

  • DELETE /v2/contacts/{id}

    • October 18, 2025 - Bulk Operations

  • Added bulk contact import endpoint

  • Support for CSV and JSON formats

  • Background processing for large imports

    • October 10, 2025 - Error Handling

  • Standardized error response format

  • Added error codes for all failure scenarios

  • Added docs_url field linking to relevant documentation

    • API Versioning Policy

    Supported Versions

    VersionStatusSunset Date
    V2Current-
    V1DeprecatedDecember 31, 2026


    Breaking Changes

    We consider the following to be breaking changes:

  • Removing an endpoint or HTTP method

  • Removing or renaming a response field

  • Changing the type of a response field

  • Adding a new required request parameter

  • Changing authentication requirements

    • Non-Breaking Changes

    The following are considered non-breaking and may be made without notice:

  • Adding new optional request parameters

  • Adding new response fields

  • Adding new endpoints

  • Adding new event types

  • Fixing bugs

    • Deprecation Notices

    V1 API Deprecation

    The V1 API is deprecated and will be sunset on December 31, 2026. Please migrate to V2 before this date.

    Timeline:

  • October 2025: V2 beta released

  • January 2026: V2 GA, V1 deprecation notice

  • July 2026: V1 read-only mode

  • December 31, 2026: V1 sunset

    • See the V1 to V2 Migration Guide for detailed migration instructions.

    Need Help?

  • Check our Migration Guide for upgrading from V1

  • Contact support at support@supersend.io