---
title: "Register a redirect URI"
method: POST
path: "/connections/redirect-uris"
tags: ["dataConnectors"]
---

# Register a redirect URI

`POST /connections/redirect-uris`

This method registers a redirect URI so the [Authorize a connection](/v1.3/api-reference/data-connectors/authorize-a-connection) method accepts it.

## Headers

- `x-api-key` string, required

## Request body

- object
  - `redirect_uri` string, required — The redirect URI to register. Must use HTTPS, resolve to a public host, and contain no wildcards. Register it exactly as your application sends it, because the authorization flow requires an exact match.

## Response `201`

The redirect URI has been successfully registered.

- RedirectUri — An authorized redirect URI. During the authorization flow, the redirect URI you provide must match either a URI configured for you or one you registered through the [Register a redirect URI](/v1.3/api-reference/data-connectors/register-a-redirect-uri) method.
  - `_id` string — The unique identifier of the redirect URI.
  - `redirect_uri` string — The registered redirect URI.
  - `created_at` string, date-time — The date and time, in the RFC 3339 format ("YYYY-MM-DDTHH:mm:ssZ"), when the redirect URI was registered.

## Other responses

- `400` — The request has failed.
- `409` — The redirect URI is already registered.
- `422` — The redirect URI could not be registered. Either it failed validation (`redirect_uri_invalid`) because it must use HTTPS, resolve to a public host, and contain no wildcards, or you have reached the maximum number of registered redirect URIs (`redirect_uri_limit_exceeded`).

---

[API](https://skmtc.net/twelvelabs/apis/twelvelabs-api.md) · [All operations](https://skmtc.net/twelvelabs/apis/twelvelabs-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/twelvelabs/twelvelabs-api/revisions/5dbd6e8473c9/schema)