Integrate ISOPILOT without losing control over tenants, revisions and audit trails.
The Developer Area describes the operational scope of the Integration Hub: server-to-server authentication or Personal Access Tokens, least-privilege scopes, tenant-scoped APIs, candidate revisions, document locks and HMAC webhooks.
From credentials to a controlled revision.
Client Credentials example
The token endpoint issues a temporary bearer token. Real credentials should be stored in a secret manager, not in source code.
POST https://isopilot.it/api/v1/oauth/token Content-Type: application/json { "grant_type": "client_credentials", "client_id": "...", "client_secret": "..." }
The integration does not directly modify an approved revision.
ETag / If-Match
The base-version hash makes it possible to detect concurrent changes before an external proposal is accepted.
Check-out / Check-in
A temporary lock reduces conflicts when a document is being edited by an external system.
Controlled promotion
Only acceptance in the ISOPILOT interface creates the new revision through the existing document service.
Need to connect an ERP, DMS, portal or external workflow?
Describe the source system, events, objects to synchronise and security requirements: we can define scopes, webhooks and the revision model together.
Manage ISOPILOT from WordPress.
Install the official connector, start a 15-day trial or link an existing subscription in one click. Then open ISOPILOT through one-time SSO without duplicating governed documents.
