- Records: sObjects describe/CRUD (40 routes), SOQL query and queryAll, SOSL search, Composite batch/graph/tree and collections (10 routes)
- Bulk API 2.0: ingest and query jobs with successful/failed/unprocessed result downloads (16 routes), plus the legacy async batch API
- Metadata and tooling: Tooling API (38 routes), UI API record and layout metadata (49), Named Credentials and External Credentials (13), apps and limits
- Automation and collaboration: invocable and custom flow actions, Connect and Chatter feeds (53), support, scheduling, loyalty and CPQ Apex REST routes
- Identity: OAuth 2.0 token, authorize, userinfo, introspect, revoke and dynamic client registration, headless login, OpenID discovery
- 330 routes (186 read-only) across login.salesforce.com and your My Domain host, documented in the AI integration guide (llms.txt)
Salesforce Platform API Connector
Salesforce Platform REST APIs — SOQL query and search, sObjects CRUD, Composite and Bulk API 2.0, UI API, Tooling and Metadata, Connect and Chatter, invocable actions and flows, Named Credentials, OAuth 2.0 endpoints — registered in Apivom Atlas as 330 routes on your My Domain org.
What you can do
Use cases
- Account and opportunity mirror — Read Accounts, Contacts and Opportunities with SOQL and the Composite API so a CRM-side copy stays current without a per-record round trip.
- Bulk load from an ERP or data platform — Push large record sets into Salesforce with Bulk API 2.0 ingest jobs and pull the successful and failed result files back for reconciliation.
- Metadata and configuration audit — Use the Tooling and UI APIs to list objects, fields, layouts and Named Credentials across orgs and track configuration drift.
Salesforce Platform APIs are the core surface of every Salesforce org: the REST data API for records, SOQL and SOSL, Composite requests that bundle several operations into one call, Bulk API 2.0 for large loads and extracts, the UI API for layouts and pick-lists, the Tooling API for metadata and Apex, Connect and Chatter for collaboration, and the OAuth 2.0 endpoints that issue the tokens. Apivom Atlas registers 330 of these routes, 186 of them read-only, with the My Domain instance URL applied per request so one connector serves any org. The credential contract is a Connected App: the caller runs the OAuth flow and sends the Bearer token, Atlas forwards and logs. No Apivom product workflow uses the Salesforce Platform API today — Apivom's CRM connectors in production are HubSpot, Zoho CRM, Microsoft Dynamics 365 and Zendesk, and the only Salesforce surface Apivom automates is the Autodesk Partner Center portal, driven through the browser rather than this API. The connector is catalogued for customers who run Salesforce and want Apivom products scoped against it.
A Connected App on your Salesforce org (consumer key + secret) and your My Domain instance URL. The caller runs the OAuth 2.0 flow and sends the access token as Bearer; the instance URL becomes the per-request base URL. Apivom Atlas forwards, logs and stores nothing.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
Which Salesforce editions and API versions does this cover?
Any org that includes API access (Enterprise, Unlimited, Performance, Developer; Professional with the API add-on). Routes carry the API version as a path parameter, so you choose the version your org supports; the My Domain instance URL is set per request.
Is this the connector Apivom uses for CRM sync today?
No. Apivom's production CRM connectors are HubSpot, Zoho CRM, Microsoft Dynamics 365 and Zendesk. Salesforce Platform is registered with its full route catalogue and credential contract; a Salesforce sync is scoped per customer.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.