foopixel

API reference

FooPixel API documentation

FooPixel accepts supported media uploads and returns a public media URL after validation. See the generated facts below and pricing and hosting limits for current account policies. Hosted still images and MP4 can be normalized and need not match the original bytes. Keep source files separately.

Start an upload

  1. Create a session with POST /v1/sessions.
  2. Hash the exact file bytes with SHA-256 and create an upload with POST /v1/uploads.
  3. Send raw bytes once to the returned Worker URL using all returned headers.
  4. Complete the upload with POST /v1/uploads/{id}/complete and wait until the asset is ready.

Keep the returned expiry. For uncertain writes, use the private status URL rather than replaying bytes. See the full API guide for authentication and recovery details.

Hosting limits

Contract 1-1f2fd4d3 · policy 2026-09-28-v2

ClientMaximum fileRetentionDaily attemptsBatch items
Visitor5 MiB1 day2525
Free account20 MiB7 days250250
PRO account20 MiBNo routine expiry while PRO is active2,5001,000

Supported upload formats

audio/mp4 · audio/mpeg · audio/wav · audio/webm · image/gif · image/heic · image/heif · image/jpeg · image/png · image/webp · video/mp4

New public IDs use 16 Base62 characters; older links remain accepted.

Production configuration

  • Motion uploads: Available
  • Credits: Available
  • CDN: Available

Check live API capabilities before using an optional feature. Configuration availability does not guarantee an account entitlement or provider health.

Reference files