Cutt.ly URL Shortener API

Name: Cutt.ly URL Shortener API API
Brand: Cutt.ly URL Shortener API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey1 EndpointsREST

For Agents

Shorten a URL into a cutt.ly link and retrieve click statistics for it via a single GET endpoint.

Quickstart

Get started with Cutt.ly URL Shortener API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"shorten a url with cutt.ly"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cutt.ly URL Shortener API API.

Shorten any long URL into a cutt.ly short link via GET /api.php

Request a custom slug for branded short links

Attach a name to a shortened link for later identification

Retrieve click statistics for an existing cutt.ly short link

Generate trackable links inline from an outbound email or SMS workflow

GET STARTED

Start building with Cutt.ly URL Shortener API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Cutt.ly URL Shortener API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Cutt.ly URL Shortener API, keeping it validated and agent-ready. Cutt.ly is a URL shortening service whose public API converts long URLs into short cutt.ly links and exposes click statistics for those links. The single endpoint is keyed by an account-level API key and accepts optional parameters for custom slugs and link names. It suits marketers and growth teams that want short branded links inside outbound emails, SMS, and social posts without standing up a self-hosted shortener.

Use Cases

Patterns agents use Cutt.ly URL Shortener API API for, with concrete tasks.

★ Trackable Links in Outbound Email

Marketing teams sending broadcast emails can call the Cutt.ly API at send time to convert each long destination URL into a short trackable link. The shortened link is dropped into the email body, and click counts are pulled back later for reporting. This avoids the need for a self-hosted link tracker and keeps the email payload small.

GET /api.php?key={apiKey}&short={longUrl}&name=campaign-2026-q2 and substitute the returned short link into the email body.

SMS Campaign Link Compression

SMS messages have a 160-character soft limit, so long marketing URLs eat into the message body and reduce conversion. Calling Cutt.ly before sending replaces the long URL with a short cutt.ly link that fits comfortably and remains trackable. The same call can request a branded slug so the recipient sees a consistent campaign code.

GET /api.php?key={apiKey}&short={longUrl}&user_domain=1 and use the response in the SMS body.

Click Reporting for a Campaign

After a campaign runs, the same /api.php endpoint can be called with the previously created short link reference to retrieve total clicks. Reporting jobs can iterate every named link from a campaign and roll the counts into a dashboard. This keeps marketing reporting honest without paying for an enterprise-tier tracker.

GET /api.php?key={apiKey}&stats={shortLinkId} for each campaign link and aggregate the click counts.

AI Agent Generating Short Links Inline

An AI agent drafting marketing emails, social posts, or SMS messages can call Cutt.ly through Jentic to produce a trackable short URL before the message is dispatched. Jentic isolates the API key so the agent never holds it in context and discovers the operation by intent. This is a small but useful tool for content-generating agents that need consistent tracking.

Search Jentic for 'shorten a url with cutt.ly', load the GET /api.php schema, and execute with the long URL and an optional name.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for cutt.

METHOD

PATH

DESCRIPTION

GET

/api.php

Shorten a URL or retrieve click stats

GET

/api.php

Shorten a URL or retrieve click stats

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Cutt.ly API key is stored in the Jentic vault and added as the key query parameter at execution time. The agent never holds the raw key in its context.

Intent-based discovery

Agents search by intent (e.g., 'shorten a url') and Jentic returns the matching Cutt.ly operation with its input schema, so the agent can call /api.php without reading the docs.

Time to first call

Direct Cutt.ly integration: under a day, since the API is a single GET. Through Jentic: a few minutes to search, load, and execute the first shorten call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Bitly API

Mature URL shortener with deeper analytics and a Bitlinks data model

Choose Bitly when richer analytics, click attribution, and team management are needed; choose Cutt.ly for a lightweight single-call shortener.

Alternative

Rebrandly API

Branded short links with custom domains and link management

Pick Rebrandly when the team needs custom domains and a full link management UI; pick Cutt.ly for free, fast, single-endpoint shortening.

Alternative

TinyURL API

Free URL shortener with a simple HTTP API

Pick TinyURL for the simplest free shortener; pick Cutt.ly when you also want click statistics from the same vendor.

FAQs

Specific to using Cutt.ly URL Shortener API API through Jentic.

Why is there no official OpenAPI spec for Cutt.ly URL Shortener API?

Cutt.ly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cutt.ly URL Shortener API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Cutt.ly API use?

Cutt.ly uses an API key passed as the key query parameter on GET /api.php. There is no header-based auth and no OAuth flow. When called through Jentic, the API key is held in the vault and added to the request at execution time.

Can I request a custom slug with the Cutt.ly API?

Yes. Pass the optional name parameter on GET /api.php with the desired slug. If the slug is already in use, Cutt.ly returns an error code in the JSON response, so the integration should retry with an alternative.

What are the rate limits for the Cutt.ly API?

Cutt.ly does not document a strict public rate limit. Free accounts are subject to soft limits that scale with the plan tier. For bulk shortening jobs, batch calls and back off on error responses rather than retrying tightly.

How do I shorten a URL through Jentic?

Search Jentic for 'shorten a url with cutt.ly', load the GET /api.php schema, and execute with the long URL in the short parameter. Jentic appends the API key from the vault.

Can I retrieve click statistics for a cutt.ly link?

Yes. The same /api.php endpoint accepts a stats parameter that returns click counts and metadata for a previously created short link. Pair this with the name you set at shorten time so reporting jobs can correlate links to campaigns.