Url Redirects

Name: Url Redirects API
Brand: Url Redirects
Availability: InStock

✓ Official Vendor SpecMarketingContent Managementoauth2, apiKey5 EndpointsREST

For Agents

Create, list, update, and delete URL redirects on HubSpot-hosted sites. Useful for agents handling site migrations, link maintenance, and SEO redirect rules.

Quickstart

Get started with Url Redirects in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a HubSpot URL redirect"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Url Redirects API.

List all current URL redirects with paging support

Create a new redirect from a routePrefix to a destination URL

Retrieve a specific redirect rule by its urlRedirectId

Update the destination, precedence, or match type of a redirect

Delete a redirect rule when its source path is retired

GET STARTED

Start building with Url Redirects API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Url Redirects API for, with concrete tasks.

★ Site Migration Redirect Mapping

When migrating content into HubSpot or restructuring an existing HubSpot site, the URL Redirects API lets an agent create 301 redirects for every legacy path so SEO equity and inbound links survive the move. Each call to POST /cms/v3/url-redirects/ accepts source path, destination, precedence, and redirect type.

Read a CSV of legacy-to-new URL pairs and POST /cms/v3/url-redirects/ for each row with redirectStyle 301 and the target path.

Broken Link Maintenance

List existing redirects via GET /cms/v3/url-redirects/, identify rules whose destination now returns a 404, and update or delete them. This keeps the redirect ruleset clean and avoids redirect chains that hurt page load and crawl budgets.

GET /cms/v3/url-redirects/ paginated, check each destination URL with HEAD requests, and PATCH /cms/v3/url-redirects/{urlRedirectId} or DELETE for any redirect whose target is dead.

Campaign Vanity URL Provisioning

Create short, memorable redirect rules pointing campaign vanity paths to long landing page URLs. The Redirects API supports flexible match types, so an agent can spin up a vanity URL per campaign as part of a marketing automation workflow.

POST /cms/v3/url-redirects/ with routePrefix `/spring-sale` and destination set to the full sale landing page URL.

Agent-Managed SEO Hygiene

Give an SEO agent the ability to inspect and maintain HubSpot redirects through Jentic. The agent searches by intent for the right Redirects operation, loads the schema, and executes — no HubSpot-specific code in the agent. Jentic isolates the HubSpot token from the agent's reasoning context.

Use Jentic search 'create a HubSpot URL redirect', load the POST /cms/v3/url-redirects/ schema, and execute with source and destination URLs from the SEO ticket.

Key Endpoints

5 endpoints — the hubspot url redirects api manages 301 and 302 redirects on hubspot-hosted cms sites.

METHOD

PATH

DESCRIPTION

GET

/cms/v3/url-redirects/

List current redirects

POST

/cms/v3/url-redirects/

Create a redirect

GET

/cms/v3/url-redirects/{urlRedirectId}

Get details for a redirect

PATCH

/cms/v3/url-redirects/{urlRedirectId}

Update a redirect

DELETE

/cms/v3/url-redirects/{urlRedirectId}

Delete a redirect

GET

/cms/v3/url-redirects/

List current redirects

POST

/cms/v3/url-redirects/

Create a redirect

GET

/cms/v3/url-redirects/{urlRedirectId}

Get details for a redirect

PATCH

/cms/v3/url-redirects/{urlRedirectId}

Update a redirect

DELETE

/cms/v3/url-redirects/{urlRedirectId}

Delete a redirect

Why though Jentic?

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

Credential isolation

HubSpot tokens for the URL Redirects API are stored encrypted in the Jentic vault. The agent receives a scoped execution token — the raw OAuth or private app token never enters the prompt.

Intent-based discovery

Agents search Jentic with intents such as 'create a 301 redirect' and Jentic returns the matching URL Redirects operation with its input schema, so the agent calls the right endpoint without browsing HubSpot docs.

Time to first call

Direct integration with HubSpot URL Redirects, including auth and pagination, takes about half a day. Through Jentic: under 20 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot CMS Pages

Manage the pages whose URLs are being redirected to or from.

Use CMS-pages when the agent needs to confirm a destination page exists before creating a redirect to it.

Complementary

HubSpot CMS Domains

Manage primary and secondary domains served by HubSpot CMS.

Pick CMS-domains when the agent needs to verify a domain is connected before configuring redirects on it.

Complementary

HubSpot CMS Blog Posts

Inspect blog post URLs that may need redirects after slug changes.

Use CMS-posts when an agent must detect blog URL changes and create matching redirects.

FAQs

Specific to using Url Redirects API through Jentic.

What authentication does the HubSpot URL Redirects API use?

OAuth 2.0 authorization code flow or a private app token in the `private-app-legacy` header. Through Jentic, credentials are stored encrypted and the agent only ever sees a scoped execution token.

Can I create a 301 redirect with the URL Redirects API?

Yes. POST /cms/v3/url-redirects/ accepts a `redirectStyle` field — set it to 301 for permanent redirects or 302 for temporary, along with `routePrefix` (source) and `destination` URL.

What are the rate limits for the URL Redirects API?

Standard HubSpot CMS API limits apply — roughly 100 requests per 10 seconds per OAuth app, with daily caps of 250,000 on most paid tiers. Throttle bulk redirect imports to stay within those limits.

How do I bulk-create redirects after a migration through Jentic?

Search Jentic for `create a URL redirect`, load the POST /cms/v3/url-redirects/ schema, and call execute in a loop over your migration mapping. Install with `pip install jentic` and use your `JENTIC_AGENT_API_KEY` for auth.

Does the URL Redirects API support pattern matching?

Yes. Each redirect record has a `precedence` and `matchType` field that supports exact-match and prefix-style routing, controlled via the create and PATCH endpoints.