---
title: "Retrieve redirects"
method: GET
path: "/cms/url-redirects/2026-03"
tags: ["Basic"]
---

# Retrieve redirects

`GET /cms/url-redirects/2026-03`

Retrieve a list of URL redirects configured in your HubSpot account. This endpoint allows you to filter redirects based on their creation or update timestamps, and sort the results. It supports pagination and can include archived redirects if specified.

## Query parameters

- `after` string
- `archived` boolean
- `createdAfter` string, date-time
- `createdAt` string, date-time
- `createdBefore` string, date-time
- `limit` integer
- `sort` string[]
- `updatedAfter` string, date-time
- `updatedAt` string, date-time
- `updatedBefore` string, date-time

## Response `200`

successful operation

- CmsUrlRedirectsCollectionResponseWithTotalUrlMappingForwardPaging
  - `paging` ForwardPaging
    - `next` NextPage — Specifies the paging information needed to retrieve the next set of results in a paginated API response
      - `after` string, required — A paging cursor token for retrieving subsequent pages.
      - `link` string — A URL that can be used to retrieve the next page results.
  - `results` CmsUrlRedirectsUrlMapping[], required — An array of UrlMapping objects, each representing a specific URL mapping.
    - `created` string, date-time, required — The date and time when the URL mapping was initially created.
    - `destination` string, required — The destination URL, where the target URL should be redirected if it matches the `routePrefix`.
    - `id` string, required — The unique ID of this URL redirect.
    - `isMatchFullUrl` boolean, required — Whether the `routePrefix` should match on the entire URL, including the domain.
    - `isMatchQueryString` boolean, required — Whether the `routePrefix` should match on the entire URL path, including the query string.
    - `isOnlyAfterNotFound` boolean, required — Whether the URL redirect mapping should apply only if a live page on the URL isn't found. If False, the URL redirect mapping will take precedence over any existing page.
    - `isPattern` boolean, required — Whether the `routePrefix` should match based on pattern.
    - `isProtocolAgnostic` boolean, required — Whether the `routePrefix` should match both HTTP and HTTPS protocols.
    - `isTrailingSlashOptional` boolean, required — Whether a trailing slash will be ignored.
    - `precedence` integer, required — Used to prioritize URL redirection. If a given URL matches more than one redirect, the one with the **lower** precedence will be used.
    - `redirectStyle` integer, required — The type of redirect to create. Options include: 301 (permanent), 302 (temporary), or 305 (proxy). Find more details [here](https://knowledge.hubspot.com/cos-general/how-to-redirect-a-hubspot-page).
    - `routePrefix` string, required — The target incoming URL, path, or pattern to match for redirection.
    - `updated` string, date-time, required — The date and time when the URL mapping was last modified.
  - `total` integer, required — The total number of URL mappings available.

## Other responses

- `default` — An error occurred.

## Changes

> 14 revisions in range; 1 not diffed, 2 could not be searched.

- **2026-04-08** `b0d8bc008db9` — 1 info
  - api operation id `get-/cms/url-redirects/2026-03_/cms/url-redirects/v3` removed and replaced with `get-/cms/url-redirects/2026-03`
- **2026-03-30** `dc2fdad57f7f` — 1 info
  - api operation id `get-/cms/url-redirects/2026-03_/cms/url-redirects/2026-03` removed and replaced with `get-/cms/url-redirects/2026-03_/cms/url-redirects/v3`
- **2026-03-25** `62586336cea2` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/hubspot/apis/hubspot-api-specification/changes/cms/url-redirects/2026-03/get.md)

---

[API](https://skmtc.dev/hubspot/apis/hubspot-api-specification.md) · [All operations](https://skmtc.dev/hubspot/apis/hubspot-api-specification/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/hubspot/hubspot-api-specification/revisions/f9c7181056c5/schema)