Apex Web Service: Building Blocks for Web Wizards (in English)
Updated 2026-11-07
What's changed since the video
Each change is dated and checked against Salesforce's own documentation.
- A missing field is a 400. The demo returns 501 for a request that's missing a required field, then 500. By the HTTP standard, 501 means "the server does not support the functionality required to fulfill the request", and 400 means a "client error" (RFC 9110, IETF, checked 2026-11-07). A missing field is the caller's mistake: answer 400, and say which field (chapter 3, module 1; chapter 8, module 5).
- Your own door keeps its versions. Salesforce's version retirement "does not impact… Custom Apex REST & SOAP Web Services" (Salesforce Platform API Versions 31.0 through 40.0 Retirement, Salesforce Help, checked 2026-11-07), so your own services' versions are yours to manage.
Still right
- Five custom Apex REST services, from simple to robust: a GET of records; a response class you control carefully, which is your contract with the other team; a parameter; a POST with a request class; and an error returned with a status code.
- If a simple query is all you need, you don't need a custom service.
- Apex REST counts against the org's limits: "Calls to Apex REST classes count against the organization's API governor limits" (Introduction to Apex REST, Apex Developer Guide, checked 2026-11-07).
All videos in this series: Integraatioarkkitehtuuri
Video ladataan YouTubesta vasta, kun napsautat sitä.