Key takeaways
- A single POST /v1/posts call handles publishing to any connected platform, so your app doesn’t need per-platform integration code.
- The REST API works from any language with plain fetch or requests calls, and you can generate a typed client from the OpenAPI 3.1 document at https://skedcast.com/openapi.json.
Post to social media via API use case: authenticate and send the request
Generate a real API key from your workspace settings, send it as a Bearer token, then POST to /v1/posts with your content, target accounts and schedule — see the snippet generator for a real, copy-paste example.
Handle the response
The API returns a real per-platform status you can store or surface in your own app.
use caseapideveloper
FAQ
- Can I use a typed client?
- Yes. Generate one from the OpenAPI 3.1 document at https://skedcast.com/openapi.json with a tool such as openapi-typescript, openapi-fetch or openapi-generator. The REST API also works directly with plain fetch or requests calls in any language.
- What does authentication look like?
- API keys for server-to-server use, or OAuth 2.1 with PKCE when acting on behalf of a user or building a public integration.
- Where do I see the exact request shape?
- The API request builder and snippet generator both compose the real request from documented shapes — copy directly from either.