IntegrationIntermediaterestcollectionsbulk
Implement REST sObject Collections API for bulk create and update
Real World Scenario
Mobile offline sync replays 200 locally queued Account updates; sequential PATCH calls exceed daily API limit.
Expected Answer
• sObject Collections composite resource up to 200 records per request
• PATCH collection for updates with allOrNone false partial success
• Response array maps input index to success errors per record
• External ID in body enables upsert semantics
• Batch 200 chunks respecting collection limit
• Retry failed subset only not entire batch
• Compare Collections vs Bulk API 2.0 threshold 2000 records
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. sObject Collections composite resource up to 200 records per request. PATCH collection for updates with allOrNone false partial success. Pick based on your integration pattern and team capability. Collections API fills gap between single REST and Bulk API—architect standard batch size 200. Balance speed of delivery with maintainability.
Architect Perspective
Collections API fills gap between single REST and Bulk API—architect standard batch size 200.