SuperSend news and product updates

SuperSend lifted the June 2026 cutoff that kept LinkedIn away from organizations created after that date, so LinkedIn is available to every organization again, new signups included. The change follows the move of LinkedIn onto a new connection provider, and V2 identities, the V1 LinkedIn inbox and connect routes, and linkedin_url on contacts now work for every organization. Admins can still turn LinkedIn on or off per organization or user.

New SuperSend customers can run email and LinkedIn in one sequence again. LinkedIn access now runs through a different connection provider than before the June cutoff.

SuperSend added three V2 API endpoints built for AI agents. GET /v2/setup lists what an account still needs before it can send, with ordered next steps marked for the agent or the human, POST /v2/setup/inbox-checkout plans domains and inboxes and returns a checkout link for a person to pay, and GET /v2/campaigns/{id}/review returns a prelaunch review with a can_launch flag.

An AI agent can now take a SuperSend account from setup to launch, while payment and the final launch check stay with a person.

SuperSend now allows a contact to be active in a campaign only once, across every path that adds, restores or moves contacts. Bulk unarchive and transfer skip people already active in the target campaign and report restored and skipped counts, restoring or moving via PUT /v1/contact/:id returns 409 contact_already_exists, and CSV, Apollo, HubSpot and LinkedIn post interaction imports now match existing contacts case insensitively. Existing duplicates were cleaned up, keeping the enrollment that is stopped or furthest along.

Duplicate enrollments mean the same prospect can receive a sequence twice, which drives complaints and hurts sender reputation at high volume. Teams importing from several sources (Apollo, HubSpot, CSV) get this protection without writing their own dedup logic.