The Salesforce Agentforce Agent API is a REST API that lets developers communicate with AI agents directly — starting sessions, sending messages, receiving responses, and ending sessions. It is one of 43 APIs Salesforce publishes on the APIs.io network, and it sits squarely in the part of the platform most companies are trying to reason about right now: putting agents in front of real business systems.
What it does
The description is refreshingly narrow. This is not a model API and not a workflow builder. It is a conversation transport for agents: open a session, exchange messages, close the session. What makes it interesting is what those three verbs unlock — the API supports embedding agents on websites, creating headless agents for automation, and building multi-agent ecosystems. The same primitive powers a support widget and a fully server-side automation with no UI at all.
The base URL tells the rest of the story: https://{instance}.salesforce.com/services/data/v{version}/agent. Agentforce rides the existing Salesforce Data API surface, versioned and instance-scoped like the rest of the platform. Agents are not a separate product bolted on the side; they are another resource under the same data services path.
The published artifacts
On APIs.io the API entry carries a clean set of properties:
- Documentation
- GettingStarted
- APIReference
- CodeExamples
That is the full onboarding arc — overview, a get-started guide, a reference, and worked examples — which is exactly the artifact set an integrator or an agent needs to go from zero to a working session. It is tagged Agentforce, Agents, AI, Conversational AI, GenAI, and REST.
One sharp observation
The headless mode is the tell. Most “agent APIs” assume a human is typing into a chat box. Agentforce explicitly supports headless agents for automation and multi-agent ecosystems, which means the messages flowing through a session may come from another program, not a person. That reframes the API: it is not a chatbot endpoint, it is an inter-agent messaging bus that happens to expose Salesforce-grounded agents. When you build against it, you are deciding whether the caller on the other end of a session is a customer or a colleague agent — and the API treats them the same.
Takeaway
Agentforce Agent API is a small, sharp surface that does one thing: it makes Salesforce agents addressable over REST, for humans and machines alike. Read the Salesforce docs for the session mechanics, then see the other 42 APIs it lives alongside at apis.io/providers/salesforce/.