---
title: "Start authorization for a consent"
method: POST
path: "/connectivity/v2/consents/{consentId}/authorizations"
tags: ["Connectivity v2.Authorization", "BETA"]
---

# Start authorization for a consent

`POST /connectivity/v2/consents/{consentId}/authorizations`

## Path parameters

- `consentId` string, required

## Headers

- `Idempotency-Key` string, required

## Request body

- CreateAuthorizationRequest — Provide parameters used during this authorization attempt.
  - `appUri` string — The end user will be redirected to this URI after the authorization code has been delivered. This field is used for flows where we have third party redirects to financial institutions. There is a default value which is tink://open. It can be any type of URI (mobile deeplink, http address etc.)
  - `callbackUri` string — This URI will be used by the ASPSP to pass the authorization code. It corresponds to the redirect/callback URI in OAuth2/OpenId. This parameter is only applicable if you are a TPP.

## Response `202`

Authorization successfully started.

- CreateAuthorizationResponse
  - `authorization` Connectivity20v2Authorization — unresolved $ref

## Other responses

- `400` — Invalid input.
- `401` — Unauthorized request.
- `403` — Permission denied.
- `404` — Consent not found.
- `409` — Request retried while the original request is still being processed.
- `422` — Attempt to reuse an idempotency key with a different request payload.
- `500` — Internal server error.

---

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