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.

Sections
API Name
Required (Yes/No)
Order of Implementation
Overview

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.

API to cleanup / logout

Registration API

Yes

2

API to get connector metadata.

API to get connector discovery details.

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.

This API needs to return all the projects that exist in the end system.

Returns all the entity types for a given project.

Returns detailed configuration information for a given entity type and project.

Returns lookup values for a given field, a given entity type.

Entity APIs

Yes

4

Entity CRUD APIs.

Gets information for a given entity id.

Creates a single entity in the end system.

Updates a single entity in the end system.

Searches API on entities.

Soft-deletes a single entity in the end system.

Substeps

No

Returns steps in which a given update needs to be broken.

User APIs

No

Search API on users.

Returns list of users matching a given search criteria.

Comments API

No

Implement these set of APIs to integrate comments.

Adds a single comment in the end system.

Gets all comments for a given entity.

Attachment APIs

No

Implement these set of APIs to integrate attachments.

Returns attachment content in base64 format.

Adds a single attachment in the end system.

Updates an attachment in the end system.

Deletes an attachment in the end system.

Parses and returns file name in given HREF or imgsrc.

Links

No

Implement these set of APIs to integrate links.

Adds or updates a link.

Deletes a link.

Gets siblings under parent ordered by rank.

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