Dub API

Name: Dub API API
Brand: Dub API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer16 EndpointsREST

For Agents

Create branded short links, read click and conversion analytics, and manage marketing campaigns and partner programs through Dub.

Quickstart

Get started with Dub 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:
"create a branded short link"

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

Capabilities

What an agent can do with Dub API API.

Create short links with custom slugs and UTMs via POST /links

Read aggregated click, lead, and sale analytics via GET /analytics

Track lead and sale conversion events via POST /track/lead and POST /track/sale

Organise links with tags and folders via /tags and /folders

GET STARTED

Start building with Dub API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Dub API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Dub API, keeping it validated and agent-ready. Dub is link management infrastructure for marketing teams who need branded short links, conversion tracking, and partner programs. The API exposes 16 endpoints to create and manage short links, custom domains, tags, folders, analytics, events, partners, and workspaces. Authentication uses an OAuth-style bearer token, and the analytics surface returns aggregated click and conversion data sliced by attributes such as country, device, and referrer.

Use Cases

Patterns agents use Dub API API for, with concrete tasks.

★ Branded Short Links for Marketing Campaigns

Generate branded short links with UTMs for paid, social, and email campaigns. The agent calls POST /links with the destination, slug, and tags, then reads GET /analytics to roll up clicks by source. Branded short links reduce trust friction in social posts and let marketing teams retire links without breaking outbound creative.

POST /links with url='https://example.com/landing', domain='go.brand.com', and tags=['summer-2026'], then GET /analytics?linkId={id}&interval=7d for the click totals

Conversion Attribution for Referral Programs

Attribute leads and sales back to the referral link or partner that drove them. The agent fires POST /track/lead when a visitor signs up and POST /track/sale when they pay, passing the customer or external_id, so Dub joins the event chain back to the original click. This unlocks partner payouts and channel ROI reporting without building attribution from scratch.

On signup, POST /track/lead with clickId and external_id; on first paid invoice, POST /track/sale with the same external_id, amount, and currency

Partner Program Provisioning

Spin up partners for a referral program and issue them tracked links automatically. The agent calls POST /partners to add a partner record, then POST /links to mint a referral link tagged to that partner. Combined with the conversion tracking above, this drives a self-serve affiliate flow where each partner sees their attributed leads and sales.

POST /partners with the partner email and name, then POST /links with the destination URL and the partner's tenantId so referrals are attributed correctly

Agent-Driven Campaign Tooling via Jentic

Wire Dub into agent workflows that draft, publish, and measure campaigns. Through Jentic the agent searches by intent, loads the schema for /links or /analytics, and executes — the bearer token stays in the Jentic vault, not the agent's prompt context.

Search Jentic for 'create a branded short link', load the Dub /links schema, and execute with a destination URL and tags supplied by the parent campaign agent

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for dub api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/links

Create a short link

GET

/links

List links

GET

/analytics

Retrieve click and conversion analytics

POST

/track/lead

Track a lead conversion event

POST

/track/sale

Track a sale conversion event

POST

/domains

POST

/partners

Create a referral partner

POST

/links

Create a short link

GET

/links

List links

GET

/analytics

Retrieve click and conversion analytics

POST

/track/lead

Track a lead conversion event

POST

/track/sale

Track a sale conversion event

POST

Why though Jentic?

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

Credential isolation

Dub bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access at execution, so the raw token never enters the agent's prompt context.

Intent-based discovery

Agents search Jentic by intent (for example 'create a branded short link' or 'track a sale conversion') and Jentic returns the matching Dub operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Dub integration: 1-2 days for auth, link creation, and analytics polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Rebrandly API

Branded short links with deep custom domain support but a thinner conversion-tracking surface than Dub

Choose Rebrandly when the workflow is purely about branded redirects across many domains; choose Dub when conversion attribution and partner programs matter

Alternative

Short.io API

Short link platform with click analytics and webhook-driven workflows

Choose Short.io for simple branded redirects with webhooks; choose Dub when partner programs and event-level tracking are required

Alternative

TinyURL API

Lightweight URL shortener without the analytics or partner surface

Choose TinyURL when only a short URL is needed; choose Dub when reporting and conversion attribution are part of the workflow

FAQs

Specific to using Dub API API through Jentic.

Why is there no official OpenAPI spec for Dub API?

Dub does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Dub 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 Dub API use?

Dub uses an OAuth-style bearer token in the Authorization header. Through Jentic the token is stored in the encrypted vault and injected at execution, so the raw bearer never enters the agent's prompt.

Can I create branded short links with the Dub API?

Yes. POST /links accepts the destination URL plus optional domain, slug, and tags, and returns a short link record. Register the branded domain first via POST /domains.

How do I track conversions with the Dub API?

Fire POST /track/lead when a click becomes a signup, then POST /track/sale on the first paid event with the same external_id. Dub joins those calls to the originating click for attribution.

What are the rate limits for the Dub API?

The OpenAPI spec does not declare rate limits. Dub publishes per-plan limits in its dashboard; have your agent retry HTTP 429 with exponential backoff.

How do I read campaign analytics through Jentic?

Search Jentic for 'retrieve link analytics', load the schema for GET /analytics, and execute with a linkId and interval (for example 7d). Install with pip install jentic.

Does the Dub API support a referral partner program?

Yes. POST /partners creates a partner record and POST /links can mint a referral link attributed to that partner, which combines with /track/lead and /track/sale for end-to-end attribution.