Add sequencer

Connect a new sequencer account (Instantly, Smartlead, Lemlist, EmailBison, etc.) to your workspace. Pass the platform identifier, the credentials the platform requires (use the field names returned by List sequencer platforms), and any optional warmup or workflow settings. Once added, you can route mailboxes into this sequencer with the Export endpoint.

Lemlist note: when platform is lemlist, this endpoint runs Lemlist live login via browser automation (synchronous, typically 30 to 90 seconds). If Lemlist auto-trusts the IP, the Sequencer record is created immediately and the endpoint returns 201 (same as other platforms). If Lemlist gates the login with a magic-link / OTP confirmation page, the endpoint returns 202 with { status: 'verification_required', verification_id, sequencer_email }. The caller must then extract the confirmation URL plus the 6-digit code from Lemlist verification email and follow up with POST /v1/api/sequencers/lemlist/verify (re-send the same email + password).

Required fields vary by platform. The fields below cover the common case; the authoritative per-platform list comes from List sequencer platforms (GET /v1/api/sequencers/platforms), which returns each platform's exact field names and which are required. For example, masterinbox additionally requires workspace_id, while sendkit, brandjet, supersend, ken, automailer, mailstrike, and outboundry require only api_key (no sequencer_login/password).

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location 'https://api.inboxkit.com/v1/api/sequencers/add' \ --header 'X-Workspace-Id;' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "name": "My Instantly Account", "platform": "instantly", "sequencer_login": "[email protected]", "sequencer_password": "StrongPass@1", "sequencer_workspace": "instantly_workspace_name" }'

Request

Responses