Send required signature headers
Provide timestamp, nonce and signature headers for every event.
Exact navigationVoice gateway → xConnect signed event callback
Before you begin
- Confirm the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What this guide covers
Provide timestamp, nonce and signature headers for every event. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Voice gateway → xConnect signed event callback.
- Locate the record, setting or action used to send required signature headers.
- Complete the displayed fields or controls exactly as described in this guide.
- Select the available save, submit, update, call, sign, upload or confirm action.
- Return to the related register, portal, dashboard or call panel and verify the recorded result.
Fields, choices and supported possibilities
Event bridge ruleProvide timestamp, nonce and signature headers for every event.
Code-backed validations and workflow rules
- The endpoint is machine-to-machine, signed, no-store and not a user login API.
Expected result and verification
- The send required signature headers workflow completes without a validation, permission or availability error.
- The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
- Any client-visible or public result appears only where the code explicitly allows it.
Security, privacy and operational checks
- Use a controlled test case, contact, extension or website origin before production rollout.
- Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.