oanor
Sign up free
Marketplace Pricing Features Sign in

API · /timelapse-api

Time-lapse API

healthy 4,130 Subscribers

Time-lapse photography maths as an API, computed locally and deterministically — the clip-length, interval and storage numbers a photographer, filmmaker or camera app plans a sequence with. The clip-length endpoint trades a long shoot for a short clip: the frames captured = the shoot duration ÷ the interval, and the clip length = those frames ÷ the playback frame rate — shooting for 60 minutes at one frame every 5 seconds gives 720 frames, and at 24 fps that plays back in 30 seconds, a 120× speed-up. Longer intervals compress time harder but can stutter on fast motion. The interval endpoint works backwards from a target clip: the frames needed = the target clip length × the frame rate, and the interval = the shoot duration ÷ those frames, so a 60-minute shoot for a 20-second clip at 24 fps needs 480 frames, one every 7.5 seconds. The storage endpoint sizes the card and disk: total storage = the frame count × the size of one frame, and because time-lapse shoots full-resolution stills (RAW ~20–30 MB each), 720 RAW frames at 25 MB is about 18 GB for a single 30-second clip — which is why a long lapse eats cards fast. Everything is computed locally and deterministically, so it is instant and private. Ideal for time-lapse and intervalometer apps, photography-planning tools, and production calculators. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For video bitrate and file size use a bitrate API.

#timelapse #photography #video #intervalometer #media #developer-tools
api.oanor.com/timelapse-api
Get an API key Try in playground → Contact provider

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

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

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

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
95 ms
Server probes · 24h
Subscribers
4,130
active
Total calls
44
last 7 days
status Full status page → · 12 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 7,400 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 7,400 calls/month
  • 2 req/sec
  • Clip length + interval + storage
  • No credit card
Sign in to subscribe

Starter

€6.95 /month

  • 62,500 calls / month
  • 6 requests / second
  • Hard cap (429 above quota, no overage)
  • 62,500 calls/month
  • 6 req/sec
  • Interval planning & storage
  • Email support
Sign in to subscribe

Pro

€23.80 /month

  • 244,000 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • 244,000 calls/month
  • 15 req/sec
  • Camera-app & production pipelines
  • Priority support
Sign in to subscribe

Mega

€73.50 /month

  • 1,145,000 calls / month
  • 40 requests / second
  • Hard cap (429 above quota, no overage)
  • 1,145,000 calls/month
  • 40 req/sec
  • Platform & app scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Flickr Photos API

Live public photo streams from Flickr, the original photo-sharing community, served from Flickr's open public feeds — no key, nothing cached. Flickr has hosted billions of photos from photographers, museums and agencies for two decades. The recent endpoint returns the newest public photos uploaded across all of Flickr right now, each with its title, photographer, capture and publish dates, tags and ready-to-use image URLs at several sizes. The tag endpoint returns the newest public photos for one or more tags — sunset, wildlife, street — the hashtag feed of Flickr, with a match-any or match-all mode. The user endpoint returns a photographer's most recent public photostream by their Flickr ID; institutions like NASA on The Commons publish here. Every photo comes back cleaned up: the photographer name pulled out of the raw author field, machine tags filtered away from human tags, and the static image URL expanded into square, small, medium and large variants plus a link to the photo page. Everything is live from Flickr's public feeds, nothing stored. This is the Flickr photo-discovery layer for any gallery, wallpaper, photography, moodboard or social app. Distinct from Pixelfed and mainstream social-network APIs — this is Flickr's public photo stream by recency, tag and user. Feeds return the 20 most recent public photos per query. 3 endpoints, no key on our side.

api.oanor.com/flickr-api

Photography Exposure API

Photographic exposure maths as an API, computed locally and deterministically — the exposure-value, equivalent-exposure and Sunny-16 numbers a photographer, camera-app developer or educator works the exposure triangle with. The exposure-value endpoint gives EV = log₂(aperture² ÷ shutter) and the ISO-100-normalised EV100 (subtracting log₂(ISO/100)) — every one-EV step is a stop, a doubling or halving of light — so bright sun reads about EV 15 and a typical interior EV 6–8, and equal-EV settings give the same exposure. The equivalent endpoint applies the reciprocity at the heart of the triangle: exposure ∝ shutter × ISO ÷ f-number², so when you close the aperture or drop the ISO it returns the new shutter that keeps the brightness constant — going from f/2.8 to f/5.6 needs four times the shutter time. The sunny16 endpoint gives the classic meterless rule: in bright sun shoot f/16 at about 1/ISO (1/125 s at ISO 100), opening up in stops for softer light — slight overcast f/11, overcast f/8, heavy overcast f/5.6, open shade f/4, and f/22 on snow or sand — solving the shutter for your chosen ISO and aperture. Everything is computed locally and deterministically, so it is instant and private. Ideal for camera and photography apps, exposure-calculator and teaching tools, and metering and automation utilities. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For depth of field and hyperfocal distance use a photography (optics) API.

api.oanor.com/exposure-api

Darkroom API

Analog darkroom and film maths as an API, computed locally and deterministically — the three corrections that bite when you develop film and make prints by hand. The reciprocity endpoint corrects long exposures for reciprocity failure, where film loses sensitivity past about a second: corrected time = metered^p (Schwarzschild p ≈ 1.3 for many films, settable per datasheet), so a metered 10-second exposure really wants about 20 seconds, a full stop more, while anything under the threshold is left untouched. The printexposure endpoint adjusts enlarger exposure when you change print size — light spreads as you raise the head, so exposure is proportional to (magnification + 1)², where magnification is print size ÷ negative size: going from 2× to 4× magnification turns a 10-second exposure into 27.8 seconds, about 1.5 stops, ready for f-stop printing. The pushpull endpoint scales development time for pushing or pulling film by N stops — time = base × factor^stops, roughly +40 % per stop pushed — turning a 7-minute base into 13.7 minutes at +2 stops, or 5 minutes pulled a stop. Everything is computed locally and deterministically, so it is instant and private. Ideal for film-photography and darkroom apps, light-meter and timer companions, lab and workshop tools, and analog-photography sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For digital depth-of-field use a photography API; for lab molarity use a dilution API.

api.oanor.com/darkroom-api

Photography Calculator API

Camera and optics maths as an API. The depth-of-field endpoint computes the near and far limits of sharp focus, the total depth of field and the hyperfocal distance from a focal length, aperture and focus distance, using the circle of confusion for your sensor format — full-frame, APS-C, Micro Four Thirds, 1-inch, medium format, Super 35 and more, or your own value. The field-of-view endpoint gives the horizontal, vertical and diagonal angle of view for a focal length on a given sensor, plus the crop factor and the 35 mm-equivalent focal length. The exposure endpoint computes the exposure value (EV) from aperture, shutter speed and ISO, and can also solve for the shutter speed or aperture that hits a target EV. Everything is computed locally and deterministically, so it is instant and private. Ideal for photography and videography apps, camera and lens tools, focus-stacking and landscape planning, and teaching exposure and optics. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This computes camera optics; for reading EXIF metadata from photo files use an EXIF API.

api.oanor.com/photography-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Time-lapse API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Time-lapse API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Time-lapse 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 Time-lapse API cost?
Time-lapse API has a free tier with 100 calls / month. Paid plans start at €6.95 / 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 Time-lapse API GDPR-compliant?
All requests to Time-lapse 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/timelapse-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/timelapse-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/timelapse-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/timelapse-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.