POST /find_redirect • Credits: 1 credit per call

Find Redirect follows a URL through every HTTP redirect and returns the final destination. Send a POST request with the link parameter. The response holds the final URL, the full redirect chain, the hop count, and the final HTTP status code. Each call costs 1 credit.

A short link such as https://bit.ly/example hides its destination. A tracking link from an email tool or an ad platform hides the destination in the same way. Find Redirect sends the request itself, follows each Location header, and reports where the link ends. Find Redirect follows up to 20 hops and accepts the redirect status codes 301, 302, 303, 307, and 308. Find Redirect is a utility endpoint. It runs inside RichAPI and calls no external data provider. The only network traffic is the request to the target host and to every host in the redirect chain.

RichAPI adds no default value to the request body. An empty link value returns a 400 error.

Find Redirect checks the host before the first request and again before every hop. If the first URL points at a private host, the response is a 400 error. If a later hop points at a private host, the response is a 200 response with resolved_successfully: false and final_status_code: 0.

The table below shows a real link value and the exact result for each field. Each row is one call.

A URL that sends no redirect returns redirect_count: 0 and is_redirected: false. In that case, redirect_link holds the same URL that you sent.

The block below is an example response for the request body {"link": "https://bit.ly/example"}. The short link passes through one HTTP hop before it reaches the final HTTPS page.

A list of scraped posts or emails holds short links and tracking links. Two different short links can point at the same page, so a count of unique links is wrong. Resolve each link first, then store the destination.

CAUTION: Do not send a short link to a scraping endpoint. The scraper reads the redirect page, and the call returns empty content and costs the full price.

Find Redirect costs 1 credit per call. At $0.02 a credit, the rate on the 1,000 and 5,000 credit packs, one call costs $0.02. Larger packs cost less per credit. RichAPI charges the credit on a 200 response only. Every error response costs no credits.

CAUTION: A response with resolved_successfully: false is still a 200 response. RichAPI charges 1 credit for it.

Every error response holds an error field with a plain-language message.

Find Redirect follows 20 redirects. The redirect_count field reports the number of hops that Find Redirect followed, and its maximum value is 20. A chain longer than 20 hops stops at hop 20.

Find Redirect returns both. The redirect_chain field holds every URL in order, and the first entry is the URL that you sent. The redirect_link field holds the final destination on its own.

Find Redirect stops after 20 hops. The response holds redirect_count: 20, a redirect_chain of 21 URLs, and the status code of the last redirect in final_status_code, for example 302. A redirect status code is under 400, so resolved_successfully stays true. To detect the cap, compare redirect_count to 20.

Find Redirect waits 10 seconds for each hop. The timeout applies to one hop, and not to the whole chain. A host that does not answer returns a 200 response with final_status_code: 0 and resolved_successfully: false.

No. Find Redirect blocks localhost, private IP addresses, reserved IP addresses, and link-local IP addresses. Find Redirect runs this check on the first URL and on every hop. An open redirect on a public host therefore cannot reach an internal address.

Yes. A dead short link returns HTTP 200 with resolved_successfully: false, and RichAPI charges 1 credit. RichAPI charges no credit for a 400 error, for example an empty link value.

Yes. Find Redirect returns the result in the same response. The endpoint needs no second call, no polling, and no webhook.