canonical: https://jentic.com/apis/abgl.link/abgl # Abgl Link AB.GL API 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. ## For AI 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. ## Scope Does not handle click analytics, branded short domains, or QR-code generation - use for basic URL shortening and link CRUD only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance. The shortened URL feeds directly into the next agent step (compose email, send SMS, post update). Example prompt: 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 | 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 | ## Key resources - **Links** — Create, list, retrieve, and delete shortened links ## Why Jentic - **Setup:** Wiring the AB.GL API by hand means managing its API key, targeting the api.abgl.link host, and shaping link create and lookup requests yourself. Through Jentic you install once, import the AB.GL API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** AB.GL puts the link id in the URL path (/links/{id}), so a rule can pin your agent to reading a specific link while leaving out deletion. You choose the operations it may call, so link deletion is not included unless you add it. - **Credential handling:** Your AB.GL 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 a URL' or 'look up a short link', and Jentic returns the matching AB.GL operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Bitly** — Bitly's URL shortening platform with click analytics and branded domains. - **Rebrandly** — Rebrandly's branded link management API with custom domains and tagging. - **TinyURL** — TinyURL's API for shortening and tracking links. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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 your Jentic One instance 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. ### Can I limit what my agent is allowed to do with the AB.GL API? Yes. Because Jentic One is self-hosted, your own rules decide which AB.GL operations and credentials your agent may use. You choose exactly which of the four endpoints it can call, so you can allow POST /links to create links and GET /links or GET /links/{id} to read them while leaving DELETE /links/{id} out entirely. Since the link id sits in the URL path, you can also pin a rule to a specific link, and link deletion is never available to the agent unless you explicitly add it.