# API docs developers actually watch and ship from

Turn the same flow you would have screen-recorded for a tutorial into a polished API documentation video that cuts integration time from days to hours. No timeline editor. No production team. Drop in the recording, get back the embed-ready walkthrough.

## Create an API documentation video for [api-name]. 
Walk through [auth/endpoint/workflow] showing code examples and expected responses for [developer-audience].

### Or pick a video type to get started
- Auto Explainer Video
- Product Launch
- Changelog
- Feature Announcement
- Customer Onboarding
- Sales Enablement
- Tutorial / How-To
- Social Clip
- Teaser / Trailer

## Trusted by teams at

### From "I gave up after two hours" to"watched the video, shipped it before lunch"

#### The old way
The reference page told me what each call does. It never told me which order to make them in.

#### The ngram way
A four-minute API documentation video links straight from the docs. The developer watches you chain the calls in real time, sees the headers, the error handling, the pagination. They pause, write their own code, unpause. The implicit knowledge in the reference becomes explicit on screen.

### Time to first integration
Under 1 day was: 1-3 days of trial and error

### Support questions per dev
Near zero was: 3-5 repeated questions

### Time to update one video
Under 15 min was: Full day per re-record

### Dev satisfaction signal
Great docs was: Docs are painful

## API walkthroughs from whatever you have
Bring a terminal recording or your existing reference docs. ngram turns either into an API documentation video developers can watch, follow, and ship from on the first attempt.

1. **Path one - Most popular**
   - Drop your terminal recording
   - .mp4 · .mov · 18:42
2. **Path two**
   - Paste your API reference
   - OpenAPI · Markdown · ReadMe

### One API documentation video, embed-ready
Frame-accurate captions, step labels per endpoint, smart zooms on every code snippet — exportable as MP4 or hosted at a share link your docs page can iframe.

### What changes when API docs ship as video
Developers integrate in hours, not days. An API documentation video shows the full integration pattern, not just isolated endpoints. Developers see how calls chain together, what headers belong where, and how to handle the errors that always bite in production.

## Terminal recording → embed-ready video in 3 steps

1. **Record your API walkthrough** - 30 seconds
   - Screen-record yourself making API calls in your terminal or IDE.
2. **Review the polished tutorial** - 2 minutes
   - ngram cuts dead air, zooms into code and JSON responses, and adds step labels per endpoint.
3. **Publish to your developer portal** - instant
   - Export as MP4 or grab an embed link for ReadMe, GitBook, Docusaurus, or your custom docs site.

## Built for API documentation video, specifically
- **Screen Recording Polish** — ngram detects clicks, keystrokes, and key interactions in your terminal or IDE recording.
- **Captions** — Frame-accurate captions burned in or exported as SRT. 
- **Script Generation** — ngram structures a narrative from your API docs or OpenAPI spec.
- **AI Voiceover** — Drop in a script and pick a voice from the library.
- **Brand Kit** — Define your developer portal's colors, fonts, logos, intro, and outro once.
- **Collaboration** — Share the storyboard link with team members for feedback before rendering.
- **Motion Graphics** — Animated step labels and callouts on the request lifecycle.
- **Translation** — Translate the API documentation video into multiple languages at once.

## The old way vs. the ngram way
|  | Text-Only Docs | Loom / Raw Recordings | ngram |
| --- | --- | --- | --- |
| Developer comprehension | Read, guess, debug | Watch and scrub through | Watch, follow, ship |
| Time to create | Hours per endpoint write-up | Minutes (but unpolished) | Under 30 minutes (polished) |
| Time to update | Rewrite entire sections | Re-record everything | Update just the changed scene |
| Support load reduction | Minimal | Some | Significant |
| Library scalability | Hard to maintain at scale | Inconsistent quality | Consistent, branded, repeatable |

## Ship API docs developers actually use
Turn the API documentation video your developers keep asking for into the embed your docs page already has room for. Start with a terminal recording or paste your reference. The first video is under thirty minutes away.