GlossaryVideo API

Video API

A video API is a set of HTTP endpoints that lets developers add video to their own product through code: upload, encoding, storage, streaming, playback, live broadcasts, analytics and AI features. The app sends a request, such as "create an asset from this file", and the service runs the pipeline and returns IDs, URLs and webhook events. Instead of operating encoders, packagers and CDNs, the team writes integration code and keeps control of the user experience, access rules and viewing data.

How does a video API work?

A video API follows a request and event pattern. Your backend authenticates with an access token and creates an asset, either by asking for a direct upload URL or by passing a URL the service can pull from. The client then sends the file straight to the provider, so your servers never carry the bytes.

The service works asynchronously. It transcodes the source into a bitrate ladder, packages it as HLS or DASH, stores the renditions and serves them through a CDN. Because this takes time, the API does not hold your request open. It sends a webhook, an HTTP callback to an endpoint you own, when the asset is ready or a step fails. Well-built APIs sign webhooks so you can verify the sender.

Playback uses a separate identifier. The asset has an ID for management, and a playback ID that goes into the player URL. Keeping them apart lets you rotate or restrict playback without touching the stored media.

Video API vs. building your own video pipeline

A self-built pipeline usually starts with FFmpeg on a few servers and a storage bucket behind a CDN. That works for a first release. The ongoing work comes later: a job queue that absorbs upload spikes, retries for failed encodes, ladder choices per content type, manifest packaging for Apple and Android devices, token checks at the CDN, DRM license integration, and a player SDK per platform that reports what went wrong. Each new codec or device class reopens part of that stack.

A video API turns those components into calls and events. The trade is control over internals in exchange for speed and a maintained surface. Building in-house tends to make sense when video infrastructure is the product itself, or when requirements are unusual enough that no provider exposes the needed controls. Where video is a feature of a larger product, the engineering time usually goes further on what sits around the player.

What does a video API include?

The core of any video API is on-demand video: create an asset, transcode it, store it, return a playback URL. Most add a live endpoint that issues stream keys and ingest URLs and records each broadcast for replay. Around that sit the parts that decide how usable the API is in production.

Access control covers public playback IDs, signed URLs with expiry, and DRM for content that must stay encrypted. Media utilities produce thumbnails, preview GIFs, storyboard sprites for scrubbing, clips and watermarks. Data endpoints report per-view quality of experience, such as startup time, rebuffering and errors, broken down by device, region and CDN. Newer APIs add AI features that run on the same asset, such as transcripts, captions, chapters and moderation flags. SDKs wrap all of this in server languages and in client libraries for upload and playback. The useful questions are how many of these share one asset ID, and how many need a second vendor.

How is a video API priced?

Video APIs bill on usage, so the first question is which unit each line counts. Encoding is billed per minute of source video on some APIs and per output rendition on others, where a taller ladder means a larger charge. Storage is counted in gigabytes or in minutes kept. Delivery is counted in gigabytes sent or in minutes watched, and the gigabyte model rises with bitrate even when watch time is flat.

The second question is what sits outside the core lines. Live usually bills ingest minutes and viewer minutes separately. DRM tends to be a platform fee plus a charge per license. AI features such as transcripts are priced per minute processed. Some providers also bill origin egress, API requests or a monthly minimum. Because these lines interact, compare providers with a real month of your uploads, library size and watch time pushed through each provider's billing model.

How does the FastPix video API work?

FastPix exposes one REST API at api.fastpix.io/v1, split into On-Demand, Live Streaming, Playback, Signing Keys, DRM, Simulcast, In-Video AI and Data endpoints that share the same media and playback IDs. Server SDKs cover Node, Python, Java, Go, Ruby, PHP and .NET, and client SDKs handle resumable upload on web, iOS, Android and Flutter.

Assets come from a direct upload or a pull from S3, GCS, Azure Blob or any HTTPS URL, and the FastPix Migration Tool moves whole libraries from other video platforms or S3. Each source gets a per-title ladder in H.264 and HEVC (H.265) as standard, with AV1 available on request, packaged as CMAF for HLS and DASH. Live streams take RTMP, RTMPS or SRT and deliver LL-HLS at 4 to 7 seconds. Playback IDs are public, signed with JWTs, or DRM-protected. Thumbnails render by frame, size and format under the video's access policy. Delivery runs on a multi-CDN network of 300+ points of presence, video and images can be served from your own custom domain, and FastPix Player SDKs for web, Android (Media3), iOS (AVPlayer) and Flutter play the same playback ID. In-Video AI returns transcripts in 50+ languages, chapters and moderation flags, and Video Data reports 56 dimensions per view.

Ready-made plugins for WordPress, Moodle, Strapi and Sanity bring the same API into existing sites: the WordPress plugin also covers LearnDash, TutorLMS and LifterLMS, and the Moodle plugins add tracked video activities to Moodle courses.

Standard encoding is free up to 4K and counted once per source minute. Storage bills per rendition-minute, streaming per minute watched, live encoding at $0.0324 a minute up to 1080p, and AI per minute processed. New accounts get $25 of credit, and the free plan needs no card.

Watch: What is FastPix? | All-in-One Video API Platform