CodivUpload TypeScript SDK — Publish to 12 Platforms with Full Type Safety

Install

The SDK is published on npm as codivupload. It works in Node.js 18+, Bun, Deno, and any TypeScript project. Zero dependencies beyond the runtime's built-in fetch.

npm install codivupload

yarn add codivupload

pnpm add codivupload

Quick start — 4 lines to publish

Get an API key from your CodivUpload dashboard, initialize the client, and call posts.create(). That's it. The SDK handles authentication, serialization, and error parsing.

import CodivUpload from "codivupload";

const codiv = new CodivUpload("cdv_your_api_key");

const post = await codiv.posts.create({
  platforms: ["tiktok", "instagram"],
  description: "Hello world!",
  media_urls: ["https://cdn.example.com/video.mp4"],
});

console.log(post.id, post.status);
// "post_a1b2c3d4" "queued"

The response is fully typed. post.id is a string, post.platforms is a string[], post.status is a union type. Your editor catches mistakes before your code runs.

Why an SDK instead of raw HTTP?

You can absolutely call the CodivUpload REST API directly with fetch or Axios. Nobody is stopping you. But here's what you're signing up for:

const res = await fetch(
  "https://api.codivupload.com/v1/posts",
  {
    method: "POST",
    headers: {
      "Authorization": "Bearer cdv_...",
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      platforms: ["tiktok"],
      description: "Hello",
      media_urls: ["https://..."],
    }),
  }
);
const data = await res.json();
// data is `any` — no autocomplete

const codiv = new CodivUpload("cdv_...");

const post = await codiv.posts.create({
  platforms: ["tiktok"],
  description: "Hello",
  media_urls: ["https://..."],
});
// post is typed — full autocomplete

Full API reference

The SDK covers every resource in the CodivUpload API. Here's each one with working examples you can copy straight into your project.

// Create — publish immediately
const post = await codiv.posts.create({
  platforms: ["tiktok", "instagram", "youtube"],
  description: "New product drop!",
  media_urls: ["https://cdn.example.com/video.mp4"],
});

// Schedule — publish at a specific time
const scheduled = await codiv.posts.schedule({
  platforms: ["linkedin", "x"],
  description: "Monday motivation.",
  media_urls: ["https://cdn.example.com/carousel.mp4"],
  scheduled_date: "2026-04-05T14:00:00Z",
});

// List — filter by status and paginate
const list = await codiv.posts.list({
  status: "completed",
  limit: 20,
});

// Get — single post by ID
const single = await codiv.posts.get("post_a1b2c3d4");

// Update — modify before it publishes
await codiv.posts.update("post_a1b2c3d4", {
  description: "Updated description",
});

// Delete
await codiv.posts.delete("post_a1b2c3d4");

// List all connected profiles
const profiles = await codiv.profiles.list();

// Create a whitelabel profile for a client
const profile = await codiv.profiles.create({
  username: "client_brand",
  profile_name: "Acme Corp",
});

// Delete a profile
await codiv.profiles.delete("uuid-of-profile");

// Upload from a public URL
const media = await codiv.media.upload(
  "https://example.com/raw-video.mp4"
);

// Use the CDN URL in a post
await codiv.posts.create({
  platforms: ["tiktok", "instagram"],
  description: "Fresh content",
  media_urls: [media.url],
});

// Start a looping live stream
await codiv.broadcasts.create({
  profile_name: "my_channel",
  title: "24/7 Lo-fi Radio",
  media_url: "https://cdn.example.com/mix.mp4",
  loop: true,
});

// List active broadcasts
const streams = await codiv.broadcasts.list();

// Stop a broadcast
await codiv.broadcasts.stop("broadcast_id");

Platform-specific overrides

Cross-posting doesn't mean every platform gets identical content. Each platform has unique fields — TikTok's privacy level, YouTube's category ID, Instagram's media type, LinkedIn's visibility. The SDK types all of these as optional top-level parameters. Pass only what you need; everything else uses sensible defaults.

await codiv.posts.create({
  platforms: ["tiktok", "instagram", "youtube", "linkedin", "x"],
  description: "Product launch!",
  media_urls: ["https://cdn.example.com/launch.mp4"],

  // TikTok
  tiktok_privacy_level: "public",

  // Instagram
  instagram_media_type: "REELS",

  // YouTube
  youtube_type: "video",
  youtube_privacy_status: "public",
  youtube_category_id: "28",

  // LinkedIn
  linkedin_visibility: "PUBLIC",

  // X (Twitter)
  x_reply_settings: "following",
});

Every override parameter autocompletes in your editor. Hover over tiktok_privacy_level and your IDE shows the valid values: "public" | "friends" | "self". No guessing, no typos, no 422 errors at runtime because you spelled a field wrong.

Error handling

The SDK throws a CodivUploadError for any non-2xx response. The error object includes .status (the HTTP status code) and .message (a human-readable explanation). Use instanceof to catch SDK errors specifically while letting unexpected exceptions bubble up.

import CodivUpload, { CodivUploadError } from "codivupload";

const codiv = new CodivUpload("cdv_your_api_key");

try {
  await codiv.posts.create({
    platforms: ["tiktok"],
    description: "Testing error handling",
    media_urls: ["https://cdn.example.com/video.mp4"],
  });
} catch (err) {
  if (err instanceof CodivUploadError) {
    console.error(err.status);  // 422
    console.error(err.message); // "media_urls: URL is not accessible"
  }
}

SDK vs MCP vs REST API

CodivUpload offers three ways to interact with the platform programmatically. The TypeScript SDK, the MCP server (for AI agents), and the raw REST API. They all hit the same backend. The difference is ergonomics.

Building a Node.js backend, a Next.js app, or a cron job? Use the SDK. Wiring CodivUpload into Claude, ChatGPT, or Cursor? Use the MCP server. Working in Python? Use the official Python SDK (pip install codivupload). Working in Go or another language? Use the REST API directly.

Resources