curl --request POST \
  --url https://connect.tryverso.ai/api/connect-native \
  --header 'Content-Type: application/json' \
  --data '
{
  "action": "start",
  "token": "eyJhbGciOiJIUzI1NiJ9…",
  "device": {
    "platform": "ios",
    "osVersion": "17.5",
    "sdkVersion": "0.1.0",
    "model": "iPhone15,2",
    "appVersion": "3.2.0"
  }
}
'

{
  "captureNonce": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "clientSecret": "<string>",
  "provider": "chatgpt",
  "loginUrl": "https://chatgpt.com/auth/login",
  "cookieDomain": "chatgpt.com",
  "cookieName": "__Secure-next-auth.session-token",
  "sessionUrl": "https://chatgpt.com/api/auth/session",
  "expiresInSeconds": 3600
}

{
  "error": "Connection not found"
}

{
  "error": "Connection not found"
}

{
  "error": "Connection not found"
}

{
  "error": "Connection not found"
}

Endpoints

Native connect (mobile SDKs)

The two calls the mobile SDKs make to connect an account from inside an app. With an SDK you never call this endpoint yourself; it is documented for teams building on a platform without an SDK yet.

start verifies and consumes a connect link, creates the user record if needed, sends connect.started, and returns where to log in and which cookie to watch, plus a one-time capture credential (captureNonce and clientSecret, valid one hour).

capture hands the provider session read from the app’s WebView to Verso, which encrypts it, creates the connection (folding a previous connection of the same account into it), sends connection.created and starts the first sync. A capture sent before the provider session is usable (no accessToken yet) returns waiting; retry every few seconds.

No API key: the link’s token authenticates start, and the capture credential authenticates capture. The app and user come from the link, never from the request.

POST

api

connect-native

curl --request POST \
  --url https://connect.tryverso.ai/api/connect-native \
  --header 'Content-Type: application/json' \
  --data '
{
  "action": "start",
  "token": "eyJhbGciOiJIUzI1NiJ9…",
  "device": {
    "platform": "ios",
    "osVersion": "17.5",
    "sdkVersion": "0.1.0",
    "model": "iPhone15,2",
    "appVersion": "3.2.0"
  }
}
'

{
  "captureNonce": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "clientSecret": "<string>",
  "provider": "chatgpt",
  "loginUrl": "https://chatgpt.com/auth/login",
  "cookieDomain": "chatgpt.com",
  "cookieName": "__Secure-next-auth.session-token",
  "sessionUrl": "https://chatgpt.com/api/auth/session",
  "expiresInSeconds": 3600
}

{
  "error": "Connection not found"
}

{
  "error": "Connection not found"
}

{
  "error": "Connection not found"
}

{
  "error": "Connection not found"
}

Body

application/json

Option 1
Option 2

action

enum<string>

required

Available options:

start

token

string

required

The token of a connect link signed with signLink() (purpose: "connect").

device

object

What the SDK reports about the device. Stored with the connection for support; each value is truncated to 80 characters.

Show child attributes

Response

The start data, or the capture outcome (connected or waiting).

Option 1
Option 2
Option 3

captureNonce

string<uuid>

required

Identifies this connect attempt in capture.

clientSecret

string

required

Returned once. Proves in capture that the caller is the SDK instance that started the flow.

provider

string

required

Example:

"chatgpt"

Where to send the WebView.

Example:

"https://chatgpt.com/auth/login"

Example:

"chatgpt.com"

The session cookie to watch. The provider may split it into <cookieName>.0, <cookieName>.1, … chunks; concatenate them in order.

Example:

"__Secure-next-auth.session-token"

sessionUrl

string<uri>

required

Fetched from inside the WebView once the cookie is present; its JSON carries accessToken, user.id and user.email.

Example:

"https://chatgpt.com/api/auth/session"

expiresInSeconds

integer

required

Lifetime of the capture credential.

Example:

3600