The Salesforce API Landscape

Headless Salesforce & APIsThe Salesforce API LandscapeA map of every major Salesforce API, what "headless Salesforce" really means, and how versions, limits, integration users and error handling work across them, so you pick the right API before you write a line of integration code.Intermediate · about 60 minutesWhat you will learn

Explain what headless Salesforce means and which platform capabilities can be consumed over APIs

Choose the right API (REST, Composite, GraphQL, UI API, Bulk 2.0, Pub/Sub, Metadata, Tooling, Connect, Agent, Models, Data 360) for a given integration scenario

Apply a versioning strategy and understand how API versions are released and retired

Monitor and budget API consumption using the /limits resource and the Sforce-Limit-Info header

Configure a least-privilege integration user with the Salesforce Integration user license

Read Salesforce API error payloads and map HTTP status codes to the right retry behaviour

Contents

What "headless" gives you: the five backend capabilities

The API catalog

Choosing an API: the when-to-use table

API versions and versioning strategy

API request limits

Integration users and licensing

API management, API Catalog and tooling

Error format and HTTP status codes

Worked example: an API inventory for an omnichannel retailer

Best practices

Common pitfalls

Hands-on exercises

Key takeaways