---
schema_version: "1"
id: 29ebbb861933970a242ae71a89e2d1fa8f3c152bbf500f65851e7d08d58bfee9
title: "Headless Registration Flow: Send a Token Request"
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/security/headless-identity-impl-guide/guides/headless-identity/headless-identity-postman-registration-token-exchange.md
canonical_url: https://developer.salesforce.com/docs/platform/headless-identity-impl-guide/guide/headless-identity-postman-registration-token-exchange.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 1044c71c80e3d0a4dae688273da73e9a2a4f264a67bff78730bba65f2605304d
products:
  - Headless Identity Implementation Guide
  - Security
---

# Headless Registration Flow: Send a Token Request

After you receive the authorization code from Salesforce, exchange the code for an access token. This example walks you through initializing the code exchange with Postman.

|Required Editions|
|-----------------|
|Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience|
|Available in: **Enterprise**, **Unlimited**, and **Developer** Editions|

1.  From the Headless Identity API Demo folder in Postman, select **Registration - Token Exchange**.

    Note the location of the POST request. It’s the `/services/oauth2/token` endpoint on your Experience Cloud site.

2.  To see the request body, click **Body**. The token request for registration includes these parameters.


    -   `code`—The authorization code from Salesforce
    -   `grant_type`—The OAuth 2.0 grant type. Because the OAuth 2.0 authorization code grant type is the foundation of this flow, this parameter is set to `authorization_code`.
    -   `client_id`—The external client app consumer key
    -   `redirect_uri`—The external client app callback URL, which points to the OAuth 2.0 echo endpoint on your Experience Cloud site
3.  For the `code`, enter the authorization code that you received after sending the authorization request.

4.  To send the request to the token endpoint, click **Send**.

    Salesforce validates the token request and returns an access token to your app.