Overview
This document catalogs the error messages a subscriber may encounter while using the Jotform integration. Most errors surface in the iPaaS.com error logs and originate from the response Jotform returns when a request cannot be completed. Behaviors that are not errors — for example, a form field whose value cannot be extracted is skipped and the submission continues — are described in the Jotform to iPaaS.com Customer Mapping Documentation and Jotform Integration Known Limitations documents rather than here.
Supported Flows
Customer Submission (Jotform to iPaaS.com)
Customer Submission (Jotform to iPaaS.com)
A Request to Jotform Did Not Complete Successfully
A call to Jotform returned an error. The HTTP status code and Jotform's response are shown in the iPaaS.com error log.
Description: When Jotform cannot complete a request, the integration records the failure along with the HTTP status code Jotform returned. That code indicates the cause. The most common causes are:
Invalid or unauthorized API key (commonly HTTP 401): the API Key on the subscription is incorrect, was regenerated in Jotform, or was revoked.
Daily API limit reached (commonly HTTP 429): Jotform enforces a per-plan daily API request limit, after which further requests are rejected until the limit resets.
Submission not found (commonly HTTP 404): the requested submission no longer exists in Jotform.
Service temporarily unavailable (HTTP 5xx) or a connectivity error.
Resolution:
For an authorization error, confirm the API Key on the Jotform subscription settings page matches a current key in your Jotform account (Account → API); create a new key in Jotform and update the setting if needed.
For a daily-limit error, wait for the limit to reset, stagger large jobs, or upgrade the Jotform plan. See Jotform's API documentation for the per-plan limits.
For other errors, confirm the submission exists and the API Url is correct. If the error persists, contact iPaaS.com Support at support@ipaas.com.