Marketing / Advertising Integration β Live Webhook URL Lookup
When a marketing or advertising platform integration is configured in Zenoti, the webhook URL and secret that Zenoti registered with that platform may need to be verified or retrieved. This article explains how Zenoti looks up live webhook configuration from the advertising platform on demand, how it handles platforms that do not support this capability, and what happens when authentication tokens need to be refreshed before the lookup can proceed.
Note: For conceptual background on the integrations framework, see Integration framework & infrastructure.
Before you begin
Your organization must have an active marketing or advertising platform integration configured in Zenoti.
The integration must use a supported platform that exposes live webhook URL retrieval. Meta does not support this capability; if you use Meta, Zenoti will return an unsupported error rather than attempting a platform API call.
You need the following permission:
Permission: You need the Manage Apps permission on the Api security role to view and manage integration configurations. Admin path: Configuration > Security > Security Roles > [your role] > Api > Manage Apps
Steps
Understand what the live webhook URL lookup does
The live webhook URL lookup retrieves the active webhook configuration β the URL and secret β directly from the advertising platform at the time of the request. This is a real-time query, not a cached value from Zenoti's database.
Use this lookup to verify that the webhook URL Zenoti registered with a platform is still active and correctly configured on the platform side. This is useful when:
- You suspect a webhook has been overwritten or removed on the platform side.
- You are troubleshooting why webhook events from an advertising platform are not reaching Zenoti.
- You want to confirm which accounts are associated with a given set of platform form IDs.
Initiate a webhook URL lookup
Navigate to Configuration > Integrations > Integration settings.
Locate and expand the marketing or advertising platform integration you want to inspect.
Provide the integration ID and, if applicable, the platform form IDs you want to check.
- Integration ID β The identifier for the specific integration configuration within Zenoti.
- Platform form IDs β The list of form identifiers on the advertising platform whose webhook configuration you want to retrieve. If you know which account owns the forms, you can supply account IDs to limit the lookup to those accounts and avoid redundant calls for unrelated accounts.
Submit the request to retrieve the live webhook configuration.
Zenoti queries the advertising platform directly and returns the webhook URL and secret for each matching form ID.
Filter the lookup by account
If you already know which integration account owns the forms you are looking up, supply the relevant account IDs in the request. This is an optional filter that limits the platform API call to only those accounts, reducing unnecessary calls for accounts that are not relevant to your query.
When account IDs are provided, Zenoti will only retrieve webhook configuration for forms owned by those accounts.
When no account IDs are provided, Zenoti evaluates all integration accounts associated with the integration to find the forms.
Handle unsupported platforms
Some advertising platforms do not expose an API for retrieving live webhook configuration. Meta is a confirmed example of a platform that does not support this capability.
If you initiate a webhook URL lookup for an integration that uses an unsupported platform, Zenoti returns a platform not supported response without making any call to the platform API. No partial results are returned.
When you see this response, the webhook URL and secret cannot be retrieved through this lookup. To verify the webhook configuration for an unsupported platform, log in to the platform's developer portal or admin console directly and inspect the webhook settings there.
Resolve authentication token refresh
Zenoti maintains an OAuth access token for each advertising platform integration. If the token has expired by the time a webhook URL lookup is requested, Zenoti automatically attempts to refresh it before calling the platform API.
- If the token refresh succeeds, Zenoti uses the refreshed token to complete the webhook URL lookup and returns the result.
- If the token refresh fails, Zenoti returns an integration not found error. The webhook URL lookup does not proceed.
When you receive an integration not found error in response to a webhook URL lookup, this indicates that Zenoti was unable to authenticate with the advertising platform using the stored credentials. To resolve this:
- Navigate to Configuration > Integrations > Integration settings.
- Expand the affected marketing or advertising platform integration.
- Re-authorize the integration by following the platform's Authorize flow. This generates a fresh access token.
- Retry the webhook URL lookup.
Important: Do not attempt to manually edit or paste access tokens. Always use the Authorize flow within the integration settings to refresh credentials.
Run a maintenance job for accounting sync
The accounting Manual Sync panel includes a Run Maintenance Job action that lets users with full access trigger the AccountingMaintenance sync operation for a specific date. Use this when you need to manually correct or reprocess accounting data for a past date.
- Navigate to Configuration > Integrations > Integration settings.
- Locate and expand the accounting integration accordion.
- Select Manual Sync.
- Locate the Run Maintenance Job section.
- Use the date picker labeled Choose a date to select the date for which you want to run the maintenance operation.
- Click Post to trigger the
AccountingMaintenancesync for the chosen date.
Permission: You need full access to the accounting integration to use Run Maintenance Job. If the control is not visible or is disabled, contact your organization administrator to confirm your access level.
Note: Run Maintenance Job is a manual operation. It does not replace or affect scheduled accounting sync jobs. Run it only when you need to reprocess data for a specific date outside the normal sync schedule.
Tips
- If you know which integration account owns the forms you are checking, always supply the account IDs. This keeps the lookup focused and avoids unnecessary platform API calls for unrelated accounts.
- If a webhook URL lookup returns an integration not found error, re-authorizing the integration is the first resolution step. Do not wait to re-authorize β OAuth tokens expire on a schedule set by the advertising platform, and expired tokens will cause all platform API calls from that integration to fail.
- For platforms that do not support live webhook URL retrieval, verify the webhook configuration directly in the platform's own admin console. Zenoti cannot retrieve this information on your behalf for those platforms.
- Use Run Maintenance Job only when you need to reprocess accounting data for a specific past date. For routine corrections, rely on the scheduled sync jobs configured in the Sync Schedule panel.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Webhook URL lookup returns a platform not supported message | The advertising platform (for example, Meta) does not expose an API for live webhook retrieval | Log in to the platform's admin console and verify webhook settings directly |
| Webhook URL lookup returns an integration not found error | The OAuth access token for the integration has expired and could not be refreshed | Navigate to Configuration > Integrations > Integration settings, expand the integration, and use the Authorize flow to re-authenticate |
| Webhook URL lookup returns no results for a specific form ID | The form ID may not be owned by any of the integration accounts, or the account filter excluded the owning account | Remove the account ID filter and retry, or confirm the form ID is correctly entered |
| Run Maintenance Job control is not visible or is disabled | Your account does not have full access to the accounting integration | Contact your organization administrator to confirm your access level |
| Post button produces no result after selecting a date | The selected date may have no accounting data to reprocess, or a sync job is already in progress for that date | Wait for any in-progress sync to complete, then retry with a date that has known accounting activity |