Abgl Link AB.GL API

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.