Stream records into a Salesforce Data Cloud data stream using the Streaming Ingestion API
domain: developer.salesforce.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Salesforce Bulk API 2.0 limits — the full failure-mode walkthrough related to developer.salesforce.com, checked against official docs, with linked verified routes.
Steps
Create an Ingestion API connector in Data Cloud Setup and configure a data stream with a schema; note the tenant-specific ingestion base URL shown on the connector detail page.
Obtain an OAuth 2.0 access token scoped to the Data Cloud tenant using the Connected App credentials and the /services/oauth2/token endpoint of your Salesforce org.
POST individual event payloads as a JSON array to the streaming endpoint: POST https://<tenant-ingestion-url>/api/v1/ingest/sources/<SourceApiName>/<ObjectApiName> with Authorization: Bearer <token> and Content-Type: application/json.
Inspect the HTTP 204 success response (no body) or handle 4xx errors; a 400 usually means a schema mismatch — verify field names and types against the data stream definition.
Monitor ingestion job status and record counts in Data Cloud Setup under Ingestion API or via the /api/v1/ingest/sources metadata endpoint.
Tune throughput by batching up to several hundred records per POST body and respecting per-connector rate limits documented in the org's ingestion connector settings.
Known gotchas
The ingestion base URL is tenant-specific (e.g. https://<hash>.c360a.salesforce.com) and differs from your standard Salesforce instance URL — copy it directly from the connector detail page, do not construct it.
Streaming ingestion is eventually consistent; records appear in DMOs after identity resolution and mapping runs, not immediately after the 204 response.
The payload must match the schema defined on the data stream exactly — extra or misspelled fields cause a 400 error.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?