Cutt.ly
Cutt.ly — free tier with API key
Cutt.ly exposes a free-tier JSON API. Register for an API key if required; we verified a public or demo endpoint.
GET https://cutt.ly/api/api.php
{
"auth": false,
"code": "4",
"message": "Invalid API key"
}curl "https://cutt.ly/api/api.php"const res = await fetch("https://cutt.ly/api/api.php");
const data = await res.json();
console.log(data);import requests
res = requests.get("https://cutt.ly/api/api.php")
print(res.json())THIS API IS DEAD — NOTHING TO RUN
/api/api.phpPROBEDCutt.ly — free tier with API key
/apiApi — documented GET route.
/api/1Api details by ID (example: 1).
/api?limit=10Api — documented GET route.
/api/search?q=testSearch by query parameters.
/api/api.php?key={{key}}&short=$url&name={{name}}&userDomain=1Api Php — documented GET route.
We probe a documented GET and expect 2xx JSON — full uptime and health score. Export includes every documented route below.
Stable. No schema drift observed since monitoring began — the response shape has not changed under our checks.
Cutt.ly: common questions
Is Cutt.ly free to use?
Yes — Cutt.ly is a free developer tools API. Free tier: Free tier — API key required. Whether the free tier allows commercial use is unclear — check the provider docs.
Does Cutt.ly need an API key?
Yes — Cutt.ly needs a free API key, which you pass on each request. Rate limits: Unpublished.
Can I call Cutt.ly from the browser?
Not directly — Cutt.ly doesn't send browser-friendly CORS headers, so call it from a server or proxy instead. Copy the curl or Python snippet on this page to get started.
Is Cutt.ly up right now?
As of our last scheduled check, Cutt.ly is dead. We re-probe it every sweep — the status badge and uptime chart above always show the latest.