Skip to content
Postman API Testing Tips

How To Get Session Id In Salesforce Using Postman

API Testing Blog

How to Obtain a Salesforce Session ID with Postman

Obtaining a Salesforce Session ID is crucial for interacting with Salesforce APIs using tools like Postman. This guide provides a step-by-step explanation of how to acquire this essential token.

1. Setting Up Your Postman Environment

Before diving into the process, ensure you have a Postman workspace set up. Within Postman, you can create a dedicated workspace for your Salesforce testing. This will help organize requests and responses related to your Salesforce interactions.

2. Obtaining Your Salesforce Credentials

You’ll need your Salesforce credentials, specifically:

a. Consumer Key: This is a unique identifier for your connected app in Salesforce. b. Consumer Secret: This is a secret key associated with your connected app, ensuring secure access to your Salesforce environment. c. Login URL: This is the URL where you log into Salesforce (e.g., https://login.salesforce.com).

3. Crafting Your Postman Request

a. Method: Choose POST as the HTTP method. b. URL: Use your Salesforce login URL, typically https://login.salesforce.com. c. Headers: * Content-Type: application/x-www-form-urlencoded * Authorization: OAuth (This indicates you’re using OAuth for authentication.)

4. Building Your Request Body

a. Grant_type: This should be set to password since you’re using username and password for login. b. Client_id: Your Consumer Key. c. Client_secret: Your Consumer Secret. d. Username: Your Salesforce username. e. Password: Your Salesforce password, optionally followed by your security token.

Example Request Body:

grant_type=password&client_id={your_consumer_key}&client_secret={your_consumer_secret}&username={your_username}&password={your_password}

Note: Remember to replace the placeholders with your actual credentials.

5. Sending Your Request

Click the “Send” button in Postman to execute this request. If successful, Postman will return a response containing your session ID.

6. Extracting the Session ID

The response body will look something like this:

{
  "access_token": "YOUR_SESSION_ID",
  "instance_url": "YOUR_SALESFORCE_INSTANCE_URL",
  "id": "YOUR_USER_ID",
  "token_type": "Bearer",
  "issued_at": 1677474761,
  "signature": "YOUR_SIGNATURE",
  "refresh_token": "YOUR_REFRESH_TOKEN"
}

You’ll notice the “access_token” key, which holds your session ID.

7. Using the Session ID in Subsequent Requests

To make further requests to Salesforce APIs, you’ll need to add the session ID as a header.

Header:

  • Authorization: Bearer YOUR_SESSION_ID

Example:

Authorization: Bearer 00Dxxxxxxxxxxxxxxxxx

Replace YOUR_SESSION_ID with the actual session ID received in the response. This header authenticates your requests with Salesforce, allowing you to access data and perform actions on your Salesforce environment.

8. Automation for Repeated Testing

For continuous automated testing, consider saving your session ID using Postman environment variables or storing it in a secure location. This simplifies and streamlines your test processes.

Conclusion

Using Postman for Salesforce API testing requires a session ID for authentication. This comprehensive guide highlights the steps to acquire this crucial authentication token, enabling you to perform API operations with Salesforce effectively. By following these steps, you can confidently leverage Postman to validate your Salesforce applications and streamline your testing efforts.

API Testing Blog