oanor
Sign up free
Marketplace Pricing Features Sign in

API · /timecode-api

Timecode API

healthy 4,486 Subscribers

Convert SMPTE timecode for video, film and broadcast. Turn a timecode (HH:MM:SS:FF) into an absolute frame number or into real-time seconds, and turn a frame count back into a timecode — at 23.976, 24, 25, 29.97, 30, 50, 59.94 or 60 fps. Crucially it handles drop-frame correctly: at 29.97 and 59.94 fps it drops the right frame numbers each minute (notated with a semicolon, 01:00:00;00) so an hour of timecode lines up with an hour of real time, and it computes real seconds with the exact fractional rate (30000/1001). Perfect for NLE and editing tools, subtitle and caption timing, playout and broadcast automation, and media asset management. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from date/time, duration and relative-time tools.

#timecode #smpte #video #broadcast #frames #developer-tools
api.oanor.com/timecode-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/timecode-api/openapi.json
/api/timecode-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
93 ms
Server probes · 24h
Subscribers
4,486
active
Total calls
60
last 7 days
status Full status page → · 20 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 860 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 860 calls/month
  • 2 req/sec
  • Frames + timecode + seconds
  • No credit card
Sign in to subscribe

Starter

€1.60 /month

  • 7,100 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 7.1k calls/month
  • 8 req/sec
  • Drop-frame 29.97/59.94
  • Email support
Sign in to subscribe

Pro

€20.00 /month

  • 130,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 130k calls/month
  • 20 req/sec
  • Editing / playout pipelines
  • Priority support
Sign in to subscribe

Mega

€56.00 /month

  • 670,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 670k calls/month
  • 50 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Viewing Distance API

TV and projector viewing-distance maths as an API, computed locally and deterministically. The distance endpoint takes a screen diagonal (inches or centimetres) and aspect ratio and returns the screen width and height and the recommended seating distance for each standard — SMPTE's 30° minimum viewing angle (the farthest comfortable seat), THX's 36° recommendation and THX's 40° maximum (the closest) — in inches, feet, centimetres and metres, plus an overall recommended range. Pass a resolution (720p, 1080p, 1440p, 4K or 8K) and it also gives the pixel-acuity distance, the point beyond which a 20/20 viewer can no longer resolve individual pixels, so moving closer stops adding detail. The screensize endpoint reverses it: from a seating distance it recommends the screen diagonal for each standard. The fov endpoint gives the horizontal field of view for a screen at a distance, with a verdict on whether it falls in the recommended range. The geometry is exact: width = diagonal × aspect-width / hypot(aspect), and distance = (width/2) / tan(angle/2). Everything is computed locally and deterministically, so it is instant and private. Ideal for home-theatre and AV apps, TV and monitor retail tools, room and seating planners, and AV-installer calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is viewing-distance geometry; for pixel density (PPI) from a resolution use a PPI API.

api.oanor.com/viewdistance-api

Bitrate & Transfer API

Media, file-size and data-transfer maths as an API. The file-size endpoint relates bitrate, duration and file size: give any two and it computes the third — so you can find the size of a video at a given bitrate and length, the bitrate of a file of known size and length, or how long a file will play. The transfer-time endpoint computes how long a file takes to download or upload over a given bandwidth (with optional protocol overhead), or the bandwidth needed to move it within a target time. The storage endpoint works out how many hours of media at a bitrate, or how many items of a given size, fit in a storage capacity. Bitrates use decimal units (kbps, Mbps, Gbps) and sizes are reported in both decimal (KB/MB/GB/TB) and binary (KiB/MiB/GiB/TiB). Everything is computed locally and deterministically, so it is instant and private. Ideal for video and audio encoding, streaming and CDN planning, storage and backup sizing, and download-time estimates. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is bitrate and transfer maths; for plain byte-unit conversion use a bytes API.

api.oanor.com/bitrate-api

Subtitle API

Work with subtitle and caption files — parse, convert and re-sync, entirely locally. The parse endpoint reads SubRip (.srt) or WebVTT (.vtt) text into clean, structured cues — index, start, end (as both HH:MM:SS,mmm timecodes and milliseconds), duration and the cue text (multi-line preserved) — auto-detecting which format you sent. The convert endpoint converts between SRT and WebVTT, getting the details right: the timestamp separator (comma for SRT, dot for WebVTT), adding or removing the WEBVTT header, and renumbering cues. The shift endpoint moves every timestamp by an offset in milliseconds, positive or negative, to fix a track that runs early or late, clamping at zero so nothing goes negative. Everything is computed locally and deterministically, so it is instant and private — your media files never leave the request. Ideal for video and streaming pipelines, caption editors and players, localization and translation workflows, accessibility, and fixing out-of-sync subtitles. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This handles subtitle files; for SMPTE video timecode (HH:MM:SS:FF) use a timecode API.

api.oanor.com/subtitle-api

Aspect Ratio API

Aspect-ratio and resize maths on plain dimensions — no image upload needed. The ratio endpoint reduces a width×height to its simplest integer ratio (1920×1080 → 16:9), its decimal value and a common name. The resize endpoint scales a dimension while preserving the ratio: give a new width or a new height and get the other side. The fit endpoint fits a source size into a target box using contain (letterbox) or cover (crop), returning the resulting size, the scale factor and the centering offset. Perfect for responsive layouts and CSS aspect-ratio, video and thumbnail framing, image-grid planning and print sizing. Pure local computation — it works on numbers only and never touches image files. Live, nothing stored. 4 endpoints. Distinct from image processing/resizing (which operates on actual files) and from geometry of shapes.

api.oanor.com/aspectratio-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Timecode API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Timecode API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Timecode API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Timecode API cost?
Timecode API has a free tier with 100 calls / month. Paid plans start at €1.60 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Timecode API GDPR-compliant?
All requests to Timecode API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/timecode-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/timecode-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/timecode-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/timecode-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.