Configure the asset event webhook service

The asset event webhook service is configured by App Support on your behalf. To set up the service, contact App Support with the required information. App Support deploys the service to a UAT environment first so you can verify it is working as expected before it is promoted to production.

Prerequisites

Before contacting App Support, ensure you have the following information ready:

  • A webhook endpoint URL that is publicly accessible and returns a 2xx HTTP response on receipt.

  • An enabled flag for each URL — set to true to activate immediately, or false to stage the integration before going live.

  • The asset supertypes you want to receive events for (Resource, Project, Adaptation, Template, or a subset). The default is Resource only.

  • The event types you want to receive (CREATED, EDITED, DELETED, PURGED, REVERSION, or a subset). The default is all event types.

  • If you require event filtering, the filter configuration you want applied — see Asset event webhook service reference for filter kinds and conditions.

  • If your endpoint requires API key authentication, the secret value for the key. App Support creates the GCP Secret Manager entry on your behalf.

  • If you require custom request headers, the header names and values.

Request initial setup

To request initial setup:

  1. Contact App Support specifying:

    • Your webhook endpoint URL or URLs.

    • The enabled flag for each URL.

    • The asset supertypes you want to receive events for.

    • The event types you want to receive.

    • Whether your endpoint requires API key authentication, and if so, the secret value. App Support creates the GCP Secret Manager entry on your behalf.

    • Any custom headers required.

    • Any filter configuration required.

  2. App Support deploys the service to your UAT environment.

  3. Verify the service is working as expected on UAT — see Verify the service for guidance.

  4. Confirm to App Support that UAT verification is complete.

  5. App Support promotes the configuration to production.

Multiple webhook URLs can be configured. Each URL can be independently enabled or disabled without affecting others. To add, remove, enable, or disable a URL after go-live, contact App Support.

Verify the service

To verify the service is receiving events correctly, make a test change and confirm delivery at your endpoint:

  1. Make a change to an asset in CMP on the UAT environment.

  2. Wait up to one minute for the next delivery interval to elapse.

  3. Confirm the webhook payload is received at your endpoint.

  4. Check that the payload structure matches your expectations — see Asset event webhook service reference for the expected payload structure.

If no payload is received:

  • Confirm your endpoint URL is correct and publicly accessible.

  • Confirm your endpoint returns a 2xx HTTP response on receipt.

  • If the issue persists, contact App Support.

Related pages