Search

Page tree
Skip to end of metadata
Go to start of metadata

Integrate to interworks.cloud

The interworks.cloud integration framework is designed to enable data synchronization (accounts, products, invoices etc.) with third party systems. It can be used for integrating with any ERP, Finance, CRM or ticketing system that supports RESTful API. It requires no development effort since all data synchronization scenarios are defined with a use of a JSON document that follows the OpenAPI-Specification (v3) Standard https://kb.interworks.cloud/pages/viewpage.action?pageId=131007045.

  • OverviewThe interworks.cloud integration framework is designed to enable data synchronization (accounts, products, invoices etc.) with third party systems. It can be used for integrating with any ERP, Finance, CRM or ticketing system that supports RESTful API.
  • Register a New Integration ConnectorA new integration connector with a third party system can be defined in setup area:
  • Describe Third Party System's APIAfter registering a new connector, sample JSON Specification will be pre-filled. In this page we'll explain how the authentication, the API paths and the object schemas of the third party system API must be defined.
  • Define the Data Transformation SchemasThe Synchronization tab should be used in order to convert a JSON object from the  third party system to inteworks.cloud JSON object and vice versa. Each object must contain a brief description, the module type that will be synced and the push or pull action. Push is for sending data to the third party system and Pull for receiving data.
  • Create an Integration InstanceAfter setting all the required information (Authentication, API paths and Objects), you can now create an instance to your staging or production deployment of your third party system. You can have your BSS linked with more than deployments of the same third party system.
  • interworks.cloud JSON ObjectsBelow is a list of the available BSS JSON objects
  • Libraries & ExamplesThis page include references to libraries used by the integration framework and examples 
  • Log MechanismThe logging of the integration framework actions is managed from our generic logging mechanism. You must define first the level of logging you wish to have for the integrations you have activated using our integration framework and then you can access these logs from our audit log.
  • Testing the Integration Instance
  • Integration Instance SchedulerFor each out-of-the box connector that you activate or for any custom integration you will build, you must define a data exchange schedule. This can be accomplished from the "Scheduled Jobs" setup option.

interworks.cloud Platform API

Service Management API

Service Management API enables integration of new services via implementation of a fixed set of API endpoints that support subscription and access management performed by the central platform

Payment Gateway Integration Framework

With our Payment Gateway Integration Framework, your development team will be able to connect the interworks.cloud platform with any payment gateway with very little effort!

  • Payment Gateway PluginPlugins are used to extend the functionality of interworks.cloud platform and you can develop your own payment gateway plugin for integrating with the gateway you wish. This article will guide you through the process of creating your own plugin. The architecture is designed here
  • Payment Gateway SDKPaymentGatewayBase class  has several methods and fields which are required to implement.
  • Payment Gateway Integration Framework - Architecture DesignIn this page you can find the architectural diagram of the payment gateway framework

  • No labels