canonical: https://jentic.com/apis/cutt.ly/cuttly

# Cutt.ly Team API

Jentic publishes the only available OpenAPI specification for Cutt.ly Team API, keeping it validated and agent-ready. Cutt.ly Team is a URL shortener built for marketing and growth teams, with custom-domain support, A/B testing, mobile deep linking, and click analytics. The Team API exposes a single endpoint that handles shortening on behalf of an authenticated team account, including custom slug, branded domain, and tracking parameters in one call.

## For AI agents

Shorten URLs on a Cutt.ly team account with optional custom slugs, branded domains, and tracking metadata in a single call.

## Scope

Does not handle email delivery, ad campaign management, or full marketing automation - use for shortening and branding outbound URLs on a Cutt.ly team account only.

## Capabilities

- Shorten a long URL into a Cutt.ly short link via GET /index.php
- Apply a custom slug to make the short link memorable for campaigns
- Route the short link through a branded custom domain attached to the team
- Tag short links with campaign metadata for downstream click analytics
- Return existing short link metadata when the same URL is reshortened
- Operate against a Team-tier account so links are owned by the team workspace

## Use cases

### Branded short links for marketing campaigns

Turn a long campaign destination URL into a short, branded link routed through your custom domain. Marketing teams use the Cutt.ly Team API to mass-generate links for paid ads, newsletters, and social posts so click data rolls up to the team workspace and reports can be filtered by campaign tag.

Example prompt: Shorten https://example.com/landing/spring-sale on the team's custom domain with the slug 'spring2026'.

### Outbound email link tracking

Generate a unique trackable short URL per recipient or per email batch before send. The single GET endpoint accepts the destination URL plus team API key and returns a Cutt.ly short link, which downstream tooling can stamp into the email body to attribute clicks back to a campaign.

Example prompt: Create one short URL per row in the recipient CSV by calling GET /index.php for each long URL.

### Bulk migration to a new short-link domain

Re-shorten an existing list of campaign URLs onto a freshly attached custom domain. The Team API processes one URL per call, so a script iterates the source list, calls the endpoint, and writes the new short link back to the campaign record.

Example prompt: Iterate 500 campaign URLs, call GET /index.php for each, and store the returned short URL keyed by source URL.

### AI agent link shortener via Jentic

Give an AI agent a tool to produce short, trackable links inside its workflow. The agent searches Jentic for 'shorten a URL', loads the schema, and executes the call without holding the API key. This avoids stuffing the team key into prompt context.

Example prompt: Through Jentic, call GET /index.php with the destination URL and return the short URL plus tracking slug.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/index.php` | Shorten a URL on the authenticated team account |

## Key resources

- **Links** — Single endpoint to shorten a URL, optionally with a custom slug and branded domain

## Why Jentic

- **Setup:** Wiring the Cutt.ly Team API by hand means provisioning a team key, passing it and the target URL as query parameters on the single index.php endpoint, and parsing its response yourself. Through Jentic you install once, import the Cutt.ly Team API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Cutt.ly Team API exposes a single operation that takes its target URL as a parameter rather than a resource id in the URL path, so scope the agent to that shortening operation. That is the only surface it can reach on the team account.
- **Credential handling:** Your Cutt.ly Team API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'shorten and brand a URL', and Jentic returns the Cutt.ly Team operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Bitly** — Larger commercial URL shortener with broader analytics and integrations
- **Rebrandly** — Branded URL shortener with strong custom-domain workflows
- **TinyURL** — Long-running general-purpose URL shortener

## FAQ

### Why is there no official OpenAPI spec for Cutt.ly Team 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 Team via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Cutt.ly Team API use?

An API key passed in the X-API-Key header. Through Jentic, the key is stored in the encrypted vault and injected at execution time so it never enters the agent's prompt or log output.

### Can I shorten a URL with a custom slug on Cutt.ly Team?

Yes. GET /index.php accepts a custom name parameter alongside the destination URL, and Cutt.ly returns the short link on the team's account, optionally routed through a branded domain attached to the team.

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

Rate limits depend on your Cutt.ly Team plan rather than being declared in the spec. Handle 429 responses with backoff and check the Cutt.ly dashboard for your tier's per-minute quota before running bulk shortening jobs.

### Can I use a custom branded domain with this API?

Yes - if the team has a branded domain attached in the Cutt.ly dashboard, the shortening call can route the new short link through that domain rather than cutt.ly.

### How do I shorten a URL through Jentic?

Run pip install jentic, search for 'shorten a URL', load the GET /index.php schema, and execute with the destination URL. Jentic returns the short URL without exposing your team API key to the agent.

### Can I limit what my agent is allowed to do with the Cutt.ly Team API?

Yes. The Cutt.ly Team API exposes a single operation that shortens a URL passed as a parameter, so with your self-hosted Jentic One instance your own rules decide that this shortening call is the only thing the agent may invoke on the team account. Because the target URL is a parameter rather than a resource id in the path, that one operation is the entire surface the agent can reach. You also control which stored credential the agent may use, so its access to your Cutt.ly team account stays limited to link shortening.