This API is designed to provide a comprehensive analysis of a domain's behavior when an HTTP request is made, offering a clear and structured view of the redirection cycle, the final response, and the associated metadata. Its main function is to receive an input domain and return detailed information that allows you to understand how the server handles the request, what path it follows to reach the final URL, and what characteristics the response delivered by the website has.
When querying a domain, the API identifies the initial URL and automatically follows any chain of redirects, recording for each hop the URL visited, the redirect destination, and the corresponding status code. This makes it easy to detect common behaviors such as redirects from HTTP to HTTPS, from domains without “www” to domains with “www,” or internal changes caused by security policies or load balancers. Each redirect is organized in an easy-to-read structure that includes a step number, the HTTP status, and the resulting URL.
The final result provides a deep understanding of how a domain responds to a real request. It is especially useful for monitoring security configurations, validating migrations, checking for correct redirects, or debugging access issues. In short, the API provides a complete and organized snapshot of a website's initial loading process, from the submitted URL to the final server response.
Analyzes domains, follows redirects, obtains status codes, and returns complete data from the final URL, headers, and relevant cookies.
URL Data - Endpoint Features
| Object | Description |
|---|---|
url |
[Required] Enter a URL |
country |
Optional Enter a country code |
{"info":{"start_url":"https://google.com","final_url":{"url":"https://www.google.com/","redirect_to":"https://www.google.com/","status_code":200,"is_end_url":true,"headers":{"Content-Type":"text/html; charset=UTF-8","Content-Security-Policy-Report-Only":"object-src 'none';base-uri 'self';script-src 'nonce-VSpX2ECFwxX2OeKXOaerNQ' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hp","Cross-Origin-Opener-Policy":"same-origin-allow-popups; report-to=\"gws\"","Report-To":"{\"group\":\"gws\",\"max_age\":2592000,\"endpoints\":[{\"url\":\"https://csp.withgoogle.com/csp/report-to/gws/other\"}]}","Accept-CH":"Sec-CH-Prefers-Color-Scheme","Permissions-Policy":"unload=()","P3P":"CP=\"This is not a P3P policy! See g.co/p3phelp for more info.\"","Date":"Tue, 18 Nov 2025 23:32:16 GMT","Server":"gws","X-XSS-Protection":"0","X-Frame-Options":"SAMEORIGIN","Expires":"Tue, 18 Nov 2025 23:32:16 GMT","Cache-Control":"private","Set-Cookie":"AEC=AaJma5uoz7D07Us4-klSDf9xNW2wtaABuzu7fPOEdfhGz2w0topur-MIvTw; expires=Sun, 17-May-2026 23:32:16 GMT; path=/; domain=.google.com; Secure; HttpOnly; SameSite=lax","Transfer-Encoding":"chunked","Alt-Svc":"h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000"}},"urls_count":2},"urls":[{"url":"https://google.com","redirect_to":"https://www.google.com/","status_code":301,"url_number":1},{"url":"https://www.google.com/","redirect_to":"https://www.google.com/","status_code":200,"url_number":2}]}
curl --location --request GET 'https://zylalabs.com/api/11318/web+header+data+extractor+api/21457/url+data?url=https://google.com&country=US' --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 GET URL Data endpoint returns detailed information about a domain's HTTP request behavior, including the initial URL, final URL, redirect chain, HTTP status codes, headers, and relevant cookies. This data helps users understand how a server processes requests and manages redirects.
Key fields in the response include "start_url," "final_url" (with subfields like "url," "redirect_to," "status_code," and "is_end_url"), and "headers." Each redirect in the chain is also documented with its corresponding status code and URL.
The response data is structured in a JSON format, with a clear hierarchy. It includes an "info" object containing the "start_url" and "final_url" details, along with a list of redirects, each represented by its step number, status code, and resulting URL.
The endpoint provides information on the initial and final URLs, the entire redirect chain, HTTP status codes for each redirect, response headers, and cookies. This comprehensive data aids in analyzing web behavior and troubleshooting issues.
Users can customize their requests by specifying the initial URL they want to analyze. The API automatically follows redirects, so no additional parameters are needed for redirect tracking. Users can focus on specific domains of interest.
Typical use cases include monitoring website security configurations, validating URL migrations, checking for proper redirects, and debugging access issues. This data is essential for web developers, SEO specialists, and security analysts.
Data accuracy is maintained through real-time HTTP requests to the specified URLs, ensuring that the information reflects the current state of the web. The API follows standard HTTP protocols to gather reliable data.
Users can expect common patterns such as HTTP to HTTPS redirects, "www" to non-"www" redirects, and various status codes indicating success (200), redirection (3xx), or errors (4xx/5xx). Understanding these patterns aids in diagnosing web behavior.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
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.
Service Level:
100%
Response Time:
3,882ms
Service Level:
100%
Response Time:
3,038ms
Service Level:
100%
Response Time:
3,264ms
Service Level:
100%
Response Time:
4,082ms
Service Level:
100%
Response Time:
3,907ms
Service Level:
100%
Response Time:
7,660ms
Service Level:
100%
Response Time:
10,154ms
Service Level:
100%
Response Time:
3,976ms
Service Level:
100%
Response Time:
11,307ms
Service Level:
100%
Response Time:
92ms
Service Level:
100%
Response Time:
2,917ms
Service Level:
100%
Response Time:
3,229ms
Service Level:
100%
Response Time:
3,171ms
Service Level:
100%
Response Time:
4,191ms
Service Level:
100%
Response Time:
2,745ms
Service Level:
50%
Response Time:
6,214ms
Service Level:
100%
Response Time:
2,717ms
Service Level:
100%
Response Time:
2,058ms
Service Level:
100%
Response Time:
2,706ms
Service Level:
100%
Response Time:
3,673ms