Ship integrations faster
Prebuilt article, category and reader actions reduce development time.

Embed Document360 into your product so customers can create, update and publish knowledge base articles, manage categories, readers and team accounts, and trigger workflows from real-time webhooks — all surfaced as in-app automations.
Prebuilt article, category and reader actions reduce development time.
Trigger publish workflows or bulk updates via API and webhooks.
Expose approved methods as managed MCP tools for customers.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Integrate and automate Document360 knowledge-base operations — create, update and publish articles, manage categories, team accounts and readers, and receive webhook notifications for article and project events. Use Cyclr to orchestrate multi-step workflows, sync content between your SaaS and Document360, and publish self-service integrations in your embedded marketplace or as MCP tools. (apidocs.document360.com)
PRODUCT USE CASES
Automate article publishing from product workflows, sync CMS updates to documentation, provision readers and permissions during onboarding, and trigger cache invalidation or notifications from Document360 webhooks. Publish integrations into Cyclr’s embedded marketplace for self-service install. (docs.document360.com)
Create and publish articles via the Articles API to surface release notes and support content in Document360 automatically. (apidocs.document360.com)
Update article content and SEO fields with the Update Article endpoints to keep customer docs and product CMS in sync. (apidocs.document360.com)
Create and update Reader or Team Account records to automate onboarding and permission changes. (apidocs.document360.com)
ORCHESTRATION
Cyclr sits between your SaaS product and Document360 to handle authentication, govern access and orchestrate every API call per customer, at scale.
Your app requests an action for a specific customer.
Cyclr authenticates, applies policies and routes the request.
Document360 processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore Document360 methods you can orchestrate through Cyclr.
Adds a new category.
Gets category by ID.
Updates a category by ID.
Deletes a category by ID.
Gets list of existing project versions, updated since the last cycle run.
Gets list of project versions.
Gets list of articles within project version
Searches for a phrase inside a project version.
Gets list of categories within project version.
Checks if email already exists in the project.
Gets available roles.
Deletes a user by ID.
Lists all the users.
Gets user by ID.
Adds a user to project
Gets settings for the article.
Deletes an article by ID.
Adds an article to an existing category.
Publishes an article by ID.
Forks an article by ID.
Gets article with an ID.
Deletes multiple articles
Updates an article by ID.
Creates multiple articles.
Updates multiple articles.
Deletes article version by ID and version number.
Gets article by a version number.
Gets all article versions by ID.
Updates settings for the article.
Publishes multiple articles.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing Document360 integrations in Cyclr.
https://apihub.document360.ioAPI key (X-API-Key header); include project_id or ProjectId header when required. (apidocs.document360.com)
Create; Read; Update; Delete; List; Publish/Unpublish; Webhook events; Project management
List responses return pagination metadata (pagination: page, page_size, total_count, has_more). Use page and page_size parameters. (apidocs.document360.com)
Rate limits apply per API token; Professional/Business 60 requests/min, Enterprise 100 requests/min. 429 responses include Retry-After and X-RateLimit headers. (apidocs.document360.com)
IMPLEMENTATION
Document360 v3 uses project-scoped API keys sent in the X-API-Key header; generate keys in Settings → Knowledge base portal → API tokens. Confirm which authentication options Cyclr Console enables during installation. (apidocs.document360.com)
API key (X-API-Key header); include project_id or ProjectId header when required. (apidocs.document360.com)
Generate a project-scoped API token in Document360; token is shown once, copy it immediately. (community.cyclr.com)
COMMON QUESTIONS
It lets you create, update, list and publish Document360 articles, manage categories, team accounts and readers, and respond to webhook events to trigger downstream workflows. (apidocs.document360.com)
Use a project-scoped API key: include it in the X-API-Key header. Generate tokens under Settings → Knowledge base portal → API tokens. Cyclr requires you to enter this key when installing the connector. (apidocs.document360.com)
Yes. Cyclr can publish Document360 Cycles into an embedded marketplace or MCP servers so many customers can self-serve installs while you retain governance. Tenant API keys and project context control per-customer access. (cyclr.com)
Yes. You can expose approved API actions as managed MCP tools in Cyclr, enforcing governance, packaging and controlled access for customers. Confirm which methods you publish from the Cyclr Console. (cyclr.com)
KEEP EXPLORING
Related Customer Experience connector for customer-facing integration workflows.
Related connectorRelated Customer Experience connector for customer-facing integration workflows.
Related connectorRelated Customer Experience connector for customer-facing integration workflows.