CRM API Limits and Portal API Usage Explained
The portal works with your CRM data through the CRM’s API. Every time a portal user opens a page with CRM data, submits a form or searches a list, the portal sends API calls to your CRM. Your CRM sets limits on those calls, so it helps to know what drives usage.
How the portal uses your CRM’s API
| Portal activity | API use |
|---|---|
| A portal user opens a page with lists, detail views or data widgets | Reads records from your CRM |
| A portal user or admin submits a form, or adds, edits or deletes a record | Writes the change to your CRM |
| An admin runs Portal Sync (entity, language or portal-level entity sync) | Reads the CRM structure: entities, fields and languages |
| An admin adds or edits a contact in Portal User Setup | Writes the contact to your CRM |
The portal connects through the connection you set up in the admin portal:
| System | Connection the portal uses |
|---|---|
| Dynamics 365 | An Entra ID app registration (Service URL, App ID, Client Secret) |
| Salesforce | A connected app. See How to Find Your Salesforce Consumer Key and Secret. |
| Business Central | An Entra ID app (Client ID, Client Secret, Tenant ID) on Settings → Portal Settings → Business Central Authentication |
How many API calls the portal uses
There is no fixed daily number. API usage depends on:
- how much your portal users use the portal
- how much traffic the portal has
- which pages, lists and widgets portal users open
How CRM API limits affect the portal
Salesforce, Microsoft Dynamics 365 and Microsoft Dynamics 365 Business Central each set their own API limits. The limits depend on your edition and licenses, and the portal’s calls count toward them along with any other integrations that use the same system.
Because of this, data syncs with your CRM, but timing depends on your CRM’s API limits and on how much traffic the portal has. Sync is asynchronous, so the portal and your CRM are not always in step at the same moment. See How CRM Data Sync Works in CRMJetty Portal.
Note: Check your current limits and usage in your CRM’s own admin tools. In Salesforce, for example, Setup → Company Information shows API Requests, Last 24 Hours. For Dynamics 365 and Business Central, see Microsoft’s documentation on API and service protection limits for your environment.
Keep API usage under control
- Show fewer records per page. In the List widget, set Record Per Page to the number portal users actually need.
- Sync only what changed. On the Portal Sync page, use Sync Specific Entity instead of Sync All Entities when only one entity changed (Business Central: Sync Specific Tables). See How to Sync CRM Layout Changes to Your Portal.
- Enable only the entities you need. Fewer entities in Settings → User Settings → Entity Configurations (Business Central: Table Configurations) means fewer lists and forms that read from your CRM. See How to Enable CRM Entities and Custom Objects in the Portal.
- Watch other integrations. Other apps that call the same CRM share its limits. If you are close to a limit, review them too.
- Test in a sandbox. Build and test heavy pages against a sandbox before you release them to live. See How to Switch the Portal Between Sandbox and Live CRM.
Troubleshooting
Portal data updates slowly at busy times: Your CRM may be throttling API calls. Check API usage in your CRM, reduce Record Per Page on large lists, and look for other integrations that use the same CRM.
Related articles
- How CRM Data Sync Works in CRMJetty Portal
- Do Portal Contact Changes Sync Back to the CRM?
- How to Sync CRM Layout Changes to Your Portal