Social media API example: SDK and curl snippet generator
A real social media API example, generated for you: a POST https://api.skedcast.com/v1/posts request as curl, JavaScript fetch, or Python requests — the exact same request shape in whichever language you actually use.
This generates the exact real request a POST /v1/posts call sends — it does not call the API for you. Swap in your own API key and run it yourself.
curl -X POST 'https://api.skedcast.com/v1/posts' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: YOUR_UNIQUE_KEY' \
-d '{"clientId":"6d58a0f2-1c3e-4b7a-9f21-0a1b2c3d4e5f","content":"Launch day is here 🚀","mediaIds":[],"targets":{"mode":"accounts","accountIds":["a1b2c3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d"]},"schedule":{"type":"now"}}'Social media API example FAQ
- Is there a published SkedCast SDK package?
- Not yet — no `@skedcast/sdk` npm package is published today, so these snippets use plain `fetch` (JavaScript) and `requests` (Python) directly against the REST API, which works in any language today.
- Do the curl, JavaScript and Python snippets send the exact same request?
- Yes — all three are rendered from the same underlying request-body builder, so the JSON body cannot drift between languages.
- Does this actually call the API?
- No — like the API request builder, this only composes the snippet locally in your browser. Swap in your own API key and run it in a terminal or your own code to actually send it.
- Why does the snippet include an Idempotency-Key placeholder?
- A real POST /v1/posts call requires one, so a retried request is never accidentally scheduled twice — replace the placeholder with your own unique value per real attempt.
Ready to broadcast everywhere?
Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.