What the social media TypeScript SDK looks like#
One client, three auth modes (cookie session, OAuth bearer token, or a Developer API key), typed resources, and a typed error class instead of hand-parsed JSON:
ts
import { createSkedcast, SkedcastApiError } from "@skedcast/sdk";
const sk = createSkedcast({
baseUrl: "https://api.skedcast.com/v1",
apiKey: process.env.SKEDCAST_API_KEY,
});
try {
const { data } = await sk.posts.create({ clientId, content, targets, schedule });
} catch (err) {
if (err instanceof SkedcastApiError && err.isRateLimited) {
await wait(err.retryAfterSeconds ?? 1);
} else throw err;
}What marketing teams should use today#
Every SDK method is a typed wrapper over a real /v1 endpoint — nothing it does is unreachable from plain HTTP. Until the npm package ships, call the REST API directly (fetch, curl, or your language's HTTP client) using the same request/response shapes documented in the quickstart and conventions reference, or generate a typed client from the published OpenAPI 3.1 spec.
sdktypescriptsocial media typescript sdk
FAQ
- Can I install @skedcast/sdk from npm today?
- Not yet. Build against the REST API and the OpenAPI 3.1 spec in the meantime — the public npm release is planned, and this page will update the moment it ships.
- What languages does SkedCast support for the API?
- Any language that can make an HTTP request — the REST API is the universal contract. TypeScript gets a typed first-party client today; the OpenAPI spec lets you generate a typed client for most other languages.
- Is this the same social media TypeScript SDK the SkedCast console uses?
- Yes — @skedcast/sdk is not a separate demo client; it's the exact typed SDK the SkedCast console itself calls against the same /v1 REST API.