Schedule posts with the REST API

Steps

1. 1
   Step 1Mark as done: step 1

   Find your workspace

   Call /api/v1/me. It lists your workspaces and which one is used by default. To use another, send its id in the Skylane-Workspace-Id header.

   curl https://skylane-api.moneymasterhq.com/api/v1/me \
     -H "Authorization: Bearer YOUR_API_KEY"

2. 2
   Step 2Mark as done: step 2

   Get your account ids

   List connected accounts and copy the id of each one you want to post to.

   curl https://skylane-api.moneymasterhq.com/api/v1/accounts \
     -H "Authorization: Bearer YOUR_API_KEY"

3. 3
   Step 3Mark as done: step 3

   Create and schedule in one call

   Send the caption, the account ids and a schedule. Add an Idempotency-Key so a retry after a network error never makes a second post. Leave out schedule to save a draft.

   curl -X POST https://skylane-api.moneymasterhq.com/api/v1/posts \
     -H "Authorization: Bearer YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -H "Idempotency-Key: blog-launch-1" \
     -d '{"caption": "Our new guide is live.", "accountIds": ["YOUR_ACCOUNT_ID"], "schedule": {"mode": "schedule", "scheduledAt": "2026-11-20T09:30:00Z"}}'

4. 4
   Step 4Mark as done: step 4

   Fix anything pre-flight finds

   If a platform would reject the post, you get 422 with error.issues: each issue names the account, the problem and how to fix it. Nothing is saved, so fix it and send the request again with a new idempotency key.

5. 5
   Step 5Mark as done: step 5

   Follow the result

   Call /results to see each account's state: scheduled, published with its url, or failed with error.message and error.fixHint. Or subscribe to webhooks to be told - see Receive Developer webhooks.

   curl https://skylane-api.moneymasterhq.com/api/v1/posts/YOUR_POST_ID/results \
     -H "Authorization: Bearer YOUR_API_KEY"

6. 6
   Step 6Mark as done: step 6

   Add media

   Upload a file with POST /api/v1/media (multipart, field file) or import one with POST /api/v1/media/from-url, then put the returned id in mediaIds. Files get the same type, size and storage checks as in the app.

   curl -X POST https://skylane-api.moneymasterhq.com/api/v1/media/from-url \
     -H "Authorization: Bearer YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"url": "https://example.com/photo.jpg", "altText": "What the photo shows"}'