What is queued this week, and whether a boost slot is free
One call that answers both "what is going out this week" and "can I boost, and on which day". Call it before schedule-post so you pick a boost time that has a slot instead of absorbing a 409. A database-only read: no LinkedIn call and no LinkedIn quota spent. It is still paced like every other call on the account (roughly one every 3 seconds), so call it before scheduling rather than polling it in a loop. `scheduledPosts` counts posts by status in the week and buckets them by local day. `boosts.days` gives `used`/`limit`/`hasSlot` for each of the seven days — this is the same per-day view the web calendar uses. `boosts.quota` and `boosts.earliestOpenSlot` describe the window right now: when `canBoostNow` is false, `earliestOpenSlot` is when the next slot frees up. Note that a boost window is NOT a calendar week. Depending on plan it is a local calendar day (multi-boost plans), a window centred on the boost time (Starter/Pro), or a rolling 7 days (free and trial) — so read `quota.limit` as the limit for that window, not for the week.
/posts/schedule/weekCode Examples
curl -X GET 'https://api.connectsafely.ai/linkedin/posts/schedule/week' \ -H 'Authorization: Bearer <your_api_key>'One call that answers both "what is going out this week" and "can I boost, and on which day". Call it before schedule-post so you pick a boost time that has a slot instead of absorbing a 409.
A database-only read: no LinkedIn call and no LinkedIn quota spent. It is still paced like every other call on the account (roughly one every 3 seconds), so call it before scheduling rather than polling it in a loop.
scheduledPosts counts posts by status in the week and buckets them by local day. boosts.days gives used/limit/hasSlot for each of the seven days — this is the same per-day view the web calendar uses. boosts.quota and boosts.earliestOpenSlot describe the window right now: when canBoostNow is false, earliestOpenSlot is when the next slot frees up.
Note that a boost window is NOT a calendar week. Depending on plan it is a local calendar day (multi-boost plans), a window centred on the boost time (Starter/Pro), or a rolling 7 days (free and trial) — so read quota.limit as the limit for that window, not for the week.
Parameters
| Name | In | Required | Type | Description |
|---|---|---|---|---|
accountId | query | No | string | Scopes the post list and picks the workspace whose boost quota is reported. Omit to use the default account. |
weekStart | query | No | string | Start of the 7-day window. Defaults to Monday 00:00 UTC of the current week. |
timezone | query | No | string | IANA name deciding which local day each post and boost slot falls on. Defaults to UTC. |
Request Body
No request body.
Responses
| Status | Description |
|---|---|
| 200 | Week view |
| 401 | Unauthorized |
| 500 | Server error |
200 Response Parameters
| Name | Type | Description |
|---|---|---|
success | boolean | |
weekStart | string (date-time) | |
weekEnd | string (date-time) | |
timezone | string | |
scheduledPosts | object | |
boosts | object |
200 Example
{
"success": true,
"weekStart": "2024-01-15T10:30:00.000Z",
"weekEnd": "2024-01-15T10:30:00.000Z",
"timezone": "2024-01-15",
"scheduledPosts": {},
"boosts": {}
}401 Response Parameters
| Name | Type | Description |
|---|---|---|
error | string |
401 Example
{
"error": "example_value"
}500 Response Parameters
| Name | Type | Description |
|---|---|---|
error | string |
500 Example
{
"error": "example_value"
}