Clipping Platform API

Clipping platform API for tracking clip views and payouts

Clippers connect their TikTok, Instagram and YouTube accounts once, and you read each clip's views straight from the platform's API before you pay out.

One API for clipping platforms and campaign operators. Clippers connect their accounts through OAuth, you import their clips and read views, likes, comments and shares on TikTok, Instagram Reels and YouTube Shorts.

Last updated: November 2026

One API keyNo per-account fees15 platformsAPI key authScheduled publishingOfficial APIs838k+ connected accountsDirect engineer support

Quick start
// 1. Send the clipper to a hosted connect pageconst { url } = await fetch("https://api.bundle.social/api/v1/social-account/create-portal-link", {  method: "POST",  headers: { "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY, "Content-Type": "application/json" },  body: JSON.stringify({    teamId: clipper.teamId,    socialAccountTypes: ["TIKTOK", "INSTAGRAM", "YOUTUBE"],    redirectUrl: "https://yourapp.com/campaigns/connected",  }),}).then((r) => r.json());// 2. Read the clipper's imported TikTok clips with their viewsconst { posts } = await fetch(  `https://api.bundle.social/api/v1/post-history-import/posts?teamId=${clipper.teamId}&socialAccountType=TIKTOK`,  { headers: { "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY } },).then((r) => r.json());

Verifying clip views natively

  • TikTok, Instagram and YouTube each need their own developer app, review, OAuth flow and token refresh before you can read one view count.
  • Screenshots can be edited and public scrapers break or get blocked, so the payout number depends on whoever is best at faking it.
  • A campaign with hundreds of clippers on three platforms means thousands of posts to re-check until the payout window closes.

What bundle.social handles

  • Clippers connect through one hosted OAuth flow, and bundle.social keeps their tokens refreshed.
  • Each clip comes back with its platform post ID, permalink and publish time.
  • Views, likes, comments and shares use the same fields on every platform.

Plan the payout cutoff around the refresh schedule

Clips published through bundle.social refresh daily for their first 30 days. Imported clips carry the count from the moment of import, and keeping them current needs the imported posts analytics add-on. Read the count at the cutoff, store it, and pay against that.

How it works

Connect accounts once, then create and schedule posts with channel-specific fields from one API.

  1. 01

    Clipper connects their account

    Create one team per clipper and send them to a hosted connect page. bundle.social stores and refreshes the tokens.
  2. 02

    Import their recent clips

    Start a post history import for the account, limited to the latest videos if you only care about campaign clips. Each import returns posts with an analytics snapshot.
  3. 03

    Match submissions and pay out

    Match the submitted link to an imported post by permalink or platform ID, store the view count you pay against, and keep the timestamp for disputes.

Build social media workflows without rebuilding every platform

Why clipping platforms need an API instead of screenshots

A clipping campaign pays clippers per thousand views on short clips cut from a creator's streams, podcasts or launches. The platform in the middle collects the creator's budget, publishes the campaign rules and pays clippers once their clips are watched. Every step depends on one number, and most platforms still collect it from a screenshot, a manual link check or a public scraper.

Screenshots can be edited. Scrapers break when a platform changes its markup and get blocked at volume. A clipping platform API reads views through an account the clipper authorized, from the platform's own endpoint. That count can trail the number shown in the app, but the clipper cannot change it.

One integration instead of TikTok, Instagram and YouTube separately

Reading views natively means three developer apps, three review processes, three token lifecycles and three data shapes. TikTok, Instagram and YouTube report views under different fields and at different delays, and Instagram only exposes insights for professional accounts.

bundle.social returns post analytics for every supported platform in one shape, so payout code reads one views field. What still differs is what each platform counts as a view, which belongs in your campaign rules.

Matching submissions to real posts

A clipper submits a link. Your platform needs to confirm that the link belongs to an account the clipper connected, that it went up after the campaign started, and how many views it has now. Importing the connected account's recent videos gives you the platform's own post ID, permalink and publish time for each clip. Clippers often submit short share links, so resolve those to the platform post ID before matching.

Imports are asynchronous jobs: you start one, poll it until it reports COMPLETED, then read the posts. Limit each import to the latest videos so a clipper with a large archive does not use up the monthly import allowance on clips that predate the campaign.

Payout timing and the numbers you store

View counts keep moving after a clip goes up, and sometimes move down when a platform filters invalid traffic. Store the snapshot you paid against, with its timestamp, rather than re-reading the live number during an audit.

Right before payout you can force a refresh on a single clip, a few times per day. Each forced refresh is a call to the platform, so spend them on clips near the payout threshold. Forced refreshes work on clips published through bundle.social, and on imported clips with the add-on.

What a clipping platform needs from a social API

Account connection, clip data and view counts for every clipper, without three separate platform integrations.

Per-clip analytics

Views, unique views, likes, comments, shares and saves per post, in one shape for TikTok, Instagram, YouTube, Facebook and the other supported platforms.

Post history import

Import up to 500 posts per account per month on Business, filtered to videos and to the latest uploads, so campaign clips arrive without the clipper's whole archive.

One team per clipper

Pro and Business plans have no cap on teams. Each clipper gets an isolated workspace under your API key, and the connect page can show your logo and name.

Publishing from the same API

If your platform also posts clips for creators, the same accounts can receive scheduled TikTok videos, Reels and Shorts.

Developer example

Import a clipper's latest videos and read their views

Examples use bundle.social's public API shape: API key authentication, a post date, selected social account types, and platform-specific data.

TypeScript
const headers = { "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY, "Content-Type": "application/json" };// Start an import of the clipper's 30 latest TikTok videosconst job = await fetch("https://api.bundle.social/api/v1/post-history-import", {  method: "POST",  headers,  body: JSON.stringify({    teamId: clipper.teamId,    socialAccountType: "TIKTOK",    count: 30,    onlyLatest: true,    mediaType: "VIDEO",    withAnalytics: true,  }),}).then((r) => r.json());// Poll until job.status === "COMPLETED", then read the clipsconst { posts } = await fetch(  `https://api.bundle.social/api/v1/post-history-import/posts?teamId=${clipper.teamId}&socialAccountType=TIKTOK&limit=100`,  { headers },).then((r) => r.json());// Match on the platform post ID; short share links won't equal the permalinkconst clip = posts.find((post) => post.externalId === submission.platformPostId);const latest = clip?.analytics.sort((x, y) => +new Date(y.createdAt) - +new Date(x.createdAt))[0];const views = latest?.views ?? 0;

Supported content

  • TikTok videos
  • Instagram Reels
  • YouTube Shorts
  • Facebook Reels
  • Per-clip views
  • Likes, comments, shares
  • Analytics snapshots

Honest limitations

  • View counts come from each platform's API and follow that platform's reporting delay. They are not real time.
  • Post history imports are capped per account per month: 100 posts on Pro and 500 on Business.
  • Refreshing analytics on imported posts after the import requires the imported posts analytics add-on.
  • Clippers must connect their own accounts. bundle.social does not read views from accounts that have not authorized your app.
  • Instagram insights are available for professional (Business or Creator) accounts only.

Developer-first infrastructure

Visible post status

Track scheduled, processing, posted, retrying, and error states per post.

Verbose errors

When native APIs fail, we return human-readable error messages and actionable recovery steps.

Flat pricing

No per-post counting. Predictable pricing for teams managing many users, workspaces, and connected accounts.

Same-day support

Direct access to the engineers building the API. We respond to technical issues the same day, sometimes the same hour.

Technical guides & documentation

Questions developers ask before building

What is a clipping platform API?

An API that lets a clipping platform connect clippers' social accounts and read the views on their clips from TikTok, Instagram and YouTube, so payouts rest on platform data instead of screenshots.

Can I track views on clips that were not posted through bundle.social?

Yes. Import the clipper's recent posts and each one comes with the counts at import time. Refreshing them later needs the imported posts analytics add-on.

Which platforms return view counts?

TikTok, YouTube, Instagram, Facebook, Threads, Snapchat, Pinterest, Reddit, LinkedIn, Bluesky, Mastodon and X. X analytics are read on request only because X bills each read.

Can clippers see my brand instead of bundle.social?

Yes. The hosted connect page can carry your logo and name.

Keep comparing your options