Schedule a social post
https://api.norreach.app/v1/social/posts/{id}/schedulePuts a post on the calendar: at at it is published to every network it has a version for, through the connected profiles — exactly as the app's Schedule button. It needs the social.publish role, outreach must not be paused (409 outreach_paused; if outreach is paused later, the post waits until it resumes), and the post must pass the calendar's checks (422 post_schedule_blocked with a reason: no_networks, empty_text, too_long, account_not_connected, instagram_media_required, too_many_media). Scheduling a scheduled post again moves it. dry_run=true runs every check and changes nothing.
curl -X POST "https://api.norreach.app/v1/social/posts/{id}/schedule" \
-H "Authorization: Bearer $NORREACH_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"at": "2026-11-12T08:30:00Z",
"timezone": "Europe/Stockholm"
}'{
"object": "social_post_action",
"post_id": "5e6f7a8b-9c0d-4e1f-8a2b-3c4d5e6f7a8b",
"action": "schedule",
"dry_run": false,
"changed": true,
"status": "scheduled",
"scheduled_at": "2026-11-12T08:30:00.000Z",
"note": "Scheduled — it goes out at that time unless outreach is paused then (it waits until outreach resumes)."
}Authorizations
Bearer authentication: send Authorization: Bearer <key>, with an API key or an OAuth access token. The key needs the scope social:publish. API keys and scopes
Path parameters
An id (UUID).
Query parameters
Run every check and return what would happen, changing nothing.
Headers
Any unique string (≤ 255). The same key with the same request returns the first answer for 24 hours.
Body
application/json
When it goes out (RFC 3339). A time in the past goes out within a minute or two.
The IANA time zone to show it in (e.g. Europe/Stockholm). Display only.
Response
200application/json— Schedule a social post
An id (UUID).
scheduleunscheduledeletefalse when there was nothing to do (or on a dry run).
The post's status now (or after it, on a dry run).
ideadraftin_reviewscheduledpublishingpublishedfaileddeletedErrors
Errors are application/problem+json with a stable code.
| Status | Code | Meaning |
|---|---|---|
| 400 | bad_request | The request couldn't be read. |
| 400 | unknown_field | The request has a field this operation doesn't know. |
| 400 | idempotency_key_required | This operation needs an Idempotency-Key header. |
| 401 | unauthorized | A valid API key is required. |
| 403 | insufficient_scope | This API key doesn't have the scope this operation needs. |
| 403 | feature_not_enabled | The API isn't switched on for this workspace. |
| 403 | role_forbidden | The key's creator's role can't do this. |
| 404 | not_found | That doesn't exist. |
| 409 | idempotency_in_progress | A request with this Idempotency-Key is still running. |
| 409 | conflict | That conflicts with the current state. |
| 409 | outreach_paused | Outreach is paused for this workspace. |
| 413 | too_large | The request body is too large. |
| 422 | validation_failed | The request has invalid fields. |
| 422 | idempotency_mismatch | This Idempotency-Key was used with a different request. |
| 422 | post_schedule_blocked | This post can't be scheduled yet. |
| 429 | rate_limited | Too many requests. Slow down and try again. |
| 500 | server_error | Something went wrong on our side. |
| 503 | unavailable | The API isn't available right now. Try again shortly. |