redirection.io

Name: redirection.io API
Brand: Redirection
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey, bearer20 EndpointsREST

For Agents

Programmatically creates a new domain, retrieves the collection of the domains.. Covers 20 operations with apiKey, bearer authentication.

Install Jentic One Beta

Connect the redirection.io to your agent

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

Creates a new domain

Retrieves the collection of the domains.

Permanently deletes a domain

Deletes a Draft

GET STARTED

Start building with redirection.io API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use redirection.io API for, with concrete tasks.

★ Marketing Operations

Use the Redirection to perform marketing operations programmatically. The API provides 20 endpoints covering core functionality including creates a new domain, retrieves the collection of the domains., retrieves a projectdomain resource..

Call POST /domains to creates a new domain

Automated Rule Management

Automate rule operations by combining multiple Redirection endpoints. Agents can retrieves the collection of the domains. and then retrieves a projectdomain resource. in a single workflow.

Call GET /domains to retrieves the collection of the domains., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Redirection 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, bearer tokens manually.

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

Key Endpoints

20 endpoints — this is the documentation of the public api of [redirection.

METHOD

PATH

DESCRIPTION

POST

/domains

Creates a new domain

GET

/domains

Retrieves the collection of the domains.

GET

/domains/{id}

Retrieves a ProjectDomain resource.

DELETE

/domains/{id}

Permanently deletes a domain

GET

/drafts

Retrieves the collection of Draft rules

GET

/drafts/{id}

Retrieves a Draft resource.

DELETE

/drafts/{id}

Deletes a Draft

GET

/ips

Retrieves the collection of Ip resources.

POST

/domains

Creates a new domain

GET

/domains

Retrieves the collection of the domains.

GET

/domains/{id}

Retrieves a ProjectDomain resource.

DELETE

/domains/{id}

Permanently deletes a domain

GET

/drafts

Retrieves the collection of Draft rules

Why Jentic?

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

Credential isolation

Redirection apiKey, bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'creates a new domain') and Jentic returns the matching Redirection operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Redirection integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using redirection.io API through Jentic.

What authentication does the Redirection use?

The Redirection uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I creates a new domain with the Redirection?

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

What are the rate limits for the Redirection?

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 creates a new domain through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'creates a new domain'. Jentic returns the matching Redirection operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Redirection have?

The Redirection exposes 20 endpoints covering rule, rulemodel operations.

redirection.io

Connect the redirection.io to your agent

Capabilities

Start building with redirection.io API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs