Ingest records using the Salesforce Bulk API 2.0

domain: developer.salesforce.com · 5 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

  1. POST to /services/data/vXX.0/jobs/ingest with a JSON body specifying object, operation (insert/update/upsert/delete), and contentType (CSV)
  2. Upload a CSV payload via PUT to the uploadedFiles endpoint returned in the job creation response, with Content-Type text/csv
  3. Close the upload by sending a PATCH to the job URL with state UploadComplete
  4. Poll the job URL with GET until state reaches JobComplete or Failed
  5. Retrieve success and failure result files via the GET successfulResults and failedResults URLs on the job

Known gotchas

Related routes

Create and monitor a Salesforce Bulk API 2.0 ingest job for a large dataset
salesforce.com · 6 steps · unrated
Retrieve and process failed records from a Salesforce Bulk API 2.0 ingest job
developer.salesforce.com · 6 steps · unrated
Stream records into a Salesforce Data Cloud data stream using the Streaming Ingestion API
developer.salesforce.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ 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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans