---
title: "Authorize or re-authorize a connection"
url: "https://docs.unified.to/unified/integration/Authorize_or_re-authorize_a_connection"
description: "Authorize or re-authorize a connection with Unified's Integration API (GET /unified/integration/auth/{workspace_id}/{integration_type}). Filter by success_redirect, failure_redirect and state."
---
# Authorize or re-authorize a connection

 GET/unified/integration/auth/{workspace\_id}/{integration\_type} NO AUTH NEEDED

Returns an authorization URL for the specified integration. After successful authorization, a new connection is created unless connection\_id and reauth\_token are provided, in which case the existing connection is updated in place.

## Parameters

**success\_redirect**string 

The URL where you want the user to be redirect to after a successful authorization. The connection ID will be appended with (id=<connectionId>) to this URL, as will the state that was provided.

**failure\_redirect**string 

The URL where you want the user to be redirect to after an unsuccessful authentication. An "error" variable will be appended.

**state**string 

Extra state to send back to your success URL

**external\_xref**string 

Your user identifier to associate with the new Integration

**scopes**string array 

**redirect**boolean 

**env**string  default=Production

**lang**string 

Language: en, fr, es, it, pt, zh, hi

**subdomain**string 

Optional tenant domain or subdomain for integrations that require it to build the authorize, token, or API URL. Depending on the integration, this may be a bare subdomain or a full domain/URL.

**region**string 

Optional region index (into the integration api.urls array) selected by the end-user. Set automatically by the auth widget when the workspace integration has prompt\_region=true.

**connection\_id**string 

Existing connection ID to re-authorize in place instead of creating a duplicate. Requires reauth\_token.

**reauth\_token**string 

Single-use token from "Create a re-authorization token for a connection" (POST /unified/connection/{id}/reauth); required with connection\_id.

**workspace\_id**string  required 

The ID of the workspace

**integration\_type**string  required 

Type of the supported integration

## Returns

string

## Errors

 Errors return the HTTP status code and a JSON body with `statusCode`, `error` (the short label) and `message` (a human-readable detail). 

```json
{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too many requests to unified.to API; max requests per minute: N"
}
```

| Status | Error                 | Meaning                                           |
| ------ | --------------------- | ------------------------------------------------- |
| 400    | Bad Request           | The request was malformed or failed validation.   |
| 401    | Unauthorized          | The connection is likely broken; re-authorize it. |
| 403    | Forbidden             | The connection is missing permissions or scopes.  |
| 404    | Not Found             | The requested resource does not exist.            |
| 429    | Too Many Requests     | Rate limit exceeded (see the two sources below).  |
| 500    | Internal Server Error | An unexpected error occurred.                     |
| 501    | Not Implemented       | Not supported by this integration.                |

 Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message. 

### 429 Too Many Requests

A 429 has two possible sources:

* The integration's own rate limit, passed through.
* Unified's workspace limit: a rolling 60 seconds, set by plan, with the message `Too many requests to unified.to API; max requests per minute: N`.