Is Clico API down?
Current status, daily uptime history and troubleshooting for the Clico API (URL Shorteners).
Possibly: Clico's last check failed
Our latest daily check of Clico (Oct 24, 2026, 12:25 UTC) failed: its TLS certificate chain is incomplete. One failure can be a blip; the live check below tells you whether it's still failing.
Checking Clico now…
Sending a request from our server.
Clico API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- Its TLS certificate chain is incomplete
- Last up
- Not seen up yet
We check Clico's listed URL (https://cli.com/swagger-ui/index.html?configUrl=/v3/api-docs/swagger-config) once a day. History started when Clico was first checked, so new entries show fewer than 30 days.
Clico API not working for you?
- Clico needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- If calls fail only in the browser with a CORS error, Clico may not allow cross-origin requests. Call it from your server instead.
- If it works from one network but not another, check firewalls, VPNs and regional blocks.
- Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.
URL Shorteners APIs up at their last check
- 1
GoTiny API
Online · 1169 msA lightweight URL shortener, focused on ease-of-use for the developer and end-user.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
1pt API
Online · 1454 msA simple URL shortener. A free url shorteners API by 1pt-co.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
Git.io API
Online · 956 msDo you have a GitHub URL you’d like to shorten?
- No API key needed
- HTTPS
No authHTTPSCORS ? - 4
RedirHub API
Online · 1169 msURL redirect management with custom domains, HTTPS, analytics, and REST API.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS - 5
UrlBae API
Online · 682 msSimple and efficient short link creation.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS
Clico API status FAQ
Is Clico API down right now?
Our latest daily check of Clico (Oct 24, 2026, 12:25 UTC) failed: its TLS certificate chain is incomplete. One failure can be a blip; the live check below tells you whether it's still failing. This page also runs a live check from our server when you open it, so you can see whether Clico is responding at this moment.
How do you check whether Clico API is up?
Once a day our checker requests Clico's listed URL (https://cli.com/swagger-ui/index.html?configUrl=/v3/api-docs/swagger-config) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.
What can I use if Clico API is down?
Free URL Shorteners APIs that were up at their last check include GoTiny, 1pt, Git.io. See the full list of Clico alternatives for a comparison.
Why does Clico API work for others but not for me?
Clico needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, Clico may not allow cross-origin requests. Call it from your server instead.