Salesforce Service Cloud APIs
Salesforce Service Cloud is the customer-service and contact-centre product on the Salesforce Platform, and its API surface is the Salesforce Platform API applied to service objects — Case, CaseComment, Knowledge articles, LiveChatTranscript, MessagingSession, entitlements and omni-channel routing — reached through the REST, SOAP, Bulk and Composite APIs. Alongside that record layer Salesforce ships purpose-built runtimes with their own contracts: an OpenAPI 3.0 document for the Einstein Bots Runtime API, a gRPC/protobuf contract for the Pub/Sub event API, a CometD Streaming API, and generally available hosted MCP servers that expose the sObject layer to AI agents over OAuth. There is no single global API host — every call is made against the customer's own org at the instance_url returned with the OAuth token, on API version 67.0 (Summer '26). Authentication is OAuth 2.0 only; Salesforce issues no API keys.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Salesforce Service Cloud APIs the way a machine reads it — 22 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Salesforce Service Cloud APIs scores 68.6/100 (exemplar), with a separate agent-readiness read of 47/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Salesforce Service Cloud APIs's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/service-cloud/"
title="Salesforce Service Cloud APIs on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/service-cloud.svg"
alt="Salesforce Service Cloud APIs Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/service-cloud/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/service-cloud/"
title="Salesforce Service Cloud APIs on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/service-cloud/card.svg"
alt="Salesforce Service Cloud APIs Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Salesforce Service Cloud APIs
Each block below is one kind of artifact we hold for Salesforce Service Cloud APIs. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Service Cloud REST API
Core REST API for Service Cloud operations: sObject CRUD over Case, CaseComment, EmailMessage, Knowledge articles and every other standard and custom object, plus SOQL query, SO...
Service Cloud Case Management API
The Case object and its children — CaseComment, CaseHistory, EmailMessage — worked through the sObjects REST resources. Assignment-rule behaviour on create and update is control...
Service Cloud Knowledge API
Knowledge article management — article versions, categories, publishing states and the knowledgeManagement REST resources used to surface self-service content.
Service Cloud Omni-Channel API
Omni-channel presence, work assignment and routing, exposed through the connect/omnichannel REST resources and the ServiceChannel / PendingServiceRouting objects.
Service Cloud Live Agent API
Real-time chat with customers over the Live Agent REST surface. Superseded for new builds by Messaging for In-App and Web, which authenticates with the scrt_api OAuth scope.
Service Cloud Pub/Sub API
The gRPC event API. Publish and subscribe to platform events and Change Data Capture events (including /data/CaseChangeEvent) with Avro-encoded payloads and replay-tracked subsc...
Service Cloud Streaming API
CometD/Bayeux long-polling surface for PushTopic, generic streaming and platform event subscriptions. The legacy transport; new integrations should use the Pub/Sub API.
Service Cloud CTI API
Open CTI — the JavaScript API that connects a telephony system's softphone to the Service Cloud console, plus the Voice/contact-centre surfaces built on it.
Salesforce Hosted MCP Servers
Generally available remote Model Context Protocol servers that expose the Salesforce sObject layer to AI agents over OAuth. Four least-privilege SObject servers (all, reads, mut...
Salesforce Service Cloud APIs Bot API
The bot API from Salesforce Service Cloud APIs — 3 operation(s) for bot.
Salesforce Service Cloud APIs Health API
The health API from Salesforce Service Cloud APIs — 1 operation(s) for health.
Salesforce Service Cloud APIs Versions API
The versions API from Salesforce Service Cloud APIs — 1 operation(s) for versions.
Scroll within the panel for all 12 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Service Cloud Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Service Cloud Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Service Cloud Event Surface
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Salesforce Service Cloud APIs — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 5
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/service-cloud · machine-readable index on apis.io
This is an independent, third-party profile of Salesforce Service Cloud APIs, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.