About the API:
The Short URL Resolver API is a service that helps users to expand shortened URLs back to their original form, created by URL shortening services. This can be useful in a number of different contexts, such as identifying the true destination of a link before clicking on it or verifying the authenticity of a website before sharing it with others.
URL shortening services are commonly used to share links on social media or messaging platforms where there is a character limit. However, these shortened links can be difficult to verify, and can sometimes lead to phishing or malware sites.
With the Short URL Resolver API, users can quickly and easily expand shortened URLs back to their original form, providing a more secure and user-friendly online experience. The API can be integrated into a wide range of applications and services, such as social media, messaging platforms, or browser extensions.
The API is easy to use and requires minimal setup and integration. It supports various programming languages and platforms, making it accessible to developers of all skill levels. Additionally, it offers a web interface for non-technical users. With this API, users can quickly and easily expand shortened URLs, without the need to visit the original website, this way it saves time and resources.
In summary, the Short URL Resolver API is a valuable tool for anyone looking to expand shortened URLs back to their original form. It helps users to access the original URL, ensuring security and avoiding phishing sites. It's easy to use and available for anyone who needs to unshorten a URL.
Pass the shortened URL and receive the unshortened version.
NOTE: Be aware that the example's shortened URL could be expired. So, the API could deliver an error when using it. We recommend you to send your own Shortened URLs to test the API correctly.
Unshort - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"status":true,"originUrl":"https://www.amazon.com/Freaks-Geeks-Complete-James-Franco/dp/B0185X2CWC/ref=as_li_ss_tl?ie=UTF8&linkCode=sl1&tag=3dblurayren-20&linkId=dab7c0ff98357b63f590a11c73e740c7"}
curl --location --request POST 'https://zylalabs.com/api/7727/short+url+resolver+api/12558/unshort' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"url": "https://amzn.to/1THmJKz"
}'
| 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 Unshort endpoint returns a JSON object containing the status of the request and the original URL. For example, a successful response includes fields like "status" (true/false) and "originUrl" (the expanded URL).
The key fields in the response data are "status," indicating the success of the request, and "originUrl," which contains the unshortened URL. If the URL is invalid or expired, the "status" will be false.
The response data is organized in a JSON format, with a clear structure that includes a boolean "status" field and a string "originUrl" field. This makes it easy to parse and utilize in applications.
The Unshort endpoint accepts a single parameter: the shortened URL. Users must provide this URL in the request body to receive the corresponding unshortened URL.
Users can check the "status" field to determine if the unshortening was successful. If true, they can use the "originUrl" for safe navigation or sharing. This helps in verifying links before clicking.
Typical use cases include verifying links in social media posts, enhancing security in messaging apps, and ensuring authenticity in emails. It helps users avoid phishing by revealing the true destination of shortened URLs.
Data accuracy is maintained by checking the validity of the shortened URL against known URL shortening services. The API ensures that only active and valid URLs are processed, reducing the risk of errors.
If users receive an error response (status: false), they should verify the shortened URL for correctness or check if it has expired. Users can also try different shortened URLs to ensure functionality.
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:
20,002ms
Service Level:
100%
Response Time:
119ms
Service Level:
100%
Response Time:
68ms
Service Level:
100%
Response Time:
16,754ms
Service Level:
100%
Response Time:
84ms
Service Level:
44%
Response Time:
496ms
Service Level:
100%
Response Time:
20,003ms
Service Level:
100%
Response Time:
254ms
Service Level:
100%
Response Time:
267ms
Service Level:
100%
Response Time:
876ms
Service Level:
100%
Response Time:
356ms
Service Level:
100%
Response Time:
1,507ms
Service Level:
100%
Response Time:
315ms
Service Level:
100%
Response Time:
287ms
Service Level:
100%
Response Time:
199ms
Service Level:
100%
Response Time:
57ms
Service Level:
100%
Response Time:
258ms
Service Level:
100%
Response Time:
187ms
Service Level:
100%
Response Time:
2,756ms
Service Level:
100%
Response Time:
2,741ms