---
title: "Redeem a chat connect link with a dashboard session"
method: POST
path: "/v1/integrations/connect/personal/redeem"
tags: ["integrations"]
---

# Redeem a chat connect link with a dashboard session

`POST /v1/integrations/connect/personal/redeem`

## Request

- Base URL: `https://api.patricia.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.patricia.app/v1/integrations/connect/personal/redeem`
- Auth: HTTP bearer

Spends the single-use connect token when the signed-in user owns the live chat identity of the person the link was made for. Invalid links and failed requester proofs return the generic 404, permitting chat sign-in fallback. A proved Billit requester receives a temporary 503 when the router is absent and the stored environment remains configured and permitted. That attempt does not spend the link.

## Request body

- SignedInRedeemBody: The single-use connect token the dashboard page read from the link's URL fragment.
  - `token` string, password, required

## Response `200`

Successful Response

- SignedInRedeemResponse: The provider's consent URL, where the browser goes next.
  - `connect_url` string, required

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden. Inspect response body `code` for the specific reason (for example: PERMISSION_DENIED, EMAIL_NOT_VERIFIED, TENANT_ACCESS_REQUIRED, ROLE_UNRESOLVED)
- `404`: Not found
- `409`: Conflict
- `422`: Validation error
- `503`: Proved member-connect attempt temporarily unavailable; the link was not spent.

---

[API](https://skmtc.dev/patricia/apis/patricia-api.md) · [All operations](https://skmtc.dev/patricia/apis/patricia-api/llms.txt) · [OpenAPI document](https://skmtc.dev/patricia/apis/patricia-api/revisions/0dfb44495ea1?raw)