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

Cyclr Connectors API

Manage and install connectors

Cyclr Connectors API is one of 9 APIs that Cyclr publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Connectors. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, an AsyncAPI specification, a JSON-LD context, and 6 JSON Schemas.

This API exposes 6 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: https://api.cyclr.com/v1.0, https://api.eu.cyclr.com/v1.0, https://api.au.cyclr.com/v1.0.

6 operations 5 paths 2 schemas 1 DELETE4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.cyclr.com/v1.0
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

Cyclr Connectors API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 Bearer token obtained from the /oauth/token endpoint using Client Credentials flow with your Cyclr Console Client ID and Client Secret.

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 1 DELETE, 4 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Connectors 6

Manage and install connectors

GET
/connectors
Cyclr List Connectors
listConnectors 3 params → 200401
GET
/connectors/{connectorId}
Cyclr Get Connector
getConnector 1 param → 200401404
POST
/connectors/{connectorId}/install
Cyclr Install Connector
installConnector 2 params body → 200400401
GET
/account/connectors
Cyclr List Account Connectors
listAccountConnectors 1 param → 200401
GET
/account/connectors/{installedConnectorId}
Cyclr Get Account Connector
getAccountConnector 2 params → 200401404
DELETE
/account/connectors/{installedConnectorId}
Cyclr Delete Account Connector
deleteAccountConnector 2 params → 200401404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Connector (7 properties), InstalledConnector (6 properties). Each schema is shown below with its type and property counts.

InstalledConnector
object
6 properties
Connector
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cyclr-connectors-api-openapi.yml Raw ↑

Other APIs Cyclr publishes across the network.

Cyclr Accounts API
Cyclr Authentication API
Cyclr Cycles API
Cyclr Data on Demand API
Cyclr LAUNCH API
Cyclr Marketplace API
Cyclr Steps API
Cyclr Templates API
Where this information came from

This is an independent, third-party profile of Cyclr Connectors 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.