Webhooks
Subscribe to real-time events on Countercyclical with webhooks.
Last updated
Subscribe to real-time events on Countercyclical with webhooks.
Last updated
Webhooks are user-defined HTTP callbacks that are triggered by specific events on the platform. When such an event occurs, the platform makes an HTTP POST request to the URL you have configured for the webhook. This allows you to receive immediate notifications and take appropriate actions based on the event data.
First, you need to set up a URL on your server that can accept incoming HTTP POST requests. This URL will be the endpoint that our platform sends webhook events to.
To register a webhook, follow these steps:
Log in to your Enterprise account on the platform.
Go to the Settings > Workspace > Advanced > Developers
Scroll to the Webhooks
section.
Click on the Create Webhook
button.
Fill in the required details:
Name: A name for your webhook (e.g., "New Report Published")
URL: The subscriber endpoint URL where you want to receive the webhook events
Events: Select the events you want to subscribe to
Once you have filled in all the details, click Save
.
You can manage your webhooks through the platform's Webhooks section:
Edit Webhooks: Modify the details of an existing webhook (e.g., change the URL or events).
Delete Webhooks: Remove a webhook if you no longer need it.
View Logs: Access logs to see the history of webhook events sent to your endpoint.
Below you can find an example of what a common payload will look like, along with the supported events we have on Countercyclical.
Like API Keys, Webhooks created on the platform are scoped based on the user's permission in the workspace.
For the greatest possible visibility across all supported events, we'd recommend having a workspace owner or admins create & manage webhooks. For more information on roles, please see Permissions
Here is a list of supported webhook events across the platform:
To ensure the security of your webhook, consider the following:
Validate the Source: Verify that the incoming requests are actually coming from our platform. This can be done by checking the request headers or using a shared secret.
Use HTTPS: Ensure your webhook URL uses HTTPS to encrypt the data in transit.
Rate Limiting: Implement rate limiting to prevent abuse of your webhook endpoint.
Please feel free to reach out to us at if you have any questions or suggestions
investment.created
: Action taken when an is created
investment.updated
: Action taken when an is updated
investment.deleted
: Action taken when an is deleted
valuation.created
: Action taken when a is created
valuation.updated
: Action taken when a is updated
valuation.deleted
: Action taken when a is deleted
memo.created
: Action taken when a is created
memo.updated
: Action taken when a is updated
memo.deleted
: Action taken when a is deleted
team.created
: Action taken when a is created
team.updated
: Action taken when a is updated
team.deleted
: Action taken when a is deleted
assumption.created
: Action taken when an is created
assumption.updated
: Action taken when an is updated
assumption.deleted
: Action taken when an is deleted
pipeline.created
: Action taken when a is created
pipeline.updated
: Action taken when a is updated
pipeline.deleted
: Action taken when a is deleted
Please reach out to us as if you'd like to see us add any additional events