Build Your Own Connector
The following table describes:
The list of SDK APIs and the mandatory APIs.
The "Order of Implementation" column to check the order of the APIs to be implemented. Empty columns represent optional APIs.
Overview of how OpsHub will call each API and its expected response.
Introduction
This section will help you understand key concepts of SDK API and help you get started with it.
Passing the Configuration Parameters to SDK APIs
Session APIs
Yes
1
API to manage sessions with the end system.
API to initiate SDK. In this API, SDK can connect to the end system, initialize memory cache, etc.
Registration API
Yes
2
Configuration Information APIs
Yes
3
These APIs are one of the most crucial APIs for the whole SDK to function as expected. OpsHub heavily relies on data sent as part of configuration info APIs to support multiple sync features.
This API needs to return basic server related information like max page size, time zone, etc.
Entity APIs
Yes
4
Entity CRUD APIs.
Substeps
No
Returns steps in which a given update needs to be broken.
User APIs
No
Search API on users.
Comments API
No
Implement these set of APIs to integrate comments.
Attachment APIs
No
Implement these set of APIs to integrate attachments.
Links
No
Implement these set of APIs to integrate links.
History APIs
No
Implement these set of APIs to integrate history.
This API is mandatory to implement if recovery.type is 'HISTORY_BASED' in entitytype - get API of configuration info category. The API should return matching history records as per the given search criteria.
Implement this API if your end system has a separate API for getting attachment history.
Implement this API if your end system has a separate API for getting comments history.
Implement this API if your end system has a separate API for getting links history.
Some Useful SDK Pages
Last updated

