Bitly API

What authentication does the Bitly API use?

Bitly v4 uses HTTP Bearer tokens. Each call sets Authorization: Bearer {token} on the request, using the generic access token you generate in your Bitly account settings under API. Bitly's authentication docs additionally describe OAuth 2.0 flows for acting on behalf of an end user, which neither this spec nor Bitly's own OpenAPI document declares, so treat OAuth as documented but undeclared. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so agents never hold the credential.

Can I shorten a URL with the Bitly API?

Yes. POST /v4/shorten accepts a long_url and an optional group_guid in the body and returns a Bitlink. Pass a domain field to mint the Bitlink on a branded short domain instead of bit.ly.

What are the rate limits for the Bitly API?

Bitly's rate-limits documentation describes two families. Platform limits apply to every account regardless of subscription plan: per-hour, per-minute and per-IP ceilings on each endpoint, with the per-minute limit set at one-tenth of the hourly one, plus a maximum of five concurrent connections from a single IP address. Plan limits are a monthly allowance, which Bitly's pricing page puts at 1,000 API requests per month on Free rising to 50,000 on Premium. Crossing either returns 429. Bitly's documented way to read your own current figures is the API itself, via GET /v4/organizations/{organization_guid}/plan_limits. Source: https://dev.bitly.com/docs/getting-started/rate-limits.

How do I get click analytics for a Bitlink through Jentic?

Install Jentic One (self-hosted), import Bitly from the API Directory, then search Jentic for 'get bitly click analytics', load the /v4/bitlinks/{bitlink}/clicks/summary operation, and execute with the Bitlink id. Jentic injects the Bearer token at execution time.

Can I generate a QR code from a Bitlink?

Yes. POST /v4/qr-codes creates a QR code from either an existing bitlink_id or a standalone long_url and returns the code's metadata, including its qr_code_id. Where the code points at a Bitlink, Bitly counts scans alongside clicks in that Bitlink's engagements endpoints, GET /v4/bitlinks/{bitlink}/engagements and /engagements/summary. Retrieving the rendered image is an operation in Bitly's own OpenAPI document rather than in this curated spec.

Can I limit what my agent is allowed to do with the Bitly API?

Yes. Because Jentic One is self-hosted, your own rules decide which Bitly operations and credentials your agent may use. Since Bitly puts the bitlink in the URL path, such as /v4/bitlinks/{bitlink}/clicks, you can pin the agent to a single link so it only reads that link's click summary and its country, device, and referrer breakdowns. You choose the operations it may call, so link creation with POST /v4/shorten stays off unless you explicitly add it.

Is there a Bitly MCP server?

Yes. Bitly runs a first-party MCP server at https://api-ssl.bitly.com/v4/mcp, documented in its own developer docs with OAuth 2.1 or a Bitly API token, and its pricing page lists Bitly MCP on every plan. You can also connect the Bitly API directly through Jentic: your agent gets this spec's full 45-endpoint surface without loading another server's tool definitions into its context, your Bitly token is stored encrypted by your own Jentic One instance and injected at call time rather than pasted into an MCP client config file, and your rules decide which operations the agent may call. Connecting the next API after Bitly is an import, not another install and authorisation setup.