Inspect senders and change pacing

Use the Senders API to inspect connected sequence senders and adjust how they send. Connect accounts and configure signatures through Sequence settings. For the sequence lifecycle, use Sequences with the API.

Inspect the sender first

Use senders:read to list senders and retrieve one. Lists include archived senders unless you filter them out.

curl -G https://api.lightfield.app/v1/senders \
  -H "Authorization: Bearer $LIGHTFIELD_API_KEY" \
  -H "Lightfield-Version: 2026-03-01" \
  --data-urlencode 'channel[equal]=EMAIL' \
  --data-urlencode 'archived[equal]=false' \
  --data-urlencode 'limit=20'

curl "https://api.lightfield.app/v1/senders/$SENDER_ID" \
  -H "Authorization: Bearer $LIGHTFIELD_API_KEY" \
  -H "Lightfield-Version: 2026-03-01"

Save the returned id, channel, transport, health, healthReason and pacing. HEALTHY can send. UNVERIFIED email needs a health check; a working LinkedIn sender can normally be UNVERIFIED because it does not run that email health check.

Replace pacing without dropping values

Update a sender requires senders:update. It replaces pacing rather than merging individual values. Read first, preserve every step type, and send every value. Concurrent edits are last-write-wins.

For an email sender, this example permits 20 emails in a rolling 24-hour period, with a minimum spacing drawn between 120 and 240 seconds:

curl "https://api.lightfield.app/v1/senders/$SENDER_ID" \
  -X POST \
  -H "Authorization: Bearer $LIGHTFIELD_API_KEY" \
  -H "Lightfield-Version: 2026-03-01" \
  -H "Content-Type: application/json" \
  -d '{"pacing":{"EMAIL":{"dailyLimit":20,"minGapSeconds":120,"maxGapSeconds":240}}}'

The actual sends can be farther apart because of send windows or exhausted limits. For a LinkedIn sender, supply both LINKEDIN_INVITE and LINKEDIN_MESSAGE pacing from its current response, changing only the values you intend.

Read the operation’s ceilings before increasing limits; workspace limits may be lower. maxGapSeconds cannot be below minGapSeconds. Verify the returned pacing and re-read before a later edit to avoid overwriting someone else’s change.

Clear a sending pause

Mark healthy can resume contacts paused solely because of that sender. Review those contacts in Lightfield before making the call. Clearing BOUNCE_THRESHOLD also turns off bounce protection until hard bounces recur; correct the audience or addresses first.

Email senders support clearing BOUNCE_THRESHOLD, RATE_LIMIT and INVITE_LIMIT. LinkedIn senders support RATE_LIMIT, INVITE_LIMIT and UNKNOWN. Other reasons need their underlying cause fixed, such as reconnecting an account or repairing DNS.

curl "https://api.lightfield.app/v1/senders/$SENDER_ID/mark_healthy" \
  -X POST \
  -H "Authorization: Bearer $LIGHTFIELD_API_KEY" \
  -H "Lightfield-Version: 2026-03-01"

This needs senders:update. Inspect healthReason in the returned sender. A sender with nothing to clear is unchanged. Contacts pinned to another unhealthy sender can remain paused, and sequences previously deactivated by a LinkedIn limit stay deactivated until resumed.

An archived sender cannot be updated or marked healthy. For 409, re-read the sender: it may be archived, have an unsupported reason or have changed while the request ran. Resolve that state before retrying. For 400 on pacing, correct the fields and bounds instead of resubmitting unchanged values.