TinyURL API: Features, Limits, and Better Options for Developers

Four labeled dispensers representing Bitly's products—landing pages, short links, QR Codes, and analytics—with a hand selecting the QR Code option.

Searching for information on the TinyURL API usually means you need programmatic URL shortening and want to know whether TinyURL’s endpoints, tokens, and plan limits fit the job. Pick a link shortener API that only covers the first call, and you may need to rebuild it once branding and reporting requests arrive.

This guide is for app developers and marketing ops teams wiring short links into SMS, SaaS, or automation tools. When links are scattered across scripts, campaigns, and QR Codes, it’s hard to tell which ones drive results. You’ll leave knowing core TinyURL API capabilities, how its token permissions work, and when Bitly is the stronger production choice.

We’ll cover capabilities, constraints, and comparison criteria, then present a structured path with Bitly to branded links, analytics, and QR Codes.

Note: The brands and examples discussed below were found during our online research for this article. Plan details and limits are current as of October 2026.

Key Takeaways

  • TinyURL API lets authorized users create and manage short links through HTTP endpoints and token-based authentication.
  • Free-plan API access exists, with tokens that can create links, update aliases, and archive. Destination changes, deletes, analytics, raw analytics logs, bulk requests, and expiration controls require a paid plan.
  • Production teams should evaluate branding, analytics depth, QR Code support, bulk creation, rate limits, integrations, and uptime, not just the first successful shorten call.
  • Bitly’s API supports branded domains, custom back-halves, click analytics, QR Code creation, and plan-based API request limits on one platform.
  • Start in Bitly when you need marketer-ready workflows plus developer endpoints, then scale your plan for more monthly links and API requests.

What the TinyURL API is and who it serves

A URL shortener API is a set of HTTP endpoints that lets software create, customize, and track short links without manual dashboard work. The TinyURL API is a programmatic interface for creating and managing TinyURL short links without relying solely on the company’s web UI.

TinyURL’s API documentation provides an interactive OpenAPI reference for endpoints hosted at api.tinyurl.com. The API is only available to authorized users, who authenticate with an API token sent in an Authorization: Bearer header or as an api_token URL parameter. Community libraries, such as this .NET client for the TinyURL API on GitHub, wrap the same endpoints.

Most people searching for TinyURL API documentation want to add shortening to a script, internal tool, or lightweight app. That work adds up: 69% of respondents spend 10 or more hours a week on API work, according to Postman’s 2025 State of the API report, which surveyed more than 5,700 developers and API professionals.

TinyURL’s public materials include an API reference plus short help center articles, so you still need to provide your own standard against which to measure what’s “good enough for production” in your workflow.

Core capabilities developers look up first

Developers usually check these TinyURL API capabilities first:

  • Creating short links programmatically through the POST /create endpoint.
  • Authenticating with an API token, often called an “API key” or “Bearer token” in community examples.
  • Updating aliases, archiving links, editing tags, changing destinations, or deleting links, depending on token permissions.
  • Pulling short link analytics, including raw logs, timelines, and location data.
  • Submitting batches of operations through the /bulk endpoint.
  • Importing the OpenAPI spec to generate a client library for your stack.

A typical TinyURL API example sends a POST request to /create with a Bearer token header and a JSON body whose url field holds the long URL. Optional fields include domain, alias, tags, expires_at, and description, though some require a paid plan, so it’s important to confirm current details in TinyURL’s API reference before you build.

TinyURL API authentication, tokens, and plan permissions

You authenticate TinyURL API calls with an account token, and permission scopes control which endpoints that token can call. TinyURL lets you create permission-specific tokens, like one that can only create links, and the permissions available depend on your plan.

According to TinyURL’s help center, the permissions break down like this:

  • Free plan: Create TinyURL, Update TinyURL (aliases), and Archive TinyURL.
  • Paid plans: Everything above, plus updates to tags and analytics settings, Change URL, Delete TinyURL, Use Analytics, Raw Analytics Logs, Use Bulk Requests, and Manage TinyURL Expiration.

Some tasks need combined permissions. A bulk job, for example, also needs permission for each operation inside it, such as create or delete.

You create a TinyURL API token under Profile → API in your account, according to TinyURL’s token guide. Name the token, grant only the permissions your use case needs, and copy it somewhere safe. You can edit a token’s permissions or delete it from the same page. If you lose a token or believe it was stolen, TinyURL’s docs say to remove it and create a new one. After you replace a token, update every system that used the old one.

Keep the token in the Authorization header and pass link data, like the long URL, in the request body. TinyURL also accepts the token as an api_token query parameter, but the header keeps it out of URLs. The create endpoint is api.tinyurl.com/create.

Bitly uses a similar Bearer pattern, with every v4 API call sending Authorization: Bearer {token} to https://api-ssl.bitly.com. Our authentication guide explains how to generate tokens. Most Bitly calls also act on behalf of a group, identified by a group_guid that you include in the request (see step 3 below).

Auth0’s OAuth 2.0 overview explains that an access token represents authorization to access resources on behalf of a user. The Bearer token specification from the Internet Engineering Task Force (IETF) defines how clients send access tokens as Bearer tokens in HTTP requests.

Features and limits that affect real projects

A successful shorten call is only the first requirement, because production quality depends on branding, measurement, automation, and enforceable limits. Here’s what teams usually hit next:

  • Custom domains and branded link presentation
  • Click analytics depth and exportability
  • QR Code generation in the same platform
  • Monthly API request ceilings and platform rate limits
  • Bulk or high-volume creation patterns
  • Security, reliability, and admin controls

Developer experience belongs on that list too. In the 2025 Stack Overflow Developer Survey, technical documentation was the most-used resource for learning to code, with nearly 68% of respondents reporting that they used documentation for learning in the past year.

On the TinyURL side, the API goes well beyond single create calls. Paid plans add branded domains, analytics endpoints, bulk requests, destination changes, and expiration controls. However, TinyURL’s API reference doesn’t include QR Code endpoints, webhooks, or published rate limits.

On the Bitly side, the API covers creation, customization, analytics, and QR Codes in one platform:

  • Create links with /v4/shorten, or customize them with /v4/bitlinks.
  • Publish branded links on custom domains with Growth tier plans and above, and add custom back-halves on any plan (Free tier includes three a month, and 1,000 API calls).
  • Pull click metrics through analytics endpoints, with analytics history ranging from 30 days on Core tier to two years on Enterprise.
  • Generate QR Codes and pull scan metrics through dedicated API endpoints.
  • Connect AI assistants through the Bitly MCP Server, available on every plan.
  • Receive real-time event notifications through webhooks on our Enterprise tier.

High-volume creation works differently on each platform. Bitly’s API creates links one call at a time; its batch support covers updates like archiving or retagging up to 100 links, not creation. Developers loop individual create calls within rate limits, and higher rate limits require an Enterprise plan. For one-off batches, the Bitly app accepts CSV or Excel uploads of up to 100 links each on our Growth tier and 3,000 on our Premium tier, with custom volumes available for Enterprise accounts. TinyURL, by contrast, offers a /bulk batch endpoint on paid plans.

Automation is where this setup pays off. Tiffany Travelute, Digital Product Manager at Pioneers, shared how Pioneers automates link work with Bitly’s integration and API through Make. The setup lets her team use Bitly without sharing direct account access.

TinyURL API and Bitly API comparison table

This table compares each capability using TinyURL and Bitly’s own documentation as of October 2026.

CapabilityTinyURL APIBitly API
Shorten via RESTPOST /create with a bearer token or api_token parameterPOST /v4/shorten, or /v4/bitlinks for titles, tags, and back-halves
Free-plan API accessYes: create, alias updates, and archivingYes: 1,000 requests a month, 5 links and 2 QR Codes
Branded domainsPaid plansGrowth tier plan and above
Custom back-halvesAliases on every planEvery plan (Free: 3 a month)
AnalyticsEight analytics endpoints, including raw logs, on paid plansClick and scan metrics APIs; history from 30 days (Core tier) to 2 years (Enterprise tier)
QR CodesIn the app, not the APICreate, update, and track scans via API and app
Bulk creation/bulk batch endpoint on paid plansOne link per API call; CSV or Excel upload in our app (Growth tier and above)
WebhooksNone in the API referenceAvailable on Enterprise tier
API request limitsNot published in the API reference1,000/month for Free tier → 50,000/month for Premium tier, with custom limits for Enterprise tier
Integrations / AISome third-party connectors, such as Pipedream and CometChat60+ native integrations; 3,400+ connected apps and workflows; Bitly MCP
Reliability signalNo uptime figure in the API reference99.99% uptime

Bitly’s monthly Link and QR Code counts also apply to anything you create through the API. Current plan counts are:

PlanAPI requests per monthShort links per monthQR Codes per month
Free1,00052
Core5,0001005
Growth25,00050010
Premium50,0003,000200
EnterpriseCustomCustomCustom

Size your plan by whichever count you’ll hit first. For most apps, that’s the link count, not API requests. Free tier suits testing, while steady production traffic fits Growth or Premium. If you need more than 3,000 links or 50,000 API requests a month, that signals an Enterprise conversation. You can check your current usage in Bitly under Settings → Billing & usage.

When Bitly is the stronger URL shortener API

Choose Bitly when short links are part of a measurable growth system rather than a one-off script. These use cases benefit most:

  • SMS and messaging links sent at volume
  • Sharing links generated inside SaaS products
  • Building marketing automation with UTM campaign tracking
  • Links, QR Codes, and landing pages managed under one vendor
  • AI-assisted workflows through Bitly MCP

For business teams that need a custom domain API, branded links, and reporting, we recommend Bitly as the default URL shortening API. With Bitly, you can create, customize, and control every touchpoint, including short links, QR Codes, and landing pages, in one place.

Bitly Analytics brings clicks, scans, and landing page views from every channel into one view, so teams can compare results across campaigns. Insights stay approachable for marketers and developers alike.

Our platform also works as a QR Code generation API. You can create Bitly QR Codes programmatically with the QR Code endpoint and track scans next to clicks on the same platform.

Bitly fits the tools you already use. Our Integrations Directory lists 60+ native integrations and 3,400+ connected apps and workflows, including customer relationship management (CRM) tools like Salesforce and HubSpot, commerce platforms like Shopify, and no-code automation tools. The developer solutions page explains the Bitly API for technical teams.

Our free plan offers 1,000 API requests, 5 links, and 2 QR Codes a month, providing the perfect zero-cost test environment for your team to use while building production-ready automations. For a broader look at the market, see our roundup of URL shortener APIs.

Create a Bitly account, generate an access token, then POST your long URL to Bitly’s shorten endpoint with Bearer auth. Follow these steps:

  1. Create or sign in to a Bitly account.
  2. Generate an access token under Settings → Developer → API.
  3. Send a POST request to https://api-ssl.bitly.com/v4/shorten with a JSON body that includes long_url and group_guid (we recommend always specifying a group), plus domain if you use a custom one.
  4. Read the returned link object and store the short link in your application.
  5. Move to /v4/bitlinks when you need titles, tags, custom back-halves (the keyword field), or richer customization.

Our API documentation covers setup, and the full API reference lists every endpoint and parameter. For custom back-halves and titles, follow the shorten and customize tutorial.

Bitly API example request

This cURL request shortens one link with the Bitly shorten URL API, using placeholder credentials:

curl -X POST “https://api-ssl.bitly.com/v4/shorten” \

  -H “Authorization: Bearer {YOUR_ACCESS_TOKEN}” \

  -H “Content-Type: application/json” \

  -d ‘{“long_url”: “https://example.com/long-page”, “domain”: “bit.ly”, “group_guid”: “{YOUR_GROUP_GUID}”}’


Bitly returns JSON with the short link in its link field; the short link redirects people to the long URL. The IETF’s HTTP semantics standard defines how permanent 301 and temporary 302 redirects differ for browsers and caches.

Rate limits and SDK options

Plan for rate limits from your first deployment. We enforce per-hour, per-minute, and per-IP limits on each endpoint. The per-minute limit is one-tenth of the hourly limit, and a single IP address can hold at most five concurrent connections. Bitly support lists the default at 1,000 links an hour on non-Enterprise plans and 10,000 on Enterprise; call GET /v4/user/platform_limits to see your account’s ceilings. Our rate limits guide has all the details.

Bitly returns a 429 with RATE_LIMIT_EXCEEDED when you pass rate limits, and API_USAGE_LIMIT_EXCEEDED when you reach your monthly plan limit. Handle them differently:

  • RATE_LIMIT_EXCEEDED: Retry with backoff (longer waits between each retry), since limits reset every minute and every hour.
  • API_USAGE_LIMIT_EXCEEDED: Stop retrying. Monthly limits reset on the first of the month, so upgrade your plan or wait.

Cache each short link and its long URL to avoid repeat requests; we recommend caching because its links don’t expire. If your team changes destinations with redirects, refresh the cached long URL when you do.

Teams that want generated software development kits (SDKs) can download our OpenAPI 3.0 specification and generate a client with OpenAPI tooling. We also offer official Android and iOS SDKs and an npm package.

Choose an API that can grow with your stack

The TinyURL API covers more than basic shortening: Paid plans add bulk requests, analytics, destination changes, and branded domains. Bitly pairs developer endpoints with branded links, analytics, QR Codes, integrations, MCP support, and enterprise-ready limits.

As your links spread across apps, messages, and print, scattered data makes it harder to measure results. Bitly is the marketing platform that helps businesses of all sizes see what’s working. Simply and clearly.

Start by testing our free API access. Then shortlist the endpoints your app needs, like shortening, custom back-half, metrics, and QR Codes, and size your plan by the links you’ll create each month. 

Ready to do more of what works with less user effort? Link your marketing. Get started building your API automation with Bitly today.

Frequently Asked Questions

Is there a TinyURL API?

Yes. TinyURL provides an API that allows authorized users to create and manage short links programmatically via documented HTTP endpoints and token-based authentication. Its API reference is published as an OpenAPI specification.

Can I use the TinyURL API on a free plan?

Yes. TinyURL’s help center confirms that Free Plan users can use the API, with tokens that can create links, update aliases, and archive. Paid plans unlock a wider permission set for actions like destination changes, deletes, analytics, bulk requests, and expiration management.

What should I look for in a URL shortener API?

Prioritize authentication model, branded domain support, analytics depth, QR Code support, bulk creation, documented rate limits, integrations, uptime, and long-term link management. Don’t judge an API only by whether a single shorten call works.

Generate a Bitly access token. Then send a POST request to https://api-ssl.bitly.com/v4/shorten with your long URL, your group_guid, and an Authorization: Bearer header. Bitly returns JSON that includes the short link.

How many Bitly API requests can I make each month?

Monthly API requests depend on your plan: Free tier includes 1,000 requests per month, Core 5,000, Growth 25,000, Premium 50,000, and Enterprise is custom. Your plan’s monthly link and QR Code assignments also apply to API-created links; the Free tier, for example, allows 5 links a month. Our API also enforces per-hour, per-minute, and per-IP rate limiting.

Does Bitly support custom domains through the API?

Yes. On Growth tier plans and above, you can set up a branded short domain and create links on it through Bitly’s link endpoints; GET /v4/bsds lists the domains you can use. Custom back-halves work on every plan, including Free.

Is Bitly a good alternative if I searched for TinyURL API?

Yes. If you need production branding, analytics, QR Codes, integrations, and clear scaling paths, Bitly is the stronger platform to build on. It still gives developers a full REST API and documentation hub.

Create a QR Code

This is a sample QR Code Note: This is a standard QR Code preview.