Integrate iPaaS.com with Chargebee to enable seamless data synchronization for customers and their billing addresses, item prices (as products), invoices and credit notes TO iPaaS.com, and customers FROM iPaaS.com.

iPaaS.com refuses to save Initial Poll Days or Poll Page Size when it holds something that isn't a number (VALD-1156), and saves a blank one as its default (7 days, 100 per page). A number the integration can't use as entered is adjusted rather than refused: a value outside the allowed range uses the nearest allowed value, and a decimal uses its whole part. Each time the integration connects, it writes a warning in the transfer's activity log (Dashboard / Integration Monitoring) naming the setting and the value it used, never the value entered, for example: The "Poll Page Size" setting is above 100, so 100 is used. The warning does not appear in Logs or in Error Logs, and the transfer carries on.

Initial Poll Days matters only before the first poll of each data type: raising it later doesn't re-read older records. The poll events themselves are events of the type Webhook (Poll Request); the Chargebee Installation Instructions describe them, including the Filter rule each transaction poll needs.

Once the subscription has exchanged data with Chargebee, the settings page also lists values the integration saved for itself:

One subscription per Chargebee site. The subscription remembers the Chargebee site it first exchanged data with. Each Chargebee site keeps its own numbering, so two sites can each hold an invoice 1042, and another site's records could overwrite this site's in iPaaS.com. If Chargebee Site later names another site, every transfer stops with CHGB-BIZL-1008: change it back to the site the message names, or add a new subscription for the other site. Correcting a mistyped site name is safe, because a site that doesn't exist never exchanges data (it gives CHGB-NFND-1001 with site_not_found).

Changing the key: create a new full-access key on the same site, enter it in API Key and click Apply; the next transfer uses it. Delete the old key in Chargebee only after the new one is saved.

Webhooks: Chargebee's webhooks reach iPaaS.com on an endpoint the integration registers in Chargebee when the first scope is set Active, named "iPaaS.com subscription {your subscription id}". Its address carries the subscription's own webhook key, so Chargebee needs no other credential. Leave that endpoint alone in Chargebee.

Currently, initialization is not supported for Chargebee in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process. Existing Chargebee records arrive through the first poll of each data type, which looks back Initial Poll Days: raise that setting before the first poll to bring in a longer history, or use bulk sync using Postman. A single record can be sent at any time with a Manual Sync.

The subscription's throttle fields are pre-populated with these defaults: API Throttle Limit 500 and API Throttle Seconds 60, API Throttle Limit (To iPaaS) 500 and API Throttle Seconds (To iPaaS) 60, Concurrent Connections 2 and Concurrent Batch Executions 10. Set API Throttle Limit to no more than your Chargebee site's published per-minute limit (with API Throttle Seconds at 60). Chargebee states: "For test sites, it is 150 API calls per minute"; for live sites its published defaults are 150 (Starter), 1000 (Performance) and 3500 (Enterprise default), and "you can easily request higher limits by contacting Chargebee Support with your requirements" (Chargebee API: Error handling). On a test site or the Starter plan, lower the default 500 to 150 or less. Keep Concurrent Connections low for the same reason: each concurrent transfer calls Chargebee, so more of them use the per-minute limit faster. Concurrent Batch Executions is not used by this integration. See Subscription Configuration - Edit in the iPaaS.com Help Center for what each throttle field does.

Chargebee states: "If you receive an HTTP 429 Too Many Requests error response to an API call, it means that the API requests for your Chargebee site have exceeded acceptable limits", and that it "may also send a Retry-After header". The integration then writes a warning in the transfer's activity log, and the transfer is held and retried after that wait (60 seconds when Chargebee gives none). Subscribers or their MiSP should validate this behaviour in a staging environment before relying on it in production.