authentication
marketplace

SSO Token Exchange

Changed on

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/v1/integrations/sso/token

Request

  • Base URL: https://api.vercel.com
  • URL: https://api.vercel.com/v1/integrations/sso/token
  • Auth: none required

Request body

OR

Response

OR

Changes

    • breaking

      request body became required

    • breaking

      the request's body type changed from object to no type

    • breaking

      added subschema #1 subschema #2 to the response body oneOf list for the response status

    • breaking

      the response's body type changed from object to no type for status

    • breaking

      removed the required property from the response with the status

    • breaking

      removed the required property from the response with the status

    • breaking

      removed the required property from the response with the status

    • warning

      removed the request property

    • warning

      removed the request property

    • warning

      removed the request property

    • warning

      removed the request property

    • warning

      removed the request property

    • warning

      removed the request property

    • warning

      removed the optional property from the response with the status

    • info

      added subschema #1 subschema #2 to the request body oneOf list

    • info

      removed the non-success response with the status

    • info

      added the optional property to the response with the status