Sequencers

A sequencer is a connection to a cold-email sending tool (Lemlist, Instantly, Smartlead, Apollo, and others — see /platforms). This is the API a platform like Infrabox uses to let a customer bulk-connect mailboxes they’ve provisioned into their own sending tool in one call, instead of copying SMTP/IMAP credentials into that tool by hand, mailbox by mailbox.

Are you building the other direction — a sequencer platform that wants to let its own users pull mailboxes out of Infrabox (an “Import from Infrabox” button)? See Building an “Import from Infrabox” Feature instead.

Method	Path	Description
`GET`	`/v1/api/sequencers/platforms`	List supported sequencer platforms
`POST`	`/v1/api/sequencers/list`	List sequencer connections in the workspace
`POST`	`/v1/api/sequencers/add`	Add a sequencer connection (credentials)
`POST`	`/v1/api/sequencers/update`	Update a sequencer connection
`POST`	`/v1/api/sequencers/delete`	Delete sequencer connection(s)
`POST`	`/v1/api/sequencers/export`	Bulk-connect mailboxes to sequencer(s)
`POST`	`/v1/api/sequencers/export/status`	Check export status per mailbox
`POST`	`/v1/api/sequencers/get-sequencers-tags`	List tags available on a platform (needs the platform’s own API key)
`POST`	`/v1/api/sequencers/lemlist/verify`	Complete a Lemlist connection paused for email OTP

List supported platforms


curl https://api.infrabox.software/v1/api/sequencers/platforms \
  -H "Authorization: Bearer YOUR_API_KEY"

Returns each platform’s identifier (e.g. "lemlist"), display name, and the credential fields it needs for /add (some platforms need only an API key; others need a username/password, or both).

Add a sequencer connection


curl -X POST https://api.infrabox.software/v1/api/sequencers/add \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "X-Workspace-Id: YOUR_WORKSPACE_UID" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Q1 Outbound",
    "platform": "lemlist",
    "username": "[email protected]",
    "password": "your-platform-password",
    "api_key": "sk_your_platform_api_key",
    "auto_export_enabled": true
  }'

api_key (the sequencer platform’s key, not your Infrabox key) unlocks tags, enable_warmup, and auto_reconnect_mailboxes — omit it and those fields are simply ignored.
auto_export_enabled: true makes newly created/bought mailboxes in this workspace automatically flow into this sequencer going forward, without a further /export call.
Some platforms (Lemlist) may respond 202 with a verification_required payload instead of 201 — the platform emailed a one-time confirmation link + OTP to the account you’re connecting. Extract both and complete the connection with POST /v1/api/sequencers/lemlist/verify (the verification_id from the 202 response expires after 30 minutes).

Bulk-connect mailboxes

This is the bulk-import call: pass the mailboxes you want connected and the sequencer(s) to connect them to. sequencer_uids takes an array — pass more than one to connect the same batch of mailboxes to several sequencers in one call (one export job is created per sequencer × mailbox pair). Fetch sequencer UIDs from GET /v1/api/sequencers/list first — there’s no platform-name filter here.


curl -X POST https://api.infrabox.software/v1/api/sequencers/export \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "X-Workspace-Id: YOUR_WORKSPACE_UID" \
  -H "Content-Type: application/json" \
  -d '{
    "sequencer_uids": ["seq_123456789"],
    "mailbox_uids": ["mb_111", "mb_222", "mb_333"]
  }'

Response:


{
  "error": false,
  "message": "Successfully created 3 export jobs for processing",
  "results": {
    "total_sequencers": 1,
    "total_mailboxes": 3,
    "total_combinations": 3,
    "new_exports_created": 3,
    "duplicate_exports_skipped": 0,
    "missing_sequencer_uids": []
  },
  "exports": {
    "created": [
      { "uid": "exp_...", "sequencer_uid": "seq_123456789", "mailbox_uid": "mb_111", "status": "queued" }
    ],
    "duplicates": []
  }
}

Connecting is asynchronous — a 200 here means the export jobs were queued, not that every mailbox is live in the sequencer yet. Poll /export/status (below) to track real progress, and don’t assume success from this response alone.

Poll export status


curl -X POST https://api.infrabox.software/v1/api/sequencers/export/status \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "X-Workspace-Id: YOUR_WORKSPACE_UID" \
  -H "Content-Type: application/json" \
  -d '{ "mailbox_uids": ["mb_111", "mb_222", "mb_333"] }'

Each mailbox/sequencer pair reports status: queued → pending → processing → completed, or errored / failed / cancelled with error_message set.

Errors

Status	Meaning
`400`	Invalid body — e.g. neither `sequencer_uid` nor `sequencer_uids` given alongside `mailbox_uids`, or (on `/add`/`/get-sequencers-tags`) the platform API key was rejected
`401`	Missing/invalid API key
`404`	Mailboxes or sequencers not found in this workspace
`500`	Internal error