Skip to main content
POST

​
Choosing a scope

Pushing a synced mailbox again is useful when its picture was changed by hand on Google or Microsoft: lemlist cannot see that change, so the mailbox still reads synced. Mailboxes already queued or syncing are never queued twice. enqueued is 0 when every mailbox in scope is already up to date or already being pushed.
The call only queues the push; there is no confirmation step. A background job processes the queue about every minute, and a Google Workspace mailbox takes a few tens of seconds more. Follow the progress with Get Sender Picture Status.
This endpoint is in closed beta. It answers 403 with the code BETA_NOT_ENABLED unless the sender picture beta is enabled for your team.

Authorizations

​
Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Body

application/json
​
scope
enum<string>
default:not_synced

not_synced: every mailbox of the user that is not up to date; synced ones are left alone. all: every mailbox of the user, synced ones pushed again. mailbox: one mailbox, pushed again even when already synced.

Available options:
not_synced,
all,
mailbox
​
mailboxId
string

scope=mailbox only: the mailbox to push, as returned by Get Sender Picture Status. Either mailboxId or email is required with scope=mailbox.

Example:

"dem_Xq7Lm2Pz9Rt4Vb8Nc"

​
email
string<email>

scope=mailbox only: the address of the mailbox to push, instead of mailboxId.

Example:

"john@example.com"

​
userId
string

scope=not_synced or scope=all only: a teammate whose mailboxes to push. Omit to push the API key owner's. Ignored with scope=mailbox, which always pushes the picture of the mailbox's own owner.

Example:

"usr_Tn8Bv2Mc4Xz6Lq1Pw"

Response

Mailboxes queued

​
data
object