Check URL for Redirects
Check - Endpoint Features
| Object | Description |
|---|---|
url |
[Required] |
{"status":"success","url":"http://zylalabs.com/","destinationStatusCode":200,"destinationUrl":"https://zylalabs.com/","numberOfRedirects":1,"totalLatency":114,"chain":[{"url":"http://zylalabs.com/","statusCode":301,"statusMessage":"Moved Permanently","latency":23,"redirectTo":"https://zylalabs.com/"},{"url":"https://zylalabs.com/","statusCode":200,"statusMessage":"OK","latency":114}]}
curl --location --request GET 'https://zylalabs.com/api/10246/redirection+api/19753/check?url=http://zylalabs.com' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Check URL for Redirects endpoint returns detailed information about the redirect chain for a specified URL. This includes the final destination URL, HTTP status codes for each redirect, and the sequence of redirects encountered.
Key fields in the response data include "final_url" (the ultimate destination), "status_codes" (HTTP status codes for each redirect), and "redirect_chain" (an array showing the sequence of URLs followed).
The response data is structured in a JSON format, with a clear hierarchy. It typically includes a main object containing fields like "final_url," "status_codes," and "redirect_chain," making it easy to parse and utilize.
Users can customize their requests using parameters such as "url" (the URL to check), "user_agent" (to simulate different browsers), and "ip" (to specify a particular IP address for the request).
The data is sourced from real-time web requests made to the specified URLs. This ensures that the redirect information is current and reflects the latest changes on the web.
Data accuracy is maintained through automated checks and validations during the redirect tracking process. The API employs enterprise-grade infrastructure to ensure reliable and consistent results.
Typical use cases include tracking affiliate link redirections, monitoring competitor redirect chains, and verifying SEO redirects. This data is essential for digital marketers and SEO professionals to optimize their strategies.
If the response contains partial or empty results, users should check the provided URL for correctness and ensure it is accessible. Additionally, consider retrying the request with different parameters or user agents to gather more data.
The Check URL for Redirects endpoint provides information about the redirect chain, including the final destination URL, HTTP status codes for each redirect, and the sequence of URLs followed. It also includes details on the user agent used and the IP address from which the request was made.
Users can customize requests by specifying parameters such as "url" (the URL to check), "user_agent" (to simulate different browsers), and "ip" (to use a specific IP address). This allows for tailored analysis based on different scenarios.
Accepted parameter values include any valid URL for the "url" parameter, common user agent strings for "user_agent," and valid IP addresses for the "ip" parameter. This flexibility enables users to test various conditions and environments.
In the response, "final_url" indicates the ultimate destination of the redirect, "status_codes" lists the HTTP status codes encountered during the redirect chain, and "redirect_chain" provides an array of URLs that were followed, allowing for detailed analysis of the redirect process.
Data accuracy is ensured through automated validation checks during the redirect tracking process. The API leverages enterprise-grade infrastructure to monitor and verify the integrity of the data collected from real-time web requests.
Users can analyze the redirect chain to identify potential SEO issues, monitor competitor strategies, or verify the functionality of marketing links. The structured JSON response allows for easy integration into analytics tools or custom applications for deeper insights.
The data covers all publicly accessible URLs across the web, regardless of region or category. This broad coverage allows users to analyze redirects from various industries, making it suitable for global SEO and marketing strategies.
Users can expect a consistent response structure with fields like "final_url," "status_codes," and "redirect_chain." Typically, the redirect chain may include multiple entries, reflecting various HTTP status codes, such as 301 or 302, indicating different types of redirects.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
2,670ms
Service Level:
100%
Response Time:
119ms
Service Level:
100%
Response Time:
3,264ms
Service Level:
100%
Response Time:
84ms
Service Level:
100%
Response Time:
19,536ms
Service Level:
100%
Response Time:
19,536ms
Service Level:
100%
Response Time:
68ms
Service Level:
100%
Response Time:
3,038ms
Service Level:
100%
Response Time:
193ms
Service Level:
100%
Response Time:
743ms
Service Level:
100%
Response Time:
196ms
Service Level:
100%
Response Time:
200ms
Service Level:
100%
Response Time:
1,166ms
Service Level:
100%
Response Time:
54ms
Service Level:
100%
Response Time:
579ms
Service Level:
100%
Response Time:
11,502ms
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
149ms
Service Level:
100%
Response Time:
199ms
Service Level:
100%
Response Time:
55ms