# Developer documentation

The SkedCast developer docs — API, authentication, scopes, and guides.

## Social media API quickstart
Make your first authenticated request to the SkedCast API in five minutes.
Read: https://skedcast.com/developers/quickstart

## OAuth 2.1 social API authentication
Authenticate with an API key (Bearer) or the OAuth 2.1 flow for third-party apps.
Read: https://skedcast.com/developers/authentication

## API scopes and permissions
The programmatic scopes an API key, OAuth token, or MCP tool may hold — reads, the publish action, library writes, and webhook management.
Read: https://skedcast.com/developers/scopes

## REST API conventions: pagination and errors
Response envelopes, keyset pagination, idempotency, correlation IDs, and the RFC 9457 error model.
Read: https://skedcast.com/developers/conventions

## The social media posting API reference
Every /v1 endpoint — posts, post targets, clients, accounts, agency, analytics, reports, best-times, media, and webhooks.
Read: https://skedcast.com/developers/api-reference

## Social media TypeScript SDK
The typed client that powers the SkedCast console — and, soon, a public npm package.
Read: https://skedcast.com/developers/sdk

## Connect an AI agent to social media (MCP)
Connect Claude (or any MCP client) to read your workspace and publish on your behalf.
Read: https://skedcast.com/developers/mcp

## Connect an app (OAuth 2.1)
A worked OAuth 2.1 flow — dynamic registration, PKCE, the authorize redirect, token exchange, refresh, and revoke.
Read: https://skedcast.com/developers/oauth

## Partner onboarding: connect a client's accounts
Create a client, mint a connect link they open with no SkedCast login, then publish on their behalf via the API.
Read: https://skedcast.com/developers/partner-onboarding

## Uploading media & video covers
The real upload sequence — presign, PUT, register — plus how to attach a custom video cover and narrow which platform renditions get produced.
Read: https://skedcast.com/developers/media-uploads

## Webhooks: the post published webhook, signed and delivered
Subscribe once, stop polling. All 40 events — publish outcomes per destination, media readiness and failures, account health, approvals, reports, team and client changes — HMAC-signed with retries and durable de-duplication.
Read: https://skedcast.com/developers/webhooks

## Versioning & changelog
How the API is versioned and how breaking changes are handled.
Read: https://skedcast.com/developers/changelog

## Social media platform capabilities API
A generated JSON export of every platform's real publishing limits and pacing defaults — the same registry the product itself enforces, not a hand-typed copy.
Read: https://skedcast.com/developers/data/platform-capabilities-json

## The problem+json error code reference (RFC 9457), and how to implement it
Every public SkedCast error code as structured JSON, plus how the RFC 9457 problem+json response it comes from is actually shaped.
Read: https://skedcast.com/developers/data/api-error-catalogue

## Social media platform limits JSON dataset
A versioned, freely downloadable JSON and CSV export of real platform publishing limits, CC BY 4.0 — built from SkedCast's own enforced registry.
Read: https://skedcast.com/developers/open-source/social-media-platform-limits-json