Developers

Connect your systems to Verbum without bypassing governance.

Webhooks and a private-beta REST API, released by plan and approved scope, so your systems react to what happens in Verbum and bring context into every conversation.

Request developer accessView plans

Webhooks and API hooks are available from Pro through private beta or guided technical onboarding. REST API remains in private beta and starts on Business through private guided onboarding. Verbum does not offer a public self-service API or public OpenAPI contract from this page.

Access by plan

What each plan includes.

  • Starter

    Core workflow only

    No CRM/help desk connector paths, Webhooks/API hooks, REST API or custom developer integrations.

  • Pro

    Event hooks and CRM/help desk paths

    Webhooks/API hooks are eligible from Pro through private beta or guided onboarding with approved workspace scope.

  • Business + Enterprise

    Private-beta REST API and custom system scope

    REST API remains private beta; Business and Enterprise scopes are reviewed through guided technical onboarding.

  • Enterprise

    Advanced review and rollout

    Custom implementation, procurement and security review support for approved programs.

What you can connect

Four ways to use it.

Capability areas for evaluation. Public pages describe patterns, not final endpoint contracts.

  • Customer systems

    CRM, help desk and internal workflow systems can provide context for governed message workflows.

  • Webhook workflows

    Approved event families can notify downstream systems while governance stays in Verbum.

  • Server-side API use cases

    Private REST access supports backend patterns after scope, authentication and permissions are reviewed.

  • Approval and audit context

    Use permitted context with Verbum Sense, route sensitive work through Verbum Assist review, keep Verbum Automate inside rules and preserve traceable history where enabled.

Integrations

Examples for planning Illustrative

Events and errors your integration should expect.

Names are illustrative. Final names, schemas, signing and delivery guarantees are confirmed during onboarding for your approved scope.

Webhook events

  • draft.created

    A governed draft workflow was created.

  • draft.approved

    A draft passed the configured approval path.

  • message.sent

    A message was sent through an approved channel workflow.

  • approval.rejected

    A reviewer rejected or returned a draft for changes.

  • audit.event.created

    A traceable workflow event was recorded where audit history is enabled.

Error categories

  • validation_error

    HTTP 400. The request shape, required field or business rule did not pass validation.

  • unauthorized

    HTTP 401. Authentication is missing, invalid or not accepted for the approved integration.

  • forbidden

    HTTP 403. The credential or workspace role is not allowed to perform the requested action.

  • rate_limited

    HTTP 429. The integration exceeded the rate limit or operational guardrail confirmed for its scope.

  • server_error

    HTTP 500. An unexpected service error occurred; retry and escalation guidance is confirmed during onboarding.

How access works

From plan eligibility to governed production use.

  1. 01

    Confirm access fit

    Match the requested surface to plan eligibility, workspace purpose and approved scope.

  2. 02

    Share implementation context

    Share target systems, workflow purpose, expected event families and security requirements.

  3. 03

    Review authentication and scopes

    Confirm server-side credential handling, least-privilege scopes and workspace permissions.

  4. 04

    Configure approved surface

    Set up the confirmed surface without bypassing governance.

  5. 05

    Monitor governed events

    Keep triggered work, approvals, webhook activity and routing context visible where enabled.

Developer access follows the same control model as the product.

  • API access is scoped by workspace and reviewed before provisioning.
  • Integrations should run from server-side environments, never from public client code.
  • Least privilege scopes are agreed during onboarding based on the integration purpose.
  • API and webhook activity is designed to preserve audit history and tenant context.

Security practices Trust Center

Connect your systems without bypassing governance.

Request developer access for a scoped review of your integration goals, security requirements and rollout path.

Request developer accessView plans

Context changes everything.