A Comprehensive Guide to Performing CRUD Operations in Salesforce Using Postman

Himanshu Varshney
Senior Salesforce Developer
February 9, 2024

CRUD Postman

1. Setup Salesforce for API Access

a. Create a Connected App in Salesforce

Log in to your Salesforce account.

Navigate to Setup > Apps > App Manager.

Click New Connected App.

Enter the necessary details (e.g., name, email). In the API (Enable OAuth Settings) section, enable OAuth Settings.

Specify the Callback URL (you can use https://www.getpostman.com/oauth2/callback for Postman).

Select the required OAuth Scopes (e.g., Access and manage your data (api)).

Save the app and note down the Consumer Key and Consumer Secret.

b. Obtain Security Token

If not already received, you can reset your security token by going to My Settings > Personal > Reset My Security Token in Salesforce. The new token will be emailed to you.


2. Configure Postman for Salesforce Authentication

a. Import Salesforce Collection (Optional)

You can start with a Salesforce Postman collection if available, or create your own requests.

b. Set Up OAuth 2.0

Go to the Authorization tab in Postman.

Choose OAuth 2.0 as the type.

Click Get New Access Token.

Fill in the token name, grant type (Authorization Code), callback URL (used in the connected app), Auth URL, Access Token URL, Client ID (Consumer Key), Client Secret, Scope (full), and state.

Auth URL: https://login.salesforce.com/services/oauth2/authorize

Access Token URL: https://login.salesforce.com/services/oauth2/token

Request the token and save it.


3. Perform CRUD Operations

a. Create (POST)

Set the method to POST.

Use the endpoint https://yourInstance.salesforce.com/services/data/vXX.0/sobjects/ObjectName/, replacing yourInstance with your Salesforce instance and ObjectName with the Salesforce object you're targeting (e.g., Account).

In the Body tab, select raw and enter the JSON data for the new record.

b. Read (GET)

Set the method to GET.

Use the endpoint https://yourInstance.salesforce.com/services/data/vXX.0/query/?q=SOQL_Query, where SOQL_Query is your Salesforce Object Query Language query, e.g., SELECT+name+FROM+Account.

c. Update (PATCH)

Set the method to PATCH.

Use the endpoint https://yourInstance.salesforce.com/services/data/vXX.0/sobjects/ObjectName/ RecordId, specifying the ObjectName and RecordId of the record you want to update.

In the Body tab, select raw and enter the JSON data with the fields you want to update.

d. Delete (DELETE)

Set the method to DELETE.

Use the endpoint https://yourInstance.salesforce.com/services/data/vXX.0/sobjects/ObjectName/ RecordId, specifying the ObjectName and RecordId of the record you want to delete.


4. Handle Responses and Errors

After each request, check the status code and response body to ensure the operation was successful.

Handle errors according to Salesforce's error codes and messages.


5. Best Practices

Always test CRUD operations in a sandbox environment before executing them in production.

Manage your OAuth tokens securely.

Be mindful of Salesforce's API rate limits to avoid service disruption. This guide provides a general framework for performing CRUD operations on Salesforce using Postman. Depending on your specific use case and Salesforce configuration, additional steps or adjustments may be necessary.

Share this article:
View all articles

Related Articles

Creating Omnichannel Customer Support with AI Chatbots featured image
January 23, 2026
Customers move between channels constantly, and siloed support forces them to repeat themselves. This post explains the difference between multichannel and omnichannel, and how AI chatbots create continuity by identifying users, capturing context, and routing requests consistently across web chat, messaging apps, and other entry points. It also covers why consistency matters, including standardized answers and unified logging into your CRM or helpdesk. Finally, it shows how Anablock approaches omnichannel support by designing the full system, not just installing another widget.
Automating Support Ticket Triage with AI and CRM Integrations featured image
January 22, 2026
Support teams waste massive time on manual triage, reading, tagging, and routing tickets before real problem-solving even begins. This post explains how AI-powered ticket triage can instantly understand ticket intent, urgency, and category, then route each case to the right queue using your existing helpdesk rules. The biggest gains come when triage connects to CRM data, letting the system prioritize based on customer value, plan tier, active opportunities, or recent escalations, not just the words in the message. You’ll also see how this improves agent productivity, reduces transfers, and speeds up first responses. Finally, it outlines Anablock’s implementation approach, using secure API integrations, your real taxonomy and SLAs, and a gradual rollout that builds confidence from auto-tagging to full automation.
Improving Healthcare Appointment Scheduling with AI Chatbots featured image
January 21, 2026
Healthcare scheduling often breaks under phone volume, after-hours demand, and constant reschedules. This post explains how an AI healthcare chatbot can handle booking flows 24/7, collect the right patient details, and offer time slots that follow real clinic rules. It also covers automated reminders that cut no-shows, plus extra patient support like prep instructions and intake guidance. Finally, it explains how Anablock designs healthcare bots around real operational constraints and data protection so clinics get efficiency without sacrificing patient experience.

Unlock the Full Power of AI-Driven Transformation

Schedule Demo

See how Anablock can automate and scale your business with AI.

Book Demo

Start a Support Agent

Talk directly with our AI experts and get real-time guidance.

Call Now

Send us a Message

Summarize this page content with AI