Linklyhq Linkly API

Name: Linkly API
Brand: Linkly API
Availability: InStock

✓ Official Vendor SpecMarketingMarketing AutomationapiKey4 EndpointsREST

For Agents

Create and update short links and pull click analytics from Linkly so agents can run attribution, generate trackable URLs, and report on campaign traffic.

Install Jentic One Beta

Connect the Linkly API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Linkly API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Linkly API.

Create or update a short link with a destination URL and custom slug via POST /link

Retrieve click-level traffic data filtered by link, workspace, or date range via GET /clicks

Pull aggregated traffic counters for one or many links to power dashboards via GET /counters

GET STARTED

Start building with Linkly API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Linkly API for, with concrete tasks.

★ Campaign Link Generation

Generate trackable short URLs for paid and organic marketing campaigns with consistent branding and per-channel attribution. The Linkly API creates or updates a link in a single POST /link call, returning the short URL ready to embed in ads, emails, or social posts. Useful for marketing teams running dozens of campaigns who need every outbound URL to be measurable.

Call POST /link with url=https://example.com/landing and name=summer-promo, then return the short URL to the user.

Click Analytics Reporting

Pull click data for short links and produce attribution reports without scraping a dashboard. GET /clicks returns event-level traffic and GET /counters returns aggregated totals, so reports can show both raw events and roll-ups. Best for weekly marketing standups, attribution dashboards, and ad-spend reviews.

Call GET /counters for link_id=12345 over the last 7 days and summarise total clicks, then return the daily breakdown.

Traffic Data Export

Export the full traffic dataset for a Linkly workspace into a data warehouse or CSV for downstream analysis. GET /export returns historical traffic data in bulk, allowing teams to combine it with paid-ad spend, CRM events, or revenue data outside the Linkly UI. Most exports complete within minutes for typical workspace sizes.

Call GET /export for the workspace and store the returned traffic dataset in S3 for the analytics pipeline.

AI Agent Link Management

Let an AI agent generate and monitor short links on behalf of a marketing team without surfacing the api_key. Through Jentic, the agent searches for the Linkly create-link operation, loads the schema, and executes it with vault-issued credentials. The agent can then poll click counters and report results back in chat or to a CRM record.

Search Jentic for 'create a Linkly short link', load the schema, and execute POST /link for the user's campaign URL, then poll counters daily.

Key Endpoints

4 endpoints — linkly is a link shortening and analytics platform that lets teams create branded short urls and track click-level traffic data.

METHOD

PATH

DESCRIPTION

POST

/link

Create or update a short link

GET

/clicks

Retrieve click data for links

GET

/counters

Get aggregated traffic counters

GET

/export

Bulk export of traffic data

POST

/link

Create or update a short link

GET

/clicks

Retrieve click data for links

GET

/counters

Get aggregated traffic counters

GET

/export

Bulk export of traffic data

Why Jentic?

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

Credential isolation

Linkly api_key values are stored encrypted in the Jentic MAXsystem vault and injected as the api_key query parameter at execution time — agents receive scoped tokens and never see the raw key.

Intent-based discovery

Agents search by intent (e.g., 'create a short link with click tracking') and Jentic returns the matching Linkly operation with its input schema, so the agent can call POST /link without browsing the Linkly docs.

Time to first call

Direct Linkly integration: 2-4 hours for auth, link creation, and analytics polling. Through Jentic: under 15 minutes — search, load schema, execute.

FAQs

Specific to using Linkly API through Jentic.

What authentication does the Linkly API use?

The Linkly API uses API key authentication passed as the api_key query parameter on every request. Through Jentic, the api_key is stored encrypted in the MAXsystem vault and injected at execution time, so the agent never sees the raw secret.

Can I create branded short links with the Linkly API?

Yes. POST /link accepts a destination URL plus an optional name or custom slug, returning the branded short URL. You can also call the same endpoint with an existing link id to update its destination, which is useful for swapping out a campaign target without changing the published short URL.

What are the rate limits for the Linkly API?

Linkly enforces 20 requests per second on link management endpoints (POST /link) and 50 requests per hour on analytics endpoints (GET /clicks, GET /counters, GET /export). Build agents to batch analytics polling rather than calling /counters in tight loops.

How do I pull click analytics through Jentic?

Run pip install jentic, then search for 'get Linkly click counts' to find GET /counters or GET /clicks. Load the schema, supply a link_id and date range, and execute. Jentic returns the parsed click data ready for the agent to summarise.

Can the Linkly API export bulk traffic data?

Yes. GET /export returns the full traffic dataset for a workspace, suitable for loading into a warehouse or running offline attribution. Pair it with /counters for live dashboards and /export for periodic full snapshots.