Integration authentication
How integrations authenticate with Nexcal, why credentials must be protected and what to do when authentication fails. Available from the Power plan.
Last reviewed: 2026-07-22
Integration authentication
For an integration to be allowed to exchange data with Nexcal, it must authenticate itself. Authentication ensures that only authorized systems can access your workspace. It is the common basis for the REST API, webhooks, the Form API and public lead intake.
Availability
Authenticated integrations are available from the Power plan and are included in Enterprise. In Starter and Pro, there is no general API and no webhooks. For an overview, see plans and feature scope.
How authentication works
- Every integration uses credentials that uniquely identify your workspace.
- These credentials are carried with every transfer.
- A connection is only accepted with valid credentials.
Protecting credentials
Treat credentials like a password. Anyone with valid credentials can exchange data on behalf of your workspace.
- Do not share credentials with unauthorized people.
- Store credentials only in protected systems intended for that purpose.
- Replace credentials if you suspect they have been exposed.
Wichtig: Never send credentials by email or over the phone, and do not share them in publicly accessible channels.
When authentication fails
If credentials are invalid or expired, the integration status usually shows a corresponding note. Failed transfers are covered in errors and reprocessing.
Renewing access when needed
If you suspect that credentials have been exposed, you should replace them. After a replacement, the affected integrations must be updated with the new credentials so the data exchange can continue. Plan such a change so that no important transfers are missed, and afterwards check the integration status.