How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Events.com Connector Controller API

The connector-controller API from Events.com — 17 operation(s) for connector-controller.

Events.com Connector Controller API is one of 113 APIs that Events.com publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include connector-controller. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 20 operations across 17 paths, and defines 35 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://datagol-be.events.com.

20 operations 17 paths 35 schemas 3 DELETE9 GET5 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://datagol-be.events.com/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Events.com Connector Controller API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (s_jwt).

  • s_jwt — Jwt Token

Paths & Operations 20

Across 17 paths, the API surfaces 20 operations — 3 DELETE, 9 GET, 5 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

connector-controller 20
PUT
/connector/api/v1/update
updates connector-type example jira
connectorUpdate body → 400503403501500200
PUT
/connector/api/v1/instance/{id}
update instance of connector instance id
updateUserConnectorCredentialInfo 1 param body → 400503403501500200
DELETE
/connector/api/v1/instance/{id}
deleteUserConnectorCredentialInfo 1 param → 400403503500501200
PUT
/connector/api/v1/credential-metadata/{id}
updateConnectorCredentialInfo 1 param body → 400503403501500200
DELETE
/connector/api/v1/credential-metadata/{id}
deleteConnectorCredentialInfo 1 param → 400503403501500200
POST
/connector/api/v1/run
connectorRun body → 400503403501500200
POST
/connector/api/v1/register
creates new connector-type example jira
connectorRegister body → 400503403501500200
POST
/connector/api/v1/register/openapi
registerConnectorByOpenApiSpec body → 400503403501500200
GET
/connector/api/v1/instance
To get all instances by userId
getAllConnectorsByUserId → 400503403501500200
POST
/connector/api/v1/instance
creating instance of existing connector by passing base url and other config and returns the connector instance id
createUserConnectorCredentialInfo body → 400403503500501200
POST
/connector/api/v1/credential-metadata
createConnectorCredentialInfo body → 400503403501500200
GET
/connector/api/v1
returns all static connector meta data
getAllConnectors → 400503403501500200
GET
/connector/api/v1/names
returns all static connector names
getAllConnectNames → 400503403501500200
GET
/connector/api/v1/metadata/{connectorType}
get the meta data of connector, not for the specific instance
getConnectorMetadata 1 param → 400503403501500200
GET
/connector/api/v1/instance/{connectorType}deprecated
api to fetch connector instances for given user ,given type
getUserConnectorCredentialInfo 1 param → 400503403501500200
GET
/connector/api/v1/instance/byId/{id}
get instance of connector instance id
getUserConnectorCredentialInfo_1 2 params → 400403503500501200
GET
/connector/api/v1/instance/byCompanydeprecated
api to fetch connector instances for given company
getConnectorCredentialByCompanyId → 400403503500501200
GET
/connector/api/v1/getByName/{name}
getConnectorConfig 1 param → 400503403501500200
GET
/connector/api/v1/credential-metadata/{connectorType}
getConnectorCredentialInfo 1 param → 400503403501500200
DELETE
/connector/api/v1/delete/{name}
deleteConnector_1 1 param → 400503403501500200

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are ConnectorRunDTO (9 properties), OpenApiInfo (9 properties), EndPointInfo (8 properties), UserConnectorCredentialDTO (8 properties). Each schema is shown below with its type and property counts.

SaasxlResponseDTOConnectorCredentialDTO
object
5 properties
Tag
object
2 properties
EventRequestParameterDTO
object
2 properties
OpenApiConnectorRegistrationRequestDTO
object
3 properties
Component
object
1 property
ConfigDTO
object
2 properties
Parameter
object
4 properties
Server
object
2 properties
PathInfo
object
5 properties
SaasxlResponseDTOObject
object
5 properties
ResponseContent
object
1 property
OpenApiInfo
object
9 properties
SaasxlResponseDTOListString
object
5 properties
SaasxlHttpResponseObject
object
6 properties
ApplicationJson
object
1 property
CredentialDTO
object
4 properties
Response
object
2 properties
SaasxlResponseDTOListUserConnectorCredentialDTO
object
5 properties
Content
object
1 property
SaasxlResponseDTOListConnectorCredentialDTO
object
5 properties
JsonNode
object
EndPointInfo
object
8 properties
SchemaDefinition
object
4 properties
SaasxlResponseDTOListOpenApiInfo
object
5 properties
Info
object
5 properties
Contact
object
1 property
Schema
object
3 properties
ConnectorRunDTO
object
9 properties
UserConnectorCredentialDTO
object
8 properties
Config
object
2 properties
Request
object
2 properties
SaasxlResponseDTOUserConnectorCredentialDTO
object
5 properties
ErrorMessage
object
5 properties
SaasxlResponseDTOOpenApiInfo
object
5 properties
ConnectorCredentialDTO
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eventscom-connector-controller-api-openapi.yml Raw ↑

Other APIs Events.com publishes across the network.

DataGol MCP Server
Events.com Agent Config Controller API
Events.com Agent Config Migration Controller API
Events.com Agent Email Controller API
Events.com Agent Job Update Controller API
Events.com Agent MCP API
Events.com Agent MCP Config Controller API
Events.com Agent Memory API
Events.com Agent Skill Controller API
Events.com Agent Template Controller API
Events.com AI Feedback Controller API
Events.com AI Third Party Page Controller API
Where this information came from

This is an independent, third-party profile of Events.com Connector Controller API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.