---
title: "Create a Connect Token"
method: POST
path: "/auth/connect_token"
tags: ["Auth"]
---

# Create a Connect Token

`POST /auth/connect_token`

The Connect front-end component must be initialized with a Connect Token scoped to the user entering the *Connect* flow.

For new users, or users creating an additional utility credential, post with a unique `client_user_id` parameter. For users editing an existing utility credential, post with the `utility_credential_id` parameter corresponding to the utility credential to be updated. Make sure the `Authorization` header is set to `Bearer ${ACCESS_TOKEN}`.

Tokens expire after two hours.

## Headers

- `Arcadia-Version` string, required

## Request body

- object
  - `client_user_id` string — The unique identifier for your user. This parameter is required for users entering the Connect flow for the first time. Note either `client_user_id` or `utility_credential_id` must be supplied to the endpoint for all requests.
  - `utility_credential_id` integer — The id associated the utility credential to be updated. This parameter is required for users entering Connect to update an existing utility credential. Note either `client_user_id` or `utility_credential_id` must be supplied to the endpoint for all requests.

## Response `200`

Success

- ConnectUrlResponse
  - `connect_url` string, required — The url to be used for initializing standalone Connect.

## Other responses

- `401` — Unauthorized.
- `404` — Not Found
- `422` — Unprocessable Entity

---

[API](https://skmtc.dev/arcadia/apis/arcadia-api-reference.md) · [All operations](https://skmtc.dev/arcadia/apis/arcadia-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/arcadia/arcadia-api-reference/revisions/468f1c903722/schema)