Salesforce APIConnect Salesforce without building on its API
Salesforce has REST, GraphQL and SOAP APIs. API is enabled by default on Enterprise, Unlimited, Performance and Developer editions; Professional Edition requires purchasing the API add-on, and Group/Essentials are not enabled by default. If you're reading the docs because you need Salesforce to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Salesforce and your other tools.
- APIREST + GraphQL + SOAP
- AuthOAuth 2.0
- AccessPlan-dependent
What the Salesforce API gives you
- Type
- REST + GraphQL + SOAP
- Authentication
- OAuth 2.0 (via connected/external client apps)
- Who can get access
- API is enabled by default on Enterprise, Unlimited, Performance and Developer editions; Professional Edition requires purchasing the API add-on, and Group/Essentials are not enabled by default.
- What it covers
- Standard and custom CRM objects (accounts, contacts, leads, opportunities, cases, etc.), queries via SOQL/SOSL, and org metadata.
- Limits
- Paid orgs such as Enterprise start at 100,000 API requests per 24 hours plus per-license allocations, and production orgs allow at most 25 concurrent long-running (20s+) requests.
Official docs: developer.salesforce.com. Checked September 2026. Vendors change access terms, so confirm with Salesforce before you build.
Building on the Salesforce API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Salesforce credentials, and manage tokens and refreshes. | Connect your Salesforce account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Salesforce task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Salesforce work off someone's desk, the build is the slow part.
What teams usually want the Salesforce API for
Account Record Creation
Caddi extracts required details from account-opening PDFs and creates the linked household, person, and new account form records, reducing manual data entry for client services teams.
Model Selection Forms
Caddi pulls household and account details to populate a model selection form and sends it for signature.
Household Review Report Filing
Caddi generates household review meeting report PDFs and files them with the correct metadata.
Signed IPS Archiving
Caddi downloads signed investment policy statements, archives the PDFs with the right metadata, and updates the related household record and task.
Salesforce API questions
Does Salesforce have an API?
Yes. Salesforce has REST, GraphQL and SOAP APIs, authenticated with OAuth 2.0 (via connected/external client apps). The official documentation is at https://developer.salesforce.com/docs/apis.
How do I get access to the Salesforce API?
API is enabled by default on Enterprise, Unlimited, Performance and Developer editions; Professional Edition requires purchasing the API add-on, and Group/Essentials are not enabled by default.
Does the Salesforce API have rate limits?
Paid orgs such as Enterprise start at 100,000 API requests per 24 hours plus per-license allocations, and production orgs allow at most 25 concurrent long-running (20s+) requests.
Can I connect Salesforce to my other tools without writing code against its API?
Yes. With Caddi you show the Salesforce task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Salesforce and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Salesforce with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Salesforce is reviewed before it runs in production, and every run is logged.
Connect Salesforce without the build.
Drop your work email and pick a time. We'll show you Caddi running your Salesforce workflow end to end.