Salesforce Bulk API 1.0 and Bulk API 2.0 provides a simple interface to load large amounts of data into your Salesforce org and to perform bulk queries on your org data

1. Demystify Salesforce
Bulk API
SalesforceCodex.com 1

2. SalesforceCodex.com 2
About Me
Dhanik Lal Sahni
Technical Architect
Conduent Business Solution
Certified Application Architect
Twitter : @dhaniksahni
Blog : salesforcecodex.com

3. SalesforceCodex.com 3
Session 15-Agenda
• In a given scenario, recommend when to use API-based
integrations, such as SOAP, REST, Bulk, Streaming, Canvas,
Workflow outbound, APEX (Callouts, @ future, etc.), and
Lightning Connect to achieve business requirements.
• Compare and contrast the advantages and drawbacks (design
trade-offs) of using API-based integrations such as SOAP, REST,
Bulk, Streaming, Canvas, Workflow outbound, APEX (Callouts,
@future, etc.), and Lightning Connect.
28%
17%
15%
10%
15%
10%
5%
Integration Architecture
Designer Exam
1 2 3 4 5 6 7
Salesforce Integration Capabilities:: 28%

4. SalesforceCodex.com 4
AGENDA
• What is Bulk API?
• When to use Bulk API?
• Bulk API Processing steps
• Bulk API 1.0 vs 2.0
• Best Practice for using Bulk API
• Bulk API Limit
• Demo

5. SalesforceCodex.com 5
WHAT IS BULK API?
 Bulk API is an asynchronous API to work with high volumes of data.
 Bulk API provides a programmatic option to quickly load your data into
Salesforce.
 Use Bulk API for more than 50K records.
Salesforce Bulk API
(v1.0/v2.0)
Data Salesforce Org

6. SalesforceCodex.com 6
WHEN TO USE BULK API?
1. Bulk API is based on REST principles and is optimized for loading or deleting
large sets of data. Example: You have new client and they want to move their
data from existing system to Salesforce.
2. Salesforce processes batches in the background. So there is no problem of
network speed.
3. Easily controlled using standard features (setup menu).
4. Easiest way to use Bulk API is to enable it for processing records in Data
Loader using CSV files.

7. SalesforceCodex.com 7
BULK API PROCESSING (V1.0)
Client Job Processing Server
Batch
Batch
Process job to
insert/update data in
org
Save Result to job
Result
Result
Result
Check Job
Status
Data

8. SalesforceCodex.com 8
BULK API PROCESSING STEPS
Create Job
Upload Data
Single Batch/Multiple
Batch
Close Job
Check Status
Login to
Salesforce
Get session token
Use token to hit Salesforce APIs
post
post
patch
put
get

9. SalesforceCodex.com 9
BULK API V1.0 VS V2.0
BULK API 1.0
BULK API 2.0
Batch need to create manually No need to create batch.
Limits on number of record, file size and batch Based on daily limit in 24 hr hour
Built on custom REST framework so not like other
REST API Integration
Built on standard REST API so similar to other REST
API integration
Support serial and parallel processing Support only parallel processing

10. SalesforceCodex.com 10
BULK API VS SOAP API
SOAP API
BULK API
SOAP API is optimized for real-time client
applications that update a few records at a time.
Bulk API is designed to make it simple to process
data from a few thousand to millions of records.
SOAP API retrieves data in batches of up to 2,000
records.
Bulk API allows batches of up to 10,000 records.
SOAP API is based on SOAP WSDL protocol. It uses
XML format.
Bulk API uses REST protocol and allows XML, JSON,
and CSV data format.
SOAP API is synchronous processing. Bulk API is asynchronous
*DataLoader is using SOAP API for bulk API.

11. SalesforceCodex.com 11
BULK API 2.0
1. Bulk API 2.0 provides a simple interface to quickly load large amounts of data
into your Salesforce org and to perform bulk queries on your org data.
2. Bulk API 2.0 supports all OAuth flows supported by other Salesforce REST APIs.
3. Bulk API 2.0 simplifies uploading large amounts of data by breaking the data
into batches automatically. All we have to do is upload a CSV file with record
data and check back when the results are ready.
4. Instead of limiting the amount of data uploaded daily by the quantity of jobs,
Bulk API 2.0 uses a limit of total records uploaded

12. SalesforceCodex.com 12
BEST PRACTISE FOR BULK API
Use Parallel Mode
1. This is default mode and process record very fast.
2. If parallel processing cause lock contention then organize records to
process it parallel or do serial processing.
Organize Batches to Minimize
Lock Contention
1. Organize record in such a manner so that it will not reference records
in another batch.
2. Put related records in same batch.
Minimize Number of Fields
1. Processing time is faster if there are fewer fields loaded for each record.
2. Foreign key, lookup relationship, and roll-up summary fields are more likely to
increase processing time.
Optimize Batch Size
1. Submit batches that process in less than 10 minutes.
2. Batch sizes should be adjusted based on processing times.
3. Start with 5000 records and adjust the batch size based on processing time. If it
takes more than five minutes to process a batch, it may be beneficial to reduce
the batch size.

13. SalesforceCodex.com 13
BULK API LIMIT
Item Bulk API Limit Bulk API 2.0 Limit
Maximum number of records uploaded per
24-hour rolling period
150,000,000 (15,000 batches x 10,000
records per batch maximum)
150,000,000
Maximum time before a batch is retried 10 minutes The API automatically handles retries. If you
receive a message that the API retried more
than 10 times, use a smaller upload file and
try again.
Maximum file size 10 MB 150 MB
Maximum number of characters in a field 32,000 The same
Maximum number of fields in a record 5,000 The same
Maximum number of characters in a record 400,000 The same
Maximum number of records in a batch 10,000 N/A
Maximum number of characters for all the
data in a batch
10,000,000 N/A

14. salesforcecodex.com 14
Share some inspiring words about
@salesforcecodex on twitter

15. salesforcecodex.com 15
Keep Exploring. Keep Learning.