EN 
PT-BR
FR
ES
DE
Custom roles
Define roles beyond the defaults, backed by the permission dependency matrix.
Customer API v3
API support
Access 180+ endpoints across content, users, analytics, and drive. Scoped keys and OAuth 2.0 mean access stops exactly where you decide it stops.
Trusted by thousands of businesses across 150+ countries
Coverage
What’s included in API v3
Resource groups covering the whole platform with a broad API surface in content and knowledge assets, taxonomy, users and access, drive, analytics, project operations, and AI services.
| Resource group | Coverage | Methods |
|---|---|---|
| Contentarticles, categories, multilingual |
ArticlesArticle
templatesCategoriesTranslationsLanguages
drafts, versions, attachments, publishing, workflow status, bulk operations |
GETPOSTPATCHPUTDEL
|
| Knowledge assetsreusable blocks |
Content reuse
snippets, variables, glossary entries |
GETPOSTPUTDEL
|
| Taxonomyclassification |
LabelsTagsCustom fieldsRedirect
rules
field definitions, article and category labels, URL redirects |
GETPOSTPUTDEL
|
| Users and accessidentity and permissions |
UsersRolesReadersContent access
user groups, reader groups, portal and content roles, SSO schemes |
GETPOSTPUTDEL
|
| Drivemedia and assets |
Drive
files, folders, drive search |
GETPOSTPUTDEL
|
| Analyticsread only insights |
Analytics
article and category performance, search keywords, AI search, feedback, trending topics |
GET
|
| Project operationsplatform administration |
ProjectsWorkspacesOperationsAPI
references
imports, exports, task status, custom scripts, API reference logs |
GETPOSTPUTDEL
|
| AI servicesgenerative controls |
AI writer style guides
writer style guide rules |
GETPOSTPUT
|
Integrate
Connect with your tools
Knowledge stops being a destination and starts being a service other systems call.
Deliver knowledge where it’s needed
Integrate Document360 with CRMs, support systems, or product portals to deliver
knowledge right where it’s needed.
Automate the repetitive work
Automate repetitive tasks, from syncing updates to pushing knowledge into
customer-facing tools.
Keep every team in sync
Create a connected ecosystem where support, product, and content teams always
stay in sync.
Governance
Built for enterprise governance
Scoped API keys with role based access controls and content permissions.
Single sign-on
Team accounts authenticate through your configured SSO scheme.
Access limits
Grant a group access to a whole category, while keeping one article off-limits.
Legacy API
deprecated model
- Single project-wide token
- No expiry
- No revocation
- No permission boundaries
- Limited endpoint coverage
Customer API v3
current
- OAuth 2.0
- Scoped API keys
- Expiring credentials
- Role-based access
- Content-level permissions
Security & access control
Every request is scoped before it’s served
Scoped API keys
Create scoped API keys with specific portal roles, content roles, and content scopes.
OAuth 2.0 with PKCE
Authenticate users securely with OAuth 2.0, Authorization Code + PKCE.
No client secret ever reaches the browser.
Granular content access
Control access by workspace, language, category, and article. Evaluated as per request, all the way down
to a single article.
Key lifecycle control
One-time API key, with expiration and revocation. Lose a key, and you can only revoke and re-issue, but
not recover it.
Full CRUD access
Read it, write it, ship it
GET
/articles · /analytics · /readers
Read anything you own
Pull article, user, or reader-level insights to power dashboards and analytics.
POST
/articles · /users · /readers
Create from anywhere
Add readers, contributors, or articles from external systems to your knowledge base.
PUT
/articles/{id} · /users/{id}
Replace in full
Update articles or user data in real time without switching platforms.
PATCH
/articles/{id}/settings
Change one field, not the record
Omitted fields keep their current values, so a partial write never clears what you didn’t touch.
DELETE
/articles/{id} · /drive/files/{id}
Remove without collateral
Safely remove outdated data or articles while maintaining compliance and accuracy.
ASYNC
/operations/{id}/status
Long jobs, tracked
Imports and exports return a task you can poll, so a large migration never blocks the caller.
From siloed knowledge to connected workflows with APIs
Without Document360
- Content stays locked in the knowledge base, shared only by copy-paste.
- Updating articles across systems requires time-consuming manual effort.
- Analytics about readers and content performance stay hidden in silos.
- Custom integrations require heavy IT involvement and long timelines.
- A single project-wide token means no real permission boundaries.
With Document360
- APIs deliver knowledge directly into CRMs and support desks.
- Real-time sync ensures updates are instantly reflected in connected tools.
- APIs expose detailed insights for informed decisions.
- Plug-and-play APIs let teams build integrations with minimal effort.
- Scoped keys and OAuth 2.0 keep every request inside its boundary.
Who builds on it
Drive strategic outcomes across your organization
The developer’s outcome
Build integrations without fighting the platform
180+ endpoints, predictable REST semantics, cursor pagination and structured error objects. PATCH sends only what changed, async operations handle imports and exports, and OAuth 2.0 with PKCE keeps browser clients honest.
180+ endpoints
Structured errors
Cursor pagination
Capabilities
The product team’s outcome
Deliver knowledge inside the product
Pull articles straight into your product portal or in-app help, scoped to the workspace and language the user belongs to. Content stays in Document360 and your product reads it as a service.
In-app help
Workspace scoping
Multilingual
Capabilities
The support team’s outcome
Sync content, automate the busywork
Push knowledge into the helpdesk, keep reader groups aligned with your CRM, and let an article update fan out to every connected tool instead of being copy-pasted by hand.
Helpdesk sync
Reader groups
Bulk operations
Capabilities
The enterprise IT outcome
Governance that holds at the request level
Every call is evaluated against the caller’s portal role, content role and content scope. Keys carry an expiry, can be revoked outright, and never outrank the person who created them.
Role-based access
Expiring credentials
Full revocation
Capabilities
The analytics team’s outcome
Content performance in your own dashboards
Read article and category performance, search keywords, AI search behaviour, feedback and trending topics through a read-only surface, then join it with the rest of your BI stack.
Read-only surface
Search keywords
Trending topics
Capabilities
Verified reviews
Our customers
Our customers
say it best
“Document360 has been helping us for the past three years in so many ways, like creating and sharing effective technical documentation and communicating all their feature releases in an organized way.”
Kendal Walton · Support Coordination & Documentation Manager,
Aspire
5/5
Read case
study
Neil MacKella · Technical Content & Learning, Electrum
“The ability to control content access in a highly flexible way using reader groups helps us make sure the right content gets to the right people.”
5/5
Reader groups
FAQ
Questions, answered
How is API v3 different from previous APIs?
API v3 introduces OAuth 2.0 authentication, scoped API keys, granular access control, modern error handling, async operations, and significantly expanded endpoint coverage.
Can I continue using my existing API integrations?
Yes. Existing v1 and v2 integrations continue to work unchanged. Migration to API v3 is optional.
How does API security work?
API v3 supports OAuth 2.0 and scoped API keys. Every request is evaluated against the caller’s role permissions and content access scope.
Can I restrict API access to specific content?
Yes. API keys can be scoped to specific workspaces, languages, categories, and content areas.
Start building on customer API v3
Generate a scoped key in the portal, or read the reference first. Every endpoint, every parameter, and every error object.
❓Frequently Asked Questions
How is API v3 different from previous APIs?
API v3 introduces OAuth 2.0 authentication, scoped API keys, granular access control, modern error handling, async operations, and significantly expanded endpoint coverage.
Can I continue using my existing API integrations?
Yes. Existing v1 and v2 integrations continue to work unchanged. Migration to API v3 is optional.
How does API security work?
API v3 supports OAuth 2.0 and scoped API keys. Every request is evaluated against the caller’s role permissions and content access scope.
Can I restrict API access to specific content?
Yes. API keys can be scoped to specific workspaces, languages, categories, and content areas.
