Before an integration can be listed on the Marketplace, it must pass iPaaS.com certification. This article covers the QA to complete first, what certification reviews, and what to submit.
QA before you submit
Run these checks in staging (never in production) before submitting:
All supported flows and directions transfer correctly, including deletes where supported.
Errors and messages are understandable, and record IDs are visible in the UI or URL for troubleshooting. See Discovery and Planning.
Logging is in place, API calls are logged at the right levels, and no API keys or credentials appear in logs. See Advanced Error Handling & Logging.
Collision handling behaves as declared. See Handling Duplicate Records.
External IDs are correct, including child/compound and ParentOnly cases. See Managing External IDs.
Supported Features are fully filled out, not left as bare-bones entries. See Supported Features Format.
Template mappings and their descriptions are complete, with client-specific data removed and any required IDs marked as placeholders. See Integration Documentation and Marketing.
Rate limit and throttling handling works against the real API. See Working with API Rate Limits.
What certification reviews
iPaaS.com reviews five areas:
Functionality - the integration does what it claims across its supported flows.
Code quality - a code review against platform standards.
Technical conventions - naming, data storage, mappings, and function conventions are followed.
Marketing - the Marketplace listing is complete and accurate.
Documentation - the required documentation set is present and clear.
Code review checklist
Real data models (PascalCase with JsonProperty tags), not dynamic or ExpandoObject types. See Data Models and Interface Definitions and Data Modeling.
Errors handled or rethrown, never silently discarded; 404s handled with notFoundAction where appropriate.
No secrets logged.
Out-of-the-box APIs used wherever possible, with extensions gated behind presets. See Integration Development Overview.
Conventions followed for data storage (presets vs persistent data vs version custom fields), mappings, and functions. See Configuration and Data Storage and Data Mapping and Custom Transformation Functions.
Documentation standards
Certification expects the documentation set described in Integration Documentation and Marketing: Installation Instructions, Known Limitations, Connections and Settings, Error Messages, API Endpoints, and Mapping Collections.
Submission requirements
To submit for certification, provide:
Source code - access to your integration's repository.
The compiled
.dll- which must be under 10 MB.The XML function documentation file for your conversion functions. See Data Mapping and Custom Transformation Functions.
A complete Marketplace listing and documentation set, per the sections above.
Third-party test access - a working account and credentials in the external system so the reviewer can validate the integration end to end.
After certification
Once certified, iPaaS.com promotes your integration from staging to production. For exactly what carries over, see Move Integration: Data Reference. For later changes, updates may require only abridged re-certification depending on scope; see Integration Maintenance and Update Procedures. Keep integrations current with third-party API changes per Managing Third-Party API Updates.