Customer systems
CRM, help desk and internal workflow systems can provide context for governed message workflows.
DEVELOPERS
Build governed messaging workflows with Verbum
Connect approved business systems to Verbum Sense, Verbum Assist and Verbum Automate workflows while preserving review paths, guardrails and traceable history. Detailed access depends on plan fit and approved onboarding scope.
- Scoped access
- Approved event workflows
- No public self-service API
ACCESS MODEL
Developer access by plan.
Verbum does not present developer access as a public self-service API. Use this single access model to confirm plan fit before detailed references, credentials or implementation materials are shared.
StarterCore workflow only
No CRM/help desk connector paths, Webhooks/API hooks, REST API or custom developer integrations.
ProEvent hooks and CRM/help desk paths
Webhooks/API hooks are eligible from Pro through private beta or guided onboarding with approved workspace scope.
Business + EnterprisePrivate-beta REST API and custom system scope
REST API remains private beta; Business and Enterprise scopes are reviewed through guided technical onboarding.
EnterpriseAdvanced review and rollout
Custom implementation, procurement and security review support for approved programs.
OpenAPI materials are not offered as a public self-service contract. Planning materials are shared only when available for the approved implementation scope.
WHAT YOU CAN CONNECT
What developer teams can connect.
These are capability areas for evaluation. Public pages describe integration patterns, not final endpoint contracts.
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.
DEVELOPER ACCESS FLOW
From plan eligibility to governed production use.
- Confirm access fit
Match the requested surface to plan eligibility, workspace purpose and approved scope.
- Share implementation context
Share target systems, workflow purpose, expected event families and security requirements.
- Review authentication and scopes
Confirm server-side credential handling, least-privilege scopes and workspace permissions.
- Configure approved surface
Set up the confirmed surface without bypassing governance.
- Monitor governed events
Keep triggered work, approvals, webhook activity and routing context visible where enabled.
API AND WEBHOOK PATTERNS
Planning guidance without fake public contracts.
Examples are illustrative. Final endpoint names, schemas, scopes, signing details and rate limits are confirmed only for approved implementation scopes.
Credentials, scopes and access boundaries are confirmed before access is provisioned. Tokens or secrets are never published on public pages.
Event categories may include lifecycle, approval, delivery and audit-related activity when enabled for the approved workspace scope.
Planning examples are illustrative until schemas, limits and event details are confirmed for the approved implementation scope.
Rollout planning covers expected volume, failure handling, ownership and governance review before production use.
SECURITY AND GOVERNANCE MODEL
Developer access follows the same control model as the product.
Developer access can be reviewed alongside security control materials, privacy documentation and protected evidence materials.
- 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.
REQUEST DEVELOPER ACCESS
Connect your systems without bypassing governance.
Request developer access for a scoped review of your integration goals, security requirements and rollout path.