Overview
Provision an HMAC v2 client connection with explicit PulseGate scopes, replay protection, rate limits, and connection logging.
Prerequisites
Permissions required
Steps (4)
-
1
Create the inbound connection
Create the external integration connection from PulseGate Connections.
Tips
Validation
Success criteria
-
2
Assign scopes and network policy
Choose the system, channel, contact, template, message, and context scopes required by the client.
Tips
Validation
Success criteria
-
3
Provision credentials
Deliver the generated client key/secret to the authorized external system using the approved credential process.
Tips
Validation
Success criteria
-
4
Sign and verify a request
Call a permitted Bridge action and verify HMAC, replay, scope, rate-limit, and PulseGate operation behavior.
Tips
Validation
Success criteria
About this guide
PulseGate is the communications control plane for Velaxe workspaces. Applications send business communication through trusted contracts while PulseGate resolves recipients and templates, applies authorization and policy, routes delivery, records message state, and publishes clean events.
Operations teams get a dedicated Messenger workspace for conversations, contacts, campaigns, approvals, failed messages, and media, plus administration for provider connections, sender identities, routing, templates, consent, suppression, quiet hours, cost rules, audit, and reports.
Durable workers handle dispatch, schedules, reminders, campaigns, provider webhooks, retries, reconciliation, metrics, retention, exports, media processing, and operational recovery. Handler, RCP, Bridge v2, EventBus, and ContextResolver contracts keep workspace integrations governed and source-aware.