Cyclr

REST API at {partner}.cyclr.com/api (partner-specific subdomain). Resources: accounts, cycles, integrations, connectors, steps, transaction-logs. POST /accounts creates a customer account. POST /accounts/{id}/cycles deploys an integration template to an account. GET /accounts/{id}/cycles lists active integrations for an account. GET /accounts/{id}/cycles/{cycleId}/transactions retrieves integration run history. POST /oauth/token obtains an account-scoped access token for embedded UI flows. All management operations via partner-level token. Response payloads are JSON.

Standard HTTP status codes with JSON error bodies. 401 for invalid token, 404 for missing account/cycle, 400 for validation errors. Integration run failures visible in transaction logs with step-level error details and connector error messages. Integration pause/resume available via API for error recovery. Rate limits not prominently documented. Cyclr platform uptime at status.cyclr.com. Connector updates managed by Cyclr (no connector maintenance overhead for SaaS vendors). Webhook support for cycle completion events.

Cyclr is an embedded iPaaS for SaaS companies — vendors use Cyclr to add native integrations to their own product (rather than integrating with external apps directly). The model: vendor builds integration templates in Cyclr's low-code builder, deploys them to customer accounts via API, and customers activate them via a hosted Cyclr UI (the 'Launch' component) embedded in the vendor's app. For agents in a SaaS product context, Cyclr's REST API enables: programmatic account provisioning for new customers, deploying integration templates to customer accounts, querying integration run history and status, and managing connector authentication. Confidence is docs-derived.

OAuth2 client credentials: POST /oauth/token with client_id (Partner API Key) and client_secret (Partner Secret) from Cyclr Console. Response: access_token (Bearer). Partner-level token has full API access. Account-scoped tokens generated for embedded UI flows (Launch component) — users authenticate with their own connector credentials through Cyclr's hosted OAuth flow. HTTPS enforced. Token expiry: 1 hour (re-issue via client credentials). Connector credentials encrypted per-account in Cyclr's Vault.

docs.cyclr.com provides the REST API reference, getting started guide (partner setup + account provisioning), Launch component embedding guide, connector authentication documentation, and integration template building tutorials. Documentation is adequate for the embedded iPaaS use case. Getting started requires a Cyclr partner account (demo/trial available). Cyclr Marketplace lists 500+ available connectors. Support via Cyclr support portal (email/ticket). Paid plans include dedicated support.