Ctrlk
Help CenterSystem StatusContact SupportYour Dashboard →
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Webhooks

Webhooks send data to your server when important events occur in your referral/affiliate program. This lets you automatically fulfill rewards or update users in your database.

If you're using an AI tool such as Cursor, Codex, Claude Code, or Antigravity to help you implement GrowSurf, we recommend utilizing our MCP server.

Example scenarios

Here are a few scenarios in which you would use webhooks:

  • If you have an internal points system, webhooks allow you to add credits to users in your database whenever a referral occurs.

  • When a new participant joins your referral or affiliate program, webhooks let you store their unique referral link (along with other participant details) in your database.

Getting started

Step 1: Add a webhook URL to your program

  1. Go to the Options step in the Program Editor.

  2. In the Set up integrations section, click the Webhooks card. Then enter your webhook endpoint URL.

  3. Publish/save your changes.

Webhooks can be configured in the Options step in the Program Editor

Tips:

  • You can test your webhook URL to see if it is set up properly and/or to see the different types of data from each webhook event. Simply click the Test button right next to the webhook URL input field.

  • You can select the specific events to receive within the advanced webhook settings section.

  • A total of 5 webhooks can be added per program.

Retry logic

If we are unable to deliver a webhook the first time, GrowSurf will attempt to redeliver your webhooks for several days with an exponential back off. After several days of failed attempts we will mark the webhook as undeliverable and it will no longer be retried.

Webhook events are stored durably, so if delivery is ever interrupted, they will be retried once service is restored. You can always check our System Status page for webhook health.

Next steps

View Examples of implementing webhooks, or view what the request payloads for webhook events look like:

Last updated

Was this helpful?