Overview
This article catalogs the errors the Syspro integration can record in the iPaaS.com error logs. Each entry gives the error's code, the message as it appears, what causes it, and what to do about it. All errors appear under Dashboard / Integration Monitoring / Error Logs in iPaaS.com.
Every error the integration itself raises carries a stable code in the form SYSP-{CATEGORY}-{NUMBER} — for example SYSP-AUTH-1001. The code is the fastest way to find an entry here: copy it out of the error log and search this page for it. Codes never change once published, so a code recorded in an old log entry still resolves to the right entry.
Some errors in the log come from the iPaaS.com platform rather than from the Syspro integration, and carry a two-part code such as VALD-1002 instead of the three-part SYSP-EXTN-1002 form. The segment count tells you which catalog to look in: two parts means the platform, and those codes are documented in Understanding iPaaS.com API Error Codes. This is the usual case when a record fails on the way into iPaaS.com — a product with no selling price, a customer with no email address, an inventory row whose warehouse has no matching iPaaS.com Location, or a tracking record whose shipping method does not match a configured Shipping Method. Each of those is documented in the relevant mapping collection article along with what to configure.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Some integration behaviors produce no error at all. Records excluded by a mapping filter — gift-card-only orders, deposit sub-orders, orders in a status the integration does not process, invoices whose sales order has not yet transferred — are skipped silently and never reach the error log. If an expected record is missing from either system and no error was raised, check the relevant collection's filter rather than looking for an error. A Manual Sync started with an identifier the record type cannot interpret behaves the same way: the value is rejected without an error being raised, the sync proceeds with no identifier set, and what you see is either nothing transferred or a later Syspro API error. If a Manual Sync produces no result, check the identifier against the format the collection's article specifies before looking for an error entry. The Syspro Integration Known Limitations article and the mapping collection articles cover those cases.
Several resolutions below refer to your Managed Integration Service Provider (MiSP) — the partner who owns your iPaaS.com configuration: your mapping collections and their filters, your connection settings and credentials, and reconciliation between the two systems. Where a resolution names the MiSP, they are the right first contact, because the change needed lives in configuration they control.
Supported Flows
Connection and Authentication
Syspro Data Transfer
Customer Lookup Formula
Error Collection
Connection and Authentication
Login Failure
SYSP-AUTH-1001 - Failed to log in to the Syspro API.
Where the Syspro API supplied a response, it is appended to the message in parentheses.
Description: The integration reached the Syspro REST API, but the API rejected the login attempt or returned a status other than success. The integration is authenticated by a passkey issued to iPaaS.com, so this is normally a sign that the API is running in a state where it cannot complete a login rather than that a subscriber-entered credential is wrong.
Resolution: Confirm the Syspro REST API is running and healthy on your server, and that the API Url subscription setting names the correct host. The appended response, where present, states what the API objected to. If the API is reachable and healthy and the failure persists, its own logs on your server record why the login was rejected — send that detail to your MiSP, who can raise it with iPaaS.com Support with the log excerpt attached.
Connection Failure
SYSP-EXTN-1001 - (the underlying connection error, as reported by the network layer)
The text varies with the cause — a host name that cannot be resolved, a refused connection, or a timeout.
Description: The integration could not reach the Syspro REST API at all. Nothing was returned to reject or accept the login, so the failure is below the level of the API itself.
Resolution: Confirm the Syspro REST API is running and that the host in API Url is correct and reachable from iPaaS.com. Enter the host name only — a value that already includes
https://produces an unusable address and every call fails. Confirm that any firewall between iPaaS.com and your network permits the traffic. Your MiSP owns the API Url setting and can correct it.
Syspro Data Transfer
Syspro API Call Failed
SYSP-EXTN-1002 - (the message returned by the Syspro API, followed by additional detail where the API supplied it)
Description: A call to the Syspro REST API failed. The message is the one Syspro returned, so its wording depends on what Syspro rejected — a missing required field, a value that does not exist in your Syspro configuration, or a record that could not be created.
Resolution: Read the returned message: it names what Syspro objected to. The common causes are documented in the mapping collection articles — a stock code that does not exist in Syspro, an order type or tax code that is not configured in your environment, or a customer record missing a name or email address. Correct the data in the source system, or the Syspro configuration, and re-run the transfer. Where the fix is a mapping or configuration change rather than a data change, your MiSP is the right contact.
Syspro API Returned an Unsuccessful Status
SYSP-EXTN-1003 - Error calling Syspro [operation]: [detail returned by Syspro] (Http Code: [status])
Description: The Syspro REST API responded, but with an HTTP status indicating the request was not carried out. The operation that was attempted, the detail Syspro returned, and the HTTP status all appear in the message.
Resolution: The returned detail identifies the cause; the HTTP status narrows it. Confirm the record satisfies Syspro's own requirements for that entity — required fields populated, referenced codes present in your Syspro configuration — and re-run the transfer. As above, a mapping or configuration correction is your MiSP's to make.
Customer Lookup Formula
Customer Lookup Could Not Reach Syspro
SYSP-INTL-1001 - Unable to connect to Syspro while looking up a customer by email address.
Description: A mapping formula that looks up a Syspro customer by email address ran without an available Syspro connection, so the lookup could not proceed and the mapping produced no value. Unlike the connection failures above, this reflects the state of the integration's own connection context rather than the reachability of the Syspro API.
Resolution: Re-run the transfer once — the connection is established per run, and a transient gap clears on the next attempt. If it recurs, this is not something you can correct in configuration: contact iPaaS.com Support at support@ipaas.com with the error log entry, the subscription, and the mapping collection the formula belongs to.