Integrate iPaaS.com with Syspro to enable seamless data synchronization for customers, products, stock levels, warehouses, sales orders and invoices.
How to Connect
Prerequisites
Syspro is customer-hosted, so the components the integration talks to run in the subscriber's own environment and must be in place before the connection can be established:
The Syspro REST API is installed and reachable. It is deployed against the subscriber's Syspro database and must be reachable from iPaaS.com over HTTPS, with an SSL certificate covering the host name entered in API Url. A wildcard certificate covering the subscriber's domain also works.
Inbound firewall access is allowed for iPaaS.com. Because the API reads the Syspro database directly, inbound traffic to it should be restricted to the sources that need it — the iPaaS.com production address
52.184.255.108(outbound.iPaaS.com), the iPaaS.com staging range69.61.66.128/27, and any addresses the subscriber's IT team uses for troubleshooting. The Installation Instructions cover this in full.The Syspro database objects are installed. These raise the change events that drive automatic transfers. They are supplied as SQL scripts and are applied to the subscriber's Syspro database.
The Syspro webhook service is installed and running. This Windows service relays queued change events from the Syspro database to iPaaS.com. Without it, only Manual Sync transfers occur.
The full installation procedure for all three is in the Syspro Installation Instructions.
Configuration Details
Only one value is entered by the subscriber to establish the connection:
API Url: the host where the Syspro REST API is reachable, for example
syspro.example.com. Enter the host name only — do not includehttps://. The integration adds the scheme itself, so a value that already carries one produces an unusable address and every call fails.
Configure Subscription Settings
Field | Description | Required | Example |
API Url | Host name of the subscriber's Syspro REST API. Scheme is added by the integration — enter the host only. | Yes |
|
Transaction Success Status | The Syspro order status the integration writes back after a sales order transfers successfully. Leave blank to skip the write-back. | No |
|
API Throttle Limit | Maximum calls the integration makes to Syspro within the throttle window. | No |
|
API Throttle Seconds | Length of the throttle window in seconds. | No |
|
API Throttle Limit (To iPaaS.com) | Maximum calls made to iPaaS.com within the throttle window. | No |
|
API Throttle Seconds (To iPaaS.com) | Length of the iPaaS.com-side throttle window in seconds. | No |
|
Concurrent Connections | How many transfers run against Syspro at once. | No |
|
Concurrent Batch Executions | How many batch transfers run at once. | No |
|
Note: the throttle and concurrency settings pace the integration's own request rate. Syspro itself does not publish or enforce a rate limit — see Throttling below.
Authentication Methods
The connection authenticates automatically. There are no credentials for the subscriber to obtain, enter or rotate:
The integration connects to the Syspro REST API at the host given in API Url.
It requests an access token from the API's login endpoint.
The returned token is cached along with its expiry, and reused for subsequent calls until it expires.
When the cached token has expired, the integration requests a new one automatically on the next transfer.
Because token renewal is automatic, an expired token is not something subscribers need to act on. If the connection fails, the cause is almost always that the Syspro REST API is unreachable at the configured API Url, or that the host was entered with a scheme.
Initialization Support
Currently, initialization is not supported for Syspro in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process.
To load an existing Syspro customer base, catalogue or warehouse list in volume, subscribers or their MiSP should use bulk sync using Postman.
Throttling
The throttle fields are pre-populated by the integration's settings and control how quickly the integration issues requests, in each direction independently.
Syspro's REST API is customer-hosted and does not itself impose a rate limit or call quota, so these settings are not there to satisfy a vendor restriction. They exist to protect the subscriber's own Syspro server: the practical ceiling is whatever that server can absorb alongside its normal workload. Subscribers running Syspro on modest hardware, or during period-end processing, may wish to lower Concurrent Connections and the throttle limit rather than raise them.
For details on editing these values, see the Subscription Configuration – Edit article in the Help Center.