A server error means something went wrong on the iPaaS.com side while processing an otherwise valid request. These are usually transient and safe to retry.
Every error in this family includes a stable code (for example INTL-1001). Find that code in the table at the bottom of this article to see exactly which rule was triggered.
Common causes
A temporary platform issue or unhandled condition.
A downstream service timed out.
A spike in load.
How to fix it
Wait a few seconds and retry the request, using exponential backoff for repeated attempts.
Confirm the request itself is well-formed (these errors are not caused by your payload).
If the error persists, contact support with the code, the approximate time, and the endpoint you called.
Codes in this family
Code | What it means |
| iPaaS.com API error: {exceptionMessage}. |
| Unable to connect to the database. Timeout set to 60 seconds. |
| The credit card was saved but the system failed to create the payment profile. |
| An exception happened that was not caught by our normal exception handling. Logs may point to a root cause. |
| Retrying the call to {endpoint} failed multiple times (Retry Count: {retryCount}). We are unable to complete this call. |
| The {item} was saved but could not be returned. Fetch the record with a GET request to confirm the saved values. |
| The authentication service was unable to complete the requested operation: {operation}. |
| iPaaS.com data configuration error: {detail}. |