What is one way in ...
 
Notifications
Clear all

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?

1 Posts
1 Users
0 Likes
150 Views
Jacques
(@hepnerjacques)
Noble Member
Joined: 6 months ago
Posts: 360
Topic starter  

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?

  • A . Use the REST API as well as the SOAP API to effectively double the API calls allowed in a 24-hour period.
  • B . write a custom Apex web service that, given an email address, does all of the logic the integration code was doing.
  • C . Create several Apex InboundEmailHandlers to accept calls from the third-party system, thus bypassing the API limits.
  • D . Create an Inbound Message that, using Flow, can do all of the logic the integration code was doing.

Show Answer Hide Answer

Suggested Answer: C

   
Quote
Share: