AB.GL API

Name: AB.GL API API
Brand: AB.GL API
Availability: InStock

★ Only Publicly Available SpecMarketingMarketing AutomationapiKey4 EndpointsREST

For Agents

Create, list, retrieve, and delete shortened links via an API-key-protected REST surface. Use it to programmatically generate tracking links for campaigns and notifications.

Quickstart

Get started with AB.GL 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"

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

Capabilities

What an agent can do with AB.GL API API.

Shorten a long URL into an AB.GL link with optional metadata

List existing shortened links for the authenticated account

Look up the destination and metadata of a single short link by ID

Delete a short link to retire a campaign URL

Use Cases

GET STARTED

Start building with AB.GL API API

Explore with Jentic

View OpenAPI Spec

Use for: I need to shorten a long campaign URL, List all the short links I have created, Get the destination URL behind a short link ID, Delete a short link that is no longer needed

Not supported: Does not handle click analytics, branded short domains, or QR-code generation — use for basic URL shortening and link CRUD only.

Jentic publishes the only available OpenAPI specification for AB.GL API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AB.GL API, keeping it validated and agent-ready. AB.GL is a link management and URL shortening service with a small REST surface for creating and listing short links and deleting them when they are no longer needed. The four endpoints cover list, create, retrieve, and delete on the /links resource, gated by a single API-key header. It is suited to teams that want shortened tracking links without taking on a heavier marketing automation stack.

★ Campaign Link Generation

Marketing teams generate one short link per campaign, channel, or audience so they can track click counts cleanly. POST /links creates the short link from the long destination and returns the AB.GL URL ready to drop into emails, SMS, and social posts. The flat surface keeps integration cheap when link shortening is one step in a larger send pipeline.

Shorten https://example.com/promo?utm_source=newsletter and return the AB.GL short URL

Link Inventory Audit

Compliance and operations occasionally need a list of all live short links to retire stale destinations or rotate broken redirects. GET /links returns the inventory and GET /links/{id} fetches the underlying destination for any single entry, so an audit script can walk the list and check each target.

List every short link, then retrieve the destination for each and flag any pointing at example-old.com

Link Retirement

When a campaign ends, leaving stale shortened links live is a leak risk. DELETE /links/{id} retires the link so subsequent visits no longer redirect. This pairs naturally with the inventory audit flow to clean up at scale.

Delete short link ID 9821 and confirm the response is successful

Agent-Driven Link Shortening via Jentic

AI agents handling messaging or marketing tasks often need a clean short link before posting. Through Jentic, an agent searches by intent, loads POST /links, and executes the call with the AB.GL key from the Jentic vault. The shortened URL feeds directly into the next agent step (compose email, send SMS, post update).

Search Jentic for 'shorten a URL', load the AB.GL schema, and execute the shorten call before passing the result to the email send step

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for ab.

METHOD

PATH

DESCRIPTION

POST

/links

Create a shortened link

GET

/links

List shortened links

GET

/links/{id}

Get link details

DELETE

/links/{id}

Delete a link

POST

/links

Create a shortened link

GET

/links

List shortened links

GET

/links/{id}

Get link details

DELETE

/links/{id}

Delete a link

Why though Jentic?

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

Credential isolation

AB.GL API keys are stored encrypted in the Jentic vault. Agents call operations by ID and Jentic injects the apiKey header at execution time, so the raw key never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'shorten a URL') and Jentic returns POST /links with its input schema, so the agent can call the right endpoint without browsing AB.GL docs.

Time to first call

Direct integration: a few hours to wire up auth, request, and response handling. Through Jentic: minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Bitly

Bitly's URL shortening platform with click analytics and branded domains.

Choose Bitly when click analytics, branded short domains, or QR codes are needed; pick AB.GL for a lighter shorten-and-store surface.

Alternative

Rebrandly

Rebrandly's branded link management API with custom domains and tagging.

Pick Rebrandly when branded domains and team workspaces matter.

Alternative

TinyURL

TinyURL's API for shortening and tracking links.

Use TinyURL when an extremely simple shortener is sufficient and brand customisation is not required.

FAQs

Specific to using AB.GL API API through Jentic.

Why is there no official OpenAPI spec for AB.GL API?

AB.GL publishes a docs page but not a discoverable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AB.GL 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 AB.GL API use?

The API uses an API key passed as a header (apiKey scheme). Through Jentic, the key is stored encrypted in the Jentic vault and added to the request at execution time, so the agent never receives the raw key.

Can I create short links with the AB.GL API?

Yes. POST /links accepts the long URL and returns the shortened AB.GL link. Use GET /links to list existing links, GET /links/{id} to retrieve a single one, and DELETE /links/{id} to retire it.

How do I shorten a URL through Jentic?

Search Jentic for 'shorten a URL' to find POST /links, load the schema, and execute the call with the long destination. Jentic injects the AB.GL API key from the vault and returns the short URL ready to use in the next agent step.

What are the rate limits for the AB.GL API?

The OpenAPI spec does not document explicit rate limits. Treat the link surface as low-throughput tooling: serialize bursts and retry with backoff on 429 or 5xx responses. Confirm production limits with AB.GL support before bulk shortening.

Does the AB.GL API support click analytics?

The four documented endpoints cover create, list, retrieve, and delete on /links and do not expose click metrics directly. For analytics, capture click events at the destination (UTMs in the long URL) or pair with a dedicated analytics API.