> ## Documentation Index > Fetch the complete documentation index at: https://support.fieldko.com/llms.txt > Use this file to discover all available pages before exploring further. # API and Platform Limits > Understand how FieldKo Atlas sync uses your org's API allocation, check your usage, and plan for reps, photos, and integrations. The FieldKo Atlas app syncs with Salesforce through Salesforce APIs, so every rep's sync uses part of your org's API allocation, alongside your integrations and other apps. Use this page to understand what drives FieldKo's API use, check your usage, and plan capacity as you add reps, photos, and integrations. Salesforce sets API allocations by edition and licenses, and they can change. This page doesn't list numbers. For current allocations, see [API Request Limits and Allocations](https://developer.salesforce.com/docs/atlas.en-us.salesforce_app_limits_cheatsheet.meta/salesforce_app_limits_cheatsheet/salesforce_app_limits_platform_api.htm) in the Salesforce Developer Limits and Allocations Quick Reference, and check your Salesforce contract or ask your Salesforce account executive. ## User Permissions Needed | To do this | You need | | - | - | | View System Overview and Company Information | View Setup and Configuration permission | | Change Sync Configurations | Customize Application permission | ## How Sync Uses the API Each sync makes a series of API requests. The app uses: * **FieldKo's Apex REST services**, in the FieldKo Native package, to download settings, layouts, and labels, upload and download records, record sync details, and update attendance. * **The Salesforce REST API** for queries, composite requests, and photo and file uploads and downloads. Calls to Apex REST services count as API requests, the same as calls to the standard APIs. | What Drives Requests | Why | Setting That Affects It | | - | - | - | | Number of reps | Every rep's device syncs on its own | Not a setting: plan for it | | Background sync | Each background sync checks for changes, even when there are few | **Interval for Background Sync** (60 minutes after install) and **Background Sync within Business Hours** in **Sync Configurations** | | Record volume | Downloads come in pages, and more records need more pages | **Number of Records** (999 after install) in **Sync Configurations**, the date window, and **Duration of the data to be fetched** | | Uploads | The app uploads changes in batches by size | **Batch Size For Native App** in **Sync Configurations** | | Photos and files | Each photo or file uploads or downloads separately | **Object Names for Attachment Sync**, such as **Past N Weeks**, **Fetch Only Most Recent**, and **Skip Sync** | | First login and Reset Sync | The app downloads all the rep's data and settings again | Ask reps to reset only when needed | For the settings, see [Sync](/admin/configuration-reference#sync) and [Photos and Files](/admin/configuration-reference#photos-and-files). For how records are chosen, see [Control What Syncs to the App](/admin/offline-data). Background sync doesn't upload photos. Reps upload photos when they sync with **Sync Images** turned on, so photo-heavy days, such as a planogram audit, use more requests. ## Check Your Usage Check API usage regularly, and before you add reps or a new integration: * From Setup, in the Quick Find box, enter `System Overview`, and then select **System Overview**. Review the API usage and storage sections. * From Setup, in the Quick Find box, enter `Company Information`, and then select **Company Information**. **API Requests, Last 24 Hours** shows your usage over a rolling 24-hour period, against your allocation. To see which reps sync most, review their [Sync Details](/admin/support-diagnostics#sync-details) records. The **Sync Action** field shows manual syncs, background syncs, and resets. ## Plan for Growth Work through these questions when you plan a rollout or a new integration: 1. **How many reps will sync, and how often?** Background sync runs at the interval you set while the app is open. A shorter interval keeps data fresher but uses more requests. 2. **How much data does each rep get?** Narrow the date window and objects so reps get only what they need. See [Narrow Records with Duration of the Data to Be Fetched](/admin/offline-data#narrow-records-with-duration-of-the-data-to-be-fetched). 3. **How many photos will reps take and download?** Limit downloads with **Past N Weeks** or **Fetch Only Most Recent**, and skip objects whose images reps don't need offline. 4. **What do your integrations use?** Prefer Bulk API for large loads, and schedule them outside reps' working hours. See [Integrate FieldKo with Other Systems](/platform/integrations/integrate). 5. **What else uses the API?** Other apps, reporting connectors, and data tools share the same allocation. To reduce background sync for one group without changing it for everyone, set **Interval for Background Sync** at the profile or user level. **Sync Configurations** is a hierarchy custom setting, so the most specific value wins. ## If You Reach Your Limit When your org exceeds its API allocation, Salesforce can refuse API requests until usage falls. Reps' syncs can then fail with an error, and integrations stop too. Work through these steps: 1. In **Company Information**, check whether usage is above your allocation. 2. Pause or reschedule integrations and data loads that aren't urgent. 3. Increase **Interval for Background Sync**, or turn on **Background Sync within Business Hours**. 4. Narrow records and photo downloads, as described in [Plan for Growth](#plan-for-growth). 5. If your usage keeps growing with your team, ask your Salesforce account executive about increasing your allocation. ## Other Platform Limits * **Storage:** Visits, survey answers, and photos use data and file storage. See [Plan for Data Volume, Storage, and Retention](/platform/data/data-volume). * **Email:** Salesforce limits single emails to 1,000 per day, which affects FieldKo's order emails. See [Notifications and Email Alerts](/platform/automate/notifications). * **Apex and flow limits:** Records from a sync are saved in batches, so your flows share limits with FieldKo's automation in each save. See [Design Automation for FieldKo](/platform/automate/design-automation). ## See Also * [Integrate FieldKo with Other Systems](/platform/integrations/integrate) * [Configuration Reference](/admin/configuration-reference) * [Plan for Data Volume, Storage, and Retention](/platform/data/data-volume) * [Understand Offline Work and Sync](/sync/how-sync-works) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.