Rebrandly API

Name: Rebrandly API
Brand: Rebrandly API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey16 EndpointsREST

Install Jentic One Beta

Connect the Rebrandly API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rebrandly 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 Rebrandly API.

Create a new link

Get a list of links

Delete multiple links in bulk

Update a specific link

GET STARTED

Start building with Rebrandly API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically create a new link, get a list of links. Covers 16 operations with apiKey authentication.

Use for: I need to a new link, I want to a list of links, Search for multiple links in bulk, Find all a specific link

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Use Cases

Patterns agents use Rebrandly API for, with concrete tasks.

★ Developer Tools Operations

Use the Rebrandly API to perform developer tools operations programmatically. The API provides 16 endpoints covering core functionality including create a new link, get a list of links, delete multiple links in bulk.

Call POST /v1/links to create a new link

Automated v1 Management

Automate v1 operations by combining multiple Rebrandly API endpoints. Agents can get a list of links and then delete multiple links in bulk in a single workflow.

Call GET /v1/links to get a list of links, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Rebrandly API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'create a new link', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

16 endpoints — url shortening and branded link management api.

METHOD

PATH

DESCRIPTION

POST

/v1/links

Create a new link

GET

/v1/links

Get a list of links

DELETE

/v1/links

Delete multiple links in bulk

POST

/v1/links/{id}

Update a specific link

GET

/v1/links/{id}

Get details about a specific link

DELETE

/v1/links/{id}

Delete a specific link

GET

/v1/links/count

Get count of links with filtering

GET

/v1/domains

Get domains shared in workspace

POST

/v1/links

Create a new link

GET

/v1/links

Get a list of links

DELETE

/v1/links

Delete multiple links in bulk

POST

/v1/links/{id}

Update a specific link

GET

/v1/links/{id}

Get details about a specific link

DELETE

Why Jentic?

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

Credential isolation

Your Rebrandly 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.

Intent-based discovery

Agents search Jentic by intent such as 'create a branded short link' or 'list domains', and Jentic returns the matching Rebrandly operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Rebrandly API through Jentic.

What authentication does the Rebrandly API use?

The Rebrandly API uses an API key passed in the `apikey` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create a new link with the Rebrandly API?

Yes. Use the POST /v1/links endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Rebrandly API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a new link through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new link'. Jentic returns the matching Rebrandly API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Rebrandly API have?

The Rebrandly API exposes 16 endpoints covering v1 operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Rebrandly operations and credentials the agent can use. Because Rebrandly puts the link id in the URL path at /v1/links/{id}, a rule can pin the agent to specific branded links and to your workspace domains from GET /v1/domains. You choose the operations it may call, so creating links with POST /v1/links or deleting them with DELETE /v1/links is only available if you allow it.