curl --request POST \
--url https://api.lemlist.com/api/sender-picture/sync \
--header 'Authorization: Basic <encoded-value>' \
--header 'Content-Type: application/json' \
--data '{}'
{
"data": {
"enqueued": 1,
"mailboxes": [
{
"mailboxId": "dem_Hw3Jk6Ds1Fy5Gu0Ea",
"email": "john@acme.com",
"provider": "m365"
}
]
}
}
Sender picture
Sync Sender Picture
Queues a push of a user’s lemlist profile picture onto the mailboxes they bought through lemlist.
POST
/
sender-picture
/
sync
curl --request POST \
--url https://api.lemlist.com/api/sender-picture/sync \
--header 'Authorization: Basic <encoded-value>' \
--header 'Content-Type: application/json' \
--data '{}'
{
"data": {
"enqueued": 1,
"mailboxes": [
{
"mailboxId": "dem_Hw3Jk6Ds1Fy5Gu0Ea",
"email": "john@acme.com",
"provider": "m365"
}
]
}
}
Choosing a scope
| scope | Mailboxes pushed | Target |
|---|---|---|
not_synced (default) | Every mailbox of the user that is not up to date. Synced ones are left alone. | The API key owner, or userId |
all | Every mailbox of the user, synced ones pushed again. | The API key owner, or userId |
mailbox | One mailbox, pushed again even when it is already synced. | mailboxId or email (required). userId is ignored: the mailbox’s own owner’s picture is pushed. |
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.
Authorizations
Body
application/json
Was this page helpful?