The native Mkto-SFDC sync uses SFDC API calls.
The Marketo REST (and sometimes SOAP) APIs are used by other integrations.
If the native Mkto-SFDC sync uses SFDC API calls, that means the call originate from SFDC and not Marketo? And that's why we're not hitting our 50k limit?
And if that is the case, then is the the fix on the marketo end or the salesforce end? Do I instruct sales ops to increase the api limit or change the number of API calls SDFC makes to marketo?
The API calls (in both cases) are used by inbound connections to the service providing the API.
Ergo, when Marketo makes a connection to SFDC to check for SFDC-side updates and/or push pending updates that were made on the Mkto side during the sync interval, that's using SFDC API calls + counted against your SFDC API limit.
Everytime Marketo checks for SFDC-side updates and/or push updates to SFDC it counts agains our SFDC API Count.
Updates received and pushed to SFDC from Marketo do NOT count against our Marketo API count. Is this statement correct?
How do I lower the number of SFDC API through marketo (without have Sales Ops increase the number of SFDC API calls)?
1. Call marketo support and ask them to decrease the interval sync? I understand the standard is 5 minutes, so I would increase the minutes correct?
2. Use campaign inspector to see what campaigns are using SFDC flow steps? What flow steps and/or triggers am I looking for?
Are there other solutions?
A nice rundown is here: https://nation.marketo.com/docs/DOC-4809-salesforce-sync-error-daily-api-limit-reached
Take those steps before increasing the sync interval.