Designing API integration: retrieving only changed/new records since last sync
Posted: Wed Apr 29, 2026 5:27 am
Hi there,
I am working on a new integration between Simpro and another system. This may be either:
1. a direct integration between the two systems via Simpro’s APIs, or
2. an integration where an Oracle-based layer sits in between to perform additional validations and transformations.
Before I go too far into design and implementation, I’d like to get some expert advice on the following:
1. Which is better - Direct integration via APIs or having Oracle in between for certain validations
2. Either way, how do i capture the changes_since_last_sync and new_records_since_last_sync
3. Do we have any limitations on the requests per minute? (for APIs like JOB list(GET), AP Invoices list(GET), AR Invoices(GET), PAYMENTS(PATCH),..)
4. Is there any retry limit on responses other than 200 or 2xx? if so, how many for each key endpoint
5. Is api_key a better option over OAUTH2 for authorization/authentication
6. How simpro helps with PATCH/GET calls monitoring incase of direct integrations
For direct integrations, what tools or mechanisms does Simpro provide to help monitor and troubleshoot API calls (e.g. GET / PATCH requests, error logs, usage metrics)?
Thanks in advance to anyone who can share their experience or point me to relevant documentation.
I am working on a new integration between Simpro and another system. This may be either:
1. a direct integration between the two systems via Simpro’s APIs, or
2. an integration where an Oracle-based layer sits in between to perform additional validations and transformations.
Before I go too far into design and implementation, I’d like to get some expert advice on the following:
1. Which is better - Direct integration via APIs or having Oracle in between for certain validations
2. Either way, how do i capture the changes_since_last_sync and new_records_since_last_sync
3. Do we have any limitations on the requests per minute? (for APIs like JOB list(GET), AP Invoices list(GET), AR Invoices(GET), PAYMENTS(PATCH),..)
4. Is there any retry limit on responses other than 200 or 2xx? if so, how many for each key endpoint
5. Is api_key a better option over OAUTH2 for authorization/authentication
6. How simpro helps with PATCH/GET calls monitoring incase of direct integrations
For direct integrations, what tools or mechanisms does Simpro provide to help monitor and troubleshoot API calls (e.g. GET / PATCH requests, error logs, usage metrics)?
Thanks in advance to anyone who can share their experience or point me to relevant documentation.