exchange-sso-token

import { Vercel } from "@vercel/sdk";

const vercel = new Vercel();

async function run() {
  const result = await vercel.marketplace.exchangeSsoToken({
    code: "<value>",
    clientId: "<id>",
    clientSecret: "<value>",
  });

  console.log(result);
}

run();

{
  "id_token": "<string>",
  "access_token": "<string>",
  "token_type": "<string>"
}

authentication

SSO Token Exchange

During the autorization process, Vercel sends the user to the provider redirectLoginUrl, that includes the OAuth authorization code parameter. The provider then calls the SSO Token Exchange endpoint with the sent code and receives the OIDC token. They log the user in based on this token and redirects the user back to the Vercel account using deep-link parameters included the redirectLoginUrl. Providers should not persist the returned id_token in a database since the token will expire. See Authentication with SSO for more details.

POST

integrations

sso

token

exchange-sso-token

import { Vercel } from "@vercel/sdk";

const vercel = new Vercel();

async function run() {
  const result = await vercel.marketplace.exchangeSsoToken({
    code: "<value>",
    clientId: "<id>",
    clientSecret: "<value>",
  });

  console.log(result);
}

run();

{
  "id_token": "<string>",
  "access_token": "<string>",
  "token_type": "<string>"
}

Body

application/json

code

string

required

The sensitive code received from Vercel

client_id

string

required

The integration client id

client_secret

string

required

The integration client secret

state

string

The state received from the initialization request

redirect_uri

string

The integration redirect URI

grant_type

enum<string>

The grant type, when using x-www-form-urlencoded content type

Available options:

authorization_code

Response

id_token

string

required

access_token

string | null

required

token_type

string | null

required

Get the data of a user-provided Edge Config List Auth Tokens

Endpoints

Body

Response