UnifyPort Account Webhooks: Why Workspace Events Go Missing
If a UnifyPort workspace webhook receives events from other messaging accounts but not one particular account, inspect that account’s independent webhook configuration. Account configuration overrides workspace configuration. An inactive account endpoint or a subscription that excludes the event does not send it to the workspace instead. Deleting the last independent endpoint restores workspace inheritance for subsequent initial deliveries—not past events.
Key takeaways
- A workspace endpoint and an account endpoint are different configuration scopes, not a primary-and-backup pair.
- List both scopes: an unfiltered endpoint list contains only workspace endpoints.
- An empty account-scoped list means no independent configuration, not no effective receiver.
- Deactivation preserves the override; restoring inheritance requires removing the last independent endpoint.
- Route selection, event subscriptions, signature verification and account connectivity are separate diagnostic gates.
Which configuration receives the account’s events?
The Create webhook endpoint reference documents the optional body field account_id. Supplying it binds the new endpoint to that messaging account. Omitting it creates a workspace endpoint. In responses, account_id is present for an independent account endpoint and omitted for a workspace endpoint.
Use this routing table before changing subscriptions:
| Account configuration | Workspace inheritance | What to inspect |
|---|---|---|
| No independent endpoints | Applies | Workspace endpoint status and subscriptions |
| Independent active endpoint with a matching subscription | Overridden | Account endpoint receiver and signing configuration |
| Independent endpoints exist, but all are inactive | No automatic fallback | Whether the independent configuration is still intended |
| Independent active endpoint excludes the event | No automatic fallback | Subscriptions on the account endpoint |
| Last independent endpoint deleted | Restored for subsequent initial deliveries | Workspace receiver readiness and a fresh test event |
For example, imagine a workspace collector subscribed to message.received, with an account endpoint subscribed only to account.status.updated. This is a hypothetical configuration, not an incident report. The workspace subscription does not fill the gap left by the account filter. Fix the selected account configuration or deliberately restore inheritance.
The event-filter guide explains which event names to select. The additional question here comes first: which scope owns delivery for this account?
Inspect both scopes with two read-only requests
Use the same server-side X-Api-Key for both calls. The key selects the workspace. The following are request-path illustrations; use the actual public account ID returned by your account query:
GET /v1/webhook-endpoints
GET /v1/webhook-endpoints?account_id=acc_example
According to List webhook endpoints, the first request returns workspace endpoints only. The second returns independent configuration for that account only; inherited workspace endpoints are not included. A successful data: [] in the second response therefore means “no independent account endpoints.” It does not mean “this account has no webhook path.”
Record the returned endpoint IDs, account binding, URL, status, subscribed_events, signing_enabled and retry policy. Inspect inactive entries too: they still matter to inheritance. Keep secrets and message content out of the diagnostic record.
Use exactly account_id. Empty, whitespace-only, repeated or differently cased query parameters are not an alternative spelling for omission. An explicit missing account or one outside the workspace returns 404 account_not_found; correct the identifier and workspace rather than treating that response as an empty list.
If both lists look correct, inspect the next boundary. Confirm the account’s authorization and runtime separately, then trace a supported fresh event through receiver authentication and durable storage. Do not restart a healthy messaging account simply because the wrong webhook URL is quiet.
Choose between repairing the override and restoring inheritance
Keep an account-specific receiver
Use Update webhook endpoint to repair the existing endpoint’s intended URL, active status or subscriptions. Preserve the reviewed signing and retry configuration. An empty signing_secret disables signing; do not copy an unsigned example into production.
Creating another active independent endpoint for the same account can return 409 account_webhook_already_exists with numeric code 40008. The same conflict applies when changing an inactive endpoint to active while another active endpoint exists. Updating an already active endpoint while retaining active is allowed, including historical configurations with multiple active endpoints. Do not assume that older duplicates are automatically removed. Workspace endpoints are not subject to this account-specific active-slot rule.
The account binding itself is not editable. On update, supplying account_id validates the original ownership; omission preserves it. Neither omission nor null converts an account endpoint into a workspace endpoint, and an existing workspace endpoint cannot be reassigned to an account.
Return the account to the workspace receiver
First verify that the workspace receiver is active, subscribes to the required events and has the correct verifier and durable store. Review the consequences with whoever owns the account-specific workflow.
Then explicitly retire the independent configuration using Delete webhook endpoint. Check every independent entry: leaving an inactive endpoint behind still leaves account configuration in place. Read the account-scoped list again and confirm that no independent endpoints remain. Successful deletion returns 204 with no response body.
This is a routing decision, not a general maintenance recommendation. For a temporary pause in CRM or AI processing, the webhook maintenance comparison explains why pausing downstream workers can be preferable to changing endpoint configuration.
Verify the new route without claiming recovery
Generate a controlled new message after the configuration change. Confirm the expected account and event at the intended receiver, verify its signature using the delivery contract, store it durably and only then acknowledge it. Check downstream processing separately.
These are recommended acceptance checks, not tests performed for your workspace. If a configuration request times out, read current state before repeating a mutation. The documented inheritance rule concerns subsequent initial deliveries; it does not establish how every in-flight attempt will behave.
UnifyPort’s unofficial interface provides a normalized event path, not guaranteed replay of missed payloads. A fresh successful test proves the new route works. It does not prove that the earlier missing interval was recovered.
FAQ
Does deactivating the account endpoint restore workspace delivery?
No. Inactive independent configuration still overrides the workspace. Removing the last independent endpoint restores inheritance for subsequent initial deliveries.
Can I add the missing event to the workspace wildcard instead?
Not to repair an account override. Inspect and change the effective account configuration, or deliberately remove it to restore inheritance.
Why does the account endpoint list return an empty array?
A successful empty result means no independent endpoints exist for that account. Read the workspace list to inspect inherited configuration. An error response is not an empty result.
Next step and sources
Start with List webhook endpoints and compare both scopes before changing anything.
Official product references checked on 2026-11-15:
Turn messaging integration into a stable product pipeline.
Start by sending through one API, then bring every inbound message back into your business system with standard events.