Overview

Clico is a URL shortener API that lets you create short links programmatically using an API key for authentication. It provides a Swagger-documented REST interface, making it easy to explore available endpoints before writing any code. Once authenticated, you can shorten URLs and manage your links through straightforward API calls.

Beginner Tip

Check the Swagger UI documentation to explore all available endpoints and test them interactively before writing code. Include your API key in the request headers as specified in the docs.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

shortened URL
original URL
click count
creation date
Use case: Integrate url shortener service data into web and mobile applications

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative
{
  "id": "abc123",
  "short_url": "https://short.ly/abc123",
  "long_url": "https://example.com/very/long/url/path",
  "clicks": 1542,
  "created_at": "2025-01-10T14:30:00Z"
}

Field Reference

id Unique identifier for the created short link
shortUrl The generated short URL
originalUrl The original long URL that was provided
createdAt Timestamp of when the short link was created

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://cli.com/swagger-ui/";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

401 Unauthorized API key is missing or incorrectly passed in the request
Add your API key in the correct header or query parameter as documented in the Swagger UI
400 Bad Request The request body is missing required fields or has invalid data
Refer to the Swagger UI at the API URL to check the exact required fields for each endpoint
Connection refused The API base URL may have changed or the service is temporarily down
Check the Swagger config URL directly to verify the current API base URL and availability

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth API Key
HTTPS REQUIRED
CORS UNKNOWN
Category Url Shorteners
Difficulty Intermediate
Listing details not endpoint-verified

Related Tags

Similar APIs

View All →