Storage from frames and frame size

Extraits de code

curl "https://api.oanor.com/timelapse-api/v1/storage" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/timelapse-api/v1/storage", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/timelapse-api/v1/storage");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/timelapse-api/v1/storage",
    headers={"x-oanor-key": "oanor_test_..."}
)

Exemple de réponse

Une réponse réelle de ce endpoint, capturée lors du dernier contrôle de santé.

{
    "data": {
        "note": "Card and disk planning: total storage = the frame count × the size of one frame. RAW stills run ~20–30 MB each, large JPEGs ~5–10 MB, so 720 RAW frames at 25 MB is about 18 GB — for one 30-second clip. Time-lapse eats cards fast because every second of output is dozens of full-resolution stills; size the card for the whole shoot plus a margin.",
        "inputs": {
            "frame_count": 720,
            "frame_size_mb": 25
        },
        "total_gb": 17.578,
        "total_mb": 18000
    },
    "meta": {
        "timestamp": "2026-06-07T08:17:51.621Z",
        "request_id": "fe65fa05-cfd2-48fc-aa4a-2a0da804433e"
    },
    "status": "ok",
    "message": "Storage",
    "success": true
}