The CacheFly API gives you full programmatic control over your CDN infrastructure — from provisioning services and managing domains to configuring caching rules, monitoring real-time performance, and shipping logs to your own storage targets.
Everything you can do in the portal, you can automate through the API. Build deployment pipelines that provision and configure services on demand, integrate CDN metrics directly into your own dashboards, or drive cache invalidation from your CI/CD workflow.
Beyond the core REST API, CacheFly supports a scripting layer that lets you attach custom logic directly to your services. Scripts run at the edge and enable advanced use cases such as fine-grained cache control for dynamic content, on-the-fly image optimisation, and signed URL access protection — all without changing your origin infrastructure.
API Reference
Guides
Script Documentation
Advanced Cache Control
Define per-path and per-extension caching policies for dynamic websites. Significantly increases cache-hit ratio, reduces origin load, and improves end-user performance — without any changes to your origin infrastructure. Configuration is managed through a YAML or JSON file attached to your service.
CacheFly Smart Image Optimization
Transform and optimise images on the fly at the edge. Resize, convert formats, adjust quality, and strip metadata — served directly from cache so your origin never takes the hit. Supports JPEG, PNG, WebP, and AVIF output with flexible transformation pipelines.
CacheFly Signed URLs
Restrict access to private or premium content by validating a cryptographic signature embedded in the URL. Enforce expiry times, IP restrictions, and path policies without touching your origin. Tokens are generated server-side and verified at the edge before any request reaches your infrastructure.
CacheFly Signed URLs v2
An updated signing scheme with a structured default policy, per-path exceptions, and a fallback mechanism. Supports multiple signing algorithms. Designed for teams migrating from other CDN providers or requiring compatibility with existing token infrastructure.