Rebrandly API

Name: Rebrandly API
Brand: Rebrandly API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone13 EndpointsREST

For Agents

Programmatically post_v1_links, get_v1_links. Covers 13 operations.

Use for: I need to post_v1_links, I want to get_v1_links, Search for patch_v1_links, Find all get_v1_links_count

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Frebrandlyapi%2Frebrandlyapi" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frebrandlyapi%2Frebrandlyapi" | 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.

post_v1_links

get_v1_links

patch_v1_links

delete_v1_links_id

GET STARTED

Start building with Rebrandly API

Explore with Jentic

View OpenAPI Document

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 13 endpoints covering core functionality including post_v1_links, get_v1_links, patch_v1_links.

Call POST /v1/links to post_v1_links

Automated Branded Domains Management

Automate branded domains operations by combining multiple Rebrandly API endpoints. Agents can get_v1_links and then patch_v1_links in a single workflow.

Call GET /v1/links to get_v1_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 none tokens manually.

Search Jentic for 'post_v1_links', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

13 endpoints — best api to rebrand links.

METHOD

PATH

DESCRIPTION

POST

/v1/links

post_v1_links

GET

/v1/links

get_v1_links

PATCH

/v1/links

patch_v1_links

GET

/v1/links/count

get_v1_links_count

GET

/v1/links/{id}

get_v1_links_id

PATCH

/v1/links/{id}

patch_v1_links_id

DELETE

/v1/links/{id}

delete_v1_links_id

POST

/v1/links/{id}/tags

post_v1_links_id_tags

POST

/v1/links

post_v1_links

GET

/v1/links

get_v1_links

PATCH

/v1/links

patch_v1_links

GET

/v1/links/count

get_v1_links_count

GET

/v1/links/{id}

get_v1_links_id

PATCH

/v1/links/{id}

patch_v1_links_id

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring this Rebrandly API by hand means routing requests to its host and calling the versioned /v1 link paths yourself. Through Jentic you install once, import the Rebrandly API from the API Directory, and your agent calls it.

Permission scoping

Rebrandly puts the link id in the URL path (/v1/links/{id}), so a rule can pin your agent to specific branded links. You choose the operations it may call, so deleting a link or updating its tags is not included unless you add it.

Credential isolation

Any credential this Rebrandly API needs 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 'add tags to a link', and Jentic returns the matching Rebrandly operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 no authentication. 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 post_v1_links 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 post_v1_links through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'post_v1_links'. 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 13 endpoints covering branded domains, branded short links, count operations.