Menu

SSO Token Exchange

POSThttps://api.vercel.com/v1/integrations/sso/token
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.
https://api.vercel.com/v1/integrations/sso/token
const response = await fetch('https://api.vercel.com/v1/integrations/sso/token', {
method: 'POST',
headers: {
'Authorization': 'Bearer YOUR_ACCESS_TOKEN',
'Content-Type': 'application/json',
},
body: JSON.stringify("value"),
});
const data = await response.json();
console.log(data);
Response
"value"

This endpoint expects an object.

400One of the provided values in the request body is invalid.
403Error
500Error
SSO Token Exchange | Vercel API