# List all redirects for a help center

You can fetch a list of all URL redirects for a help center by making a GET request to `https://api.intercom.io/help_center/help_centers/{help_center_id}/redirects`.
Redirects are returned in descending order on the `updated_at` attribute.
Requires the `read_help_center_redirects_scope` OAuth scope. Set `Intercom-Version: Preview`.

Endpoint: GET /help_center/help_centers/{help_center_id}/redirects
Version: Preview
Security: bearerAuth

## Path parameters:

  - `help_center_id` (string, required)
    The unique identifier for the help center.

## Query parameters:

  - `page` (integer)
    The page of results to fetch. Defaults to the first page.

  - `per_page` (integer)
    The number of results to return per page. Defaults to 50, maximum 250.

## Header parameters:

  - `Intercom-Version` (string)

## Response 200 fields (application/json):

  - `type` (string)
    The type of the object - `list`.
    Enum: "list"

  - `pages` (object)
    Cursor-based pagination is a technique used in the Intercom API to navigate through large amounts of data.
A "cursor" or pointer is used to keep track of the current position in the result set, allowing the API to return the data in small chunks or "pages" as needed.

  - `pages.type` (string)
    the type of object `pages`.
    Enum: "pages"

  - `pages.page` (integer)
    The current page
    Example: 1

  - `pages.next` (object)

  - `pages.next.per_page` (integer)
    The number of results to fetch per page.
    Example: 2

  - `pages.next.starting_after` (string)
    The cursor to use in the next request to get the next page of results.
    Example: your-cursor-from-response

  - `pages.per_page` (integer)
    Number of results per page
    Example: 2

  - `pages.total_pages` (integer)
    Total number of pages
    Example: 13

  - `total_count` (integer)
    A count of the total number of redirects.
    Example: 1

  - `data` (array)
    An array of help center redirect objects.

  - `data.id` (string)
    The unique identifier for the redirect.
    Example: 26

  - `data.type` (string)
    The type of the object - `help_center_redirect`.
    Enum: "help_center_redirect"

  - `data.from_url` (string)
    The source URL that is redirected. An absolute URL within the help center's URL space.
    Example: http://help-center.test/lovelyhelpcenter/old-page

  - `data.locale` (string)
    The locale of the redirect's target. For article targets this is the bound translation's locale, which may differ from the requested locale if no translation exists in that locale.
    Example: en

  - `data.help_center_id` (string)
    The unique identifier for the help center the redirect belongs to.
    Example: 7

  - `data.target_type` (string)
    The type of the redirect target.
    Enum: "article", "collection"

  - `data.target_id` (string)
    The unique identifier of the target article or collection. For article targets this is the Article ID.
    Example: 11

  - `data.created_at` (integer)
    The time the redirect was created as a UTC Unix timestamp.
    Example: 1781619405

  - `data.updated_at` (integer)
    The time the redirect was last updated as a UTC Unix timestamp.
    Example: 1781619405

## Response 401 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: error.list

  - `request_id` (string)
    Example: f93ecfa8-d08a-4325-8694-89aeb89c8f85

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: unauthorized

  - `errors.message` (string)
    Optional. Human readable description of the error.
    Example: Access Token Invalid

  - `errors.field` (string)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: email

## Response 404 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: error.list

  - `request_id` (string)
    Example: f93ecfa8-d08a-4325-8694-89aeb89c8f85

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: unauthorized

  - `errors.message` (string)
    Optional. Human readable description of the error.
    Example: Access Token Invalid

  - `errors.field` (string)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: email