Data · api-request-flow
API request flow
A request / response round trip: client, server and database nodes in a row; labelled request packets travel between them, responses come back in a second colour, each arrival pulses the node and pops an HTTP status badge, and a call log fills in underneath.
A free, MIT-licensed animated chart from the Opus Motion Library — 616 motions for Remotion, React and plain HTML.

What API request flow is for
Explaining how an API call works, backend architecture, REST / HTTP basics, error-handling stories (a 500 shakes the node), latency and developer-docs videos.
Details
- Category
- Animated charts & data visualisation
- Length
- 8.0 s (240 frames at 30 fps)
- Formats
- 16:9, 1:1, 9:16
- Weight
- light
- Transparent overlay
- yes
- Seamless loop
- no
- Text props
title- Colour props
backgroundpanelinkaccentaccent2okColorerrColor- Mood
- hud
- Roles
- subject
Use API request flow in Remotion, React or HTML
Remotion project
# copy this motion into your Remotion project
node cli/mgl.mjs add api-request-flow --to ../my-app/src
# render an mp4 (run in the library folder)
node cli/mgl.mjs render api-request-flow --props '{"title":"What happens on a request","background":"#0C0F16","panel":"#151A25","ink":"#EAEFF8","accent":"#4C8DFF","accent2":"#F5A524","okColor":"#2EC4A6","errColor":"#FF5C5C"}'
# or export for apps / editors: mp4 | webm-alpha | prores-alpha | gif | png | poster
node cli/mgl.mjs export api-request-flow --as webm-alpha --props '{"title":"What happens on a request","background":"#0C0F16","panel":"#151A25","ink":"#EAEFF8","accent":"#4C8DFF","accent2":"#F5A524","okColor":"#2EC4A6","errColor":"#FF5C5C"}'React / Next.js
import {MotionPlayer} from 'opus-motion-library/web';
<MotionPlayer
motion="api-request-flow"
props={{
title: 'What happens on a request',
background: '#0C0F16',
panel: '#151A25',
ink: '#EAEFF8',
accent: '#4C8DFF',
accent2: '#F5A524',
okColor: '#2EC4A6',
errColor: '#FF5C5C',
}}
playOnView
loop="auto"
/>Plain HTML / WordPress
<script src="opus-motion.element.js" defer></script>
<opus-motion motion="api-request-flow"
props='{"title":"What happens on a request","background":"#0C0F16","panel":"#151A25","ink":"#EAEFF8","accent":"#4C8DFF","accent2":"#F5A524","okColor":"#2EC4A6","errColor":"#FF5C5C"}'>
</opus-motion>Compose spec (multi-scene video)
{
"width": 1920,
"height": 1080,
"fps": 30,
"scenes": [
{
"motion": "api-request-flow",
"props": {
"title": "What happens on a request",
"background": "#0C0F16",
"panel": "#151A25",
"ink": "#EAEFF8",
"accent": "#4C8DFF",
"accent2": "#F5A524",
"okColor": "#2EC4A6",
"errColor": "#FF5C5C"
}
}
]
}API request flow props
15 parameters — change any of them to make the motion yours.
| Prop | Default | What it does |
|---|---|---|
nodes | [{"label":"Client","kind":"client","sub":"web app"},{"label":"API server","kind":"serve… | boxes in order [{label, kind?: 'client' | 'server' | 'database' | 'cache' | 'queue' | 'service', sub?}] (2–5) |
steps | [{"from":0,"to":1,"label":"POST /orders"},{"from":1,"to":2,"label":"INSERT order"},{"fr… | packets in order [{from, to (node indexes), label, status? (HTTP code, 4xx/5xx = red + shake), statusText?, ms?, type? ('request' | 'response'; default: response when going back toward node 0)}] |
title | "What happens on a request" | heading (empty = none) |
showLog | true | show the call log under the diagram |
stepFrames | 42 | frames per packet |
speed | 1 | timing multiplier |
startAt | 0 | frame the flow starts |
background | "#0C0F16" | page colour or 'transparent' |
panel | "#151A25" | node / card colour |
ink | "#EAEFF8" | text colour |
accent | "#4C8DFF" | request colour |
accent2 | "#F5A524" | response colour |
okColor | "#2EC4A6" | 2xx badge colour |
errColor | "#FF5C5C" | 5xx badge / error colour |
fontFamily | "" | monospace font override (empty = JetBrains Mono) |
Related motions

Flow diagram (packets on edges)
How-it-works explainers (APIs, AI agents, networks, payments), onboarding and architecture videos: pass `nodes` + `edges`; optionally…
flow-diagram
JSON tree expand
API-response explainers, "what the data looks like" beats, structured-output / schema stories for AI, developer docs and tutorials,…
json-tree-expand
Network graph (your nodes and edges)
Explicit relationship maps: system architecture, supply chains, org or contact networks, dependency graphs, knowledge graphs, social…
network-graph
Deploy pipeline stages
DevOps / CI-CD explainers, "how we ship" and release-process videos, deployment tooling promos, incident stories (set one stage to fail).
deploy-pipeline-stages
Git branch graph
Explaining branching and merging, release flow, pull-request workflows, version-control tutorials, "how our team ships" and developer-tool…
git-branch-graph
Crowd tracks
Footfall / mobility / network-activity explainers, smart-city and retail-analytics films, "everyone is connected" beats; drop a crowd…
crowd-tracks
Notes & credits
Technique sources:
- original (generic developer explainer)