Recently a Salesforce org's integration failed because it exceeded the number of allowed API calls in a 24-hour period. The integration handles a near real-time, complex insertion of data into Salesforce. The flow of data is as follows:
• The integration looks up Contact records with a given email address and, if found, the integration adds a Task to the first matching Contact it finds.
• If a match is not found, the integration looks up Lead records with a given email address and, if found, the integration adds a Task to the first matching Lead it finds.
• If a match is not found, the integration will create a Lead and a Task for that newly created Lead. What is one way in which the integration can stay near real-time, but not exceed the number of allowed API calls in a 24-hour period?
Select one answer.
Marked answer: C
Community Discussion
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Chose C1
A custom Apex web service can handle all lookup and creation logic in a single API call, reducing the number of API calls significantly. The Integration was doing calls for each scenario. Apex can perform all actions (query, insert, update) within a single transaction.
Chose C1
For D, does InboundEmailHandler require need send email by every email address to create task for?
