Across the APIs: Salesforce REST SObject Insert and Update (in English)
Updated 2026-11-07
What's changed since the video
Each change is dated and checked against Salesforce's own documentation.
- Sign in without a password in the request. The demo signs in to Postman with the OAuth username-password flow. Salesforce blocks that flow in orgs created in Summer '26 and later, and stops supporting it for connected apps on February 20, 2027 (Retirement of OAuth 2.0 Username-Password Flow for Connected Apps (Release Update), Salesforce Help, checked 2026-11-07). On your own bench, sign in with the client credentials flow or the web server flow with PKCE, through an External Client App (chapter 13, module 8).
- A newer API version. The video calls version 59 the latest. Today's is 68.0 (Winter '27), and the oldest versions are closing: 31.0 to 40.0 are deprecated in Summer '27 and retired in Summer '28, when a REST call to them returns 410 GONE (Salesforce Platform API Versions 31.0 through 40.0 Retirement, Salesforce Help, checked 2026-11-07).
Still right
- POST creates a record and answers 201 Created; PATCH, with the record's ID in the address, changes it and answers 204 No Content.
- Each call is one record, it's fast, and it still runs your automation: triggers and flows fire just as they would for a person.
All videos in this series: 통합 아키텍처
동영상은 클릭할 때만 YouTube에서 불러옵니다.