The API Report CardAPI Index
Imgix

Imgix API

imgix.com

Imgix is an API-first image CDN with two surfaces: a URL-based Rendering API for transforms and a REST Management API for sources, assets, and purges. Plans are self-serve and credit-based. SDKs span roughly 15 languages, with signed URLs and webhooks for asset events.

Last verified: July 2026Software & Data Tools
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODTwo public APIs: a URL-parameter Rendering API for transforms and a REST Management API for sources and assets.
AccessGOODSelf-serve credit-based plans from trial to enterprise; API keys come with any account.
CoverageGOODTransforms, AI operations (background removal, generative fill), sources, assets, purges, usage reports, and users.
AuthGOODBearer API keys for the Management API; rendering URLs can be HMAC-signed for secure sources.
Docs & DXGOODOpen-source SDKs in about 15 languages plus CMS plugins; docs are split between rendering and management surfaces.
StabilityGOODThe URL-parameter contract is long-lived with a machine-readable spec; SDKs have shipped occasional breaking changes.
Supergood: Imgix shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Imgix scores A on the API Report Card. Imgix is an API-first image CDN with two surfaces: a URL-based Rendering API for transforms and a REST Management API for sources, assets, and purges. Plans are self-serve and credit-based. SDKs span roughly 15 languages, with signed URLs and webhooks for asset events.

Tried to integrate with Imgix?
SOURCES
Per-endpoint rate limits trigger 429s; raising limits requires premium/enterprise contract negotiation docs.imgix.com ↗
424 origin errors are common when origin S3/GCS bucket configuration drifts (permissions, CORS), surfaces as broken images downstream docs.imgix.com ↗
Recent SDK breaking changes (e.g., imgix-swift fixes for secure-source params) have required customer code updates github.com ↗
Documentation is split across rendering vs management APIs, no single OpenAPI bundle covering both surfaces docs.imgix.com ↗
Status page shows long history of incidents (1,558+ tracked by StatusGator over ~11 years); last notable 'Elevated rendering errors' incident June 12, 2025 statusgator.com ↗
IsDown has logged 117 incidents since April 2020 across Imgix services isdown.app ↗
Credits draw from one shared pool across delivery, transformations and storage, making per-API cost attribution opaque to engineering teams gumlet.com ↗
Signed-URL implementation differs by source type (web folder vs S3 vs Imgix-hosted) which creates cross-stack confusion docs.imgix.com ↗
No GraphQL surface, REST/URL-param only docs.imgix.com ↗
Recent pricing changes ('credit' model) significantly raised costs for some customers, reports of 5x bill increases after migration g2.com ↗
Capterra 'Value for Money' score is 2.0/5, the lowest-rated dimension across reviewer categories capterra.com ↗
Credit system is hard to predict, media management, delivery and transformations all draw from one prepaid pool, leading to overages or wasted capacity gumlet.com ↗
Overages billed at 120% of standard rate; unused credits expire and do not roll over gumlet.com ↗
Bandwidth costs at scale can be much higher than commodity CDNs like Bunny.net or Cloudflare Images gumlet.com ↗
Limited free tier and short trial (30 days / 100 credits) makes evaluation difficult for production-grade workloads imgix.com ↗
Learning curve on URL parameter API, reviewers cite that it is powerful but initially hard to use g2.com ↗
Pricing tiers feel rigid, limited middle ground between self-serve and enterprise capterra.com ↗
StatusGator has tracked 1,500+ incidents over ~11 years of monitoring; most recent notable issue was 'Elevated rendering errors' in June 2025 statusgator.com ↗