Lightning-fast redirect lookups at the edge
Query redirect rules from 300+ global edge locations with sub-50ms response times. A single HTTP GET returns the destination and status code — no SDK required.
$ curl "https://edge.redirections.app/v1/lookup\?project=PROJECT_ID&path=/old-blog/my-post" \-H "Authorization: Bearer rk_live_..."{"destination": "/blog/my-post","statusCode": 301,"matchType": "exact"}
How edge API redirect lookups work
When a request hits your origin server with a URL that might need redirecting, your server makes a single HTTP GET to the Redirections Edge API. The request travels to the nearest of our 300+ edge locations, where a pre-warmed worker evaluates your redirect rules against the incoming URL in under 50 milliseconds.
The edge worker loads your project's compiled rule set from a globally replicated datastore. Rules are evaluated with exact matches checked first, then prefix matches. The first matching rule wins, and the API returns the destination URL and HTTP status code.
Because the rule evaluation happens at the edge rather than your origin, you get consistent sub-50ms latency regardless of where your users are located. There are no cold starts — workers are always warm and ready to serve lookups instantly.
Why teams choose this
Built for performance, reliability, and developer experience.
Global Edge Network
Deployed to 300+ locations across 6 continents for minimal latency everywhere.
Zero Cold Starts
Always-warm workers mean consistent sub-50ms response times, even at 3 AM.
Protocol Agnostic
Works with any HTTP client — curl, fetch, Nginx, HAProxy, or your own code.
High Throughput
Handle millions of redirect lookups per day without breaking a sweat.
Edge API use cases
Site migration
Route legacy URLs to their new destinations during domain or CMS migrations without slowing down page loads.
CMS migration
Query the edge API from your new CMS to handle legacy URLs transparently, keeping old links working during and after the migration.
Domain consolidation
Merge multiple domains into one by querying redirect rules at the edge, ensuring all old domain URLs resolve to the canonical domain.
Legacy URL cleanup
Gradually retire old URL structures by routing them to canonical paths, preserving SEO equity and user bookmarks.
How we compare
See how Redirections compares to alternatives.
Built for performance at global scale
The Edge API is designed as a stateless lookup service. Every request is self-contained — you send a URL and get back a redirect decision. This design means the API scales horizontally without any coordination between edge nodes. Whether you're handling 100 lookups per day or 10 million, every request follows the same fast path.
Under the hood, redirect rules are compiled into an optimized matching structure when you deploy. Exact matches use a hash map for O(1) lookups, while prefix matches are sorted by length for efficient evaluation. The result is consistent single-digit millisecond evaluation times even for projects with thousands of rules.
Integration is straightforward because the API uses plain HTTP. You can call it from Nginx, HAProxy, Cloudflare Workers, a Node.js server, or a simple curl command. No language-specific SDK is required, and the response format is a simple JSON object with the fields you need to issue the redirect.
Related Articles
Architecting Edge Redirects: Reducing Latency and Enhancing Privacy in 2026
Optimizing redirect patterns using CDN Rules Engines and Edge Workers to achieve sub-50ms global latency.
Dynamic Edge Redirects: Low-Latency Lookups for Nginx and Next.js
Implementing sub-10ms redirect lookups at the edge using Nginx maps and Next.js Edge Config.
Optimizing Global Redirect Architecture via Edge Computing
Shifting redirect logic to the edge to reduce TTFB and eliminate origin roundtrips.
Related features
Explore more capabilities that work great together.
Start querying in under a minute
Get your API key and deploy your first redirect rule to the edge. No credit card required.
No credit card required · Free tier available