Skip to main content
This page describes when Vendor Sync runs, how it is triggered, and the constraints integrations must respect when scheduling sync operations.

​
Sync Schedule

The integration is responsible for defining and owning the sync schedule. Pleo does not trigger syncs automatically. The recommended schedule is:
  • On connect: run an initial sync immediately after the integration is connected and authorised
  • Recurring: run a sync every hour, or less frequently if reducing the number of API calls made to the Accounting System is desirable
This ensures Pleo Vendors are populated from the outset and remain continuously up to date.

​
Ad Hoc Vendor Sync

Allow users to request fresh vendor data at any time by providing a Sync button. Ad hoc sync is useful when:
  • A new vendor has been added to the Accounting System and the bookkeeper wants it reflected in Pleo immediately.
  • A user suspects Vendors are out of date and wants to force a refresh.
Ad hoc sync follows the same reconciliation process as scheduled sync.

​
Pleo API Rate Limit

The Pleo Vendors API rate limit is 600 requests per minute, shared across all Vendors API calls made with the same credential, including scheduled and ad hoc Vendor Sync runs, Vendor Creation’s draft-vendor polling, and vendor activation. Budget your combined request volume across all of these against this one limit rather than sizing each workflow independently. See Rate Limits for details, and Backpressure and Throttling for what to do when a 429 is actually returned mid-run. This limit is separate from the target Accounting System’s own API rate limit, which the integration must determine and respect independently. Integrations should:
  • Conduct stress testing for syncing and importing operations at the scale you expect to support. There is no single “large” number, vendor volumes vary widely by company size and industry. As a rule of thumb, test with at least 2x your largest expected customer’s vendor count, and re-test as you onboard larger customers (mid-market and enterprise accounts can have vendor lists in the thousands or tens of thousands).
  • Optimise data processing to accommodate larger datasets without delays or degradation.
  • Monitor request volume during sync cycles and implement throttling if vendor volumes are high; on a 429, follow the Backpressure and Throttling guidance rather than treating it as an item-level failure only.
  • Avoid unnecessary repeated requests within a single sync cycle.

​
What Comes Next?