Every error returned by the iPaaS.com API now includes a short, stable error code in the response, alongside a plain-language message and a link to the help article that explains how to resolve it. This page explains how those codes work and links to every error family in one place.
How error codes are structured
Each code looks like CATEGORY-NNNN, for example VALD-1001. The four-letter prefix tells you the type of problem; the number identifies the specific error within that type.
The prefix never changes meaning, so once you recognize it you can tell at a glance what kind of issue you are dealing with.
Codes are stable. A given code always refers to the same error, so you can reference it in support requests and internal documentation.
The number has no hidden meaning beyond identifying the error. Lower numbers within a category are simply the more common errors.
The six error categories
Prefix | Category | What it means | Can I just retry? |
| Authentication | We could not verify who you are. Your access token is missing, expired, or invalid. | No. Refresh or correct your credentials, then retry. |
| Authorization | You are signed in, but your account or plan does not permit this action. | No. Adjust your permissions or plan, or contact your administrator. |
| Validation | Something in your request is missing, malformed, or the wrong type. | No. Correct the request and send it again. |
| Business Logic | Your request is well formed, but it conflicts with a rule (for example a duplicate, or an inactive record). | No. Resolve the conflict described in the message, then retry. |
| Not Found | The record, table, or resource your request referred to does not exist. | No. Check the ID or name and try again. |
| Server Error | Something went wrong on the iPaaS.com side while processing your request. | Often. Wait a moment and retry; if it persists, contact support. |
How to use a code
Look at the prefix to understand the category of problem (see the table above).
Find the full code in the relevant family article below to see exactly which rule was triggered and how to fix it.
If you contact support, quote the full code and the request you sent. It identifies the exact error immediately.
All error families
Errors are grouped into 14 families, each with its own article. Browse by category:
AUTH · Authentication
Authentication Failures (4 codes)
AUTZ · Authorization
Authorization & Permissions (4 codes)
VALD · Validation
ID Validation (23 codes)
Required Field Validation (13 codes)
Field Validation (other) (77 codes)
Format & Range Validation (27 codes)
External ID Mapping (4 codes)
Custom Field Validation (6 codes)
Request Body Validation (1 code)
BIZL · Business Logic
Duplicate Detection (33 codes)
Inactive/Reactivation (1 code)
NFND · Not Found
Resource Not Found (22 codes)
Table/Schema Lookup (4 codes)
INTL · Server Error
Server Errors (4 codes)