Background
iPaaS.com provides an Open Software Development Kit (SDK) for Integrators to develop Integrations between iPaaS.com and Third Party Software using their Application Programming Interfaces (APIs) as well as the iPaaS.com APIs. iPaaS.com recognizes that, from time to time, the companies that own and/or maintain these pieces of software will update their APIs which may include adding or deprecating fields, endpoints, or versions.
Integrators Responsibility
It is the responsibility of the Integrator to ensure that these changes do not break the existing functionality of the Integration. While API changes are usually announced with ample time to update integrations, iPaaS.com cannot control the announcement or lead time of third-party software publishers. Integrators are responsible for updating any Integrations they have written and published to the iPaaS.com Marketplace to correct for any defects caused by third-party API changes within 30 days of those API updates going into effect.
NOTE: Integrators cannot always remove a field from the integration. If that field was used in subscription mappings it cannot be removed until all of those references are also removed. The integrator should notify iPaaS.com of which field is being removed, so impacted customers (and their MiSPs) can be notified about necessary changes.
Possible Changes
New Endpoints Added
When a new endpoint is added, this, traditionally, indicates new features added to the API. It is at the discretion of the Integrator to update their Integration to support any new endpoints.
If a user of the Integration is interested in having a new endpoint added to an integration they should reach out to the Integrator directly.
New Fields Added on Existing Endpoints
When a new field on an existing endpoint is added, this traditionally indicates new features have been added to the API. It is at the discretion of the Integrator to update their Integration to support any new fields on existing endpoints.
If a user of the Integration is interested in having this added they should reach out to the Integrator directly.
New Versions of an API
When a version of a third-party API is released, it is at the discretion of the Integrator to update their Integration to support this new version.
If a user of the Integration is interested in having this added they should reach out to the Integrator directly.
Fields Deprecated on Existing Endpoints
When a Third-Party removes a field from their API it is up to the Integrator to determine if removing this field will impact the functionality of the integration (inclusive of logging errors). If it is determined that it will impact functionality for users, the Integrator needs to address it (either by removing that field from their integration or obtaining the data from a different source) as outlined in this policy.
Existing Endpoints Deprecated
When a Third-Party removes an endpoint from their API it is up to the Integrator to determine if removing this endpoint will impact the functionality of the integration (inclusive of logging errors). If it is determined that it will impact functionality for users, the Integrator needs to address it (either by removing that field from their integration or obtaining the data a different source) as outlined in this policy.
Deprecated Versions of an API
When a Third-Party deprecates a version of their API it is up to the Integrator to determine if this deprecated version is used in their integration and, if so, will its removal impact the functionality of the integration (inclusive of logging errors). If it is determined that it will impact functionality for users, the Integrator needs to address it (either by removing that field from their integration or obtaining the data from a different source) as outlined in this policy.
In cases where a new endpoint or field is intended to replace an old endpoint or field that is being deprecated, the Integrator will be responsible for updating their integration in order to keep feature-parity with the historical capabilities of the integration. Exceptions may be made, such as for fields and endpoints not actively being used by any iPaaS.com Subscribers.
Contacting Your Integrator
Please fill out the contact form on our website and we will put you in touch with the Integrator. Coming soon, you will be able to contact the Integrator via the listing within the iPaaS.com portal.