Skip to main content

Getting started with Webhooks and Okendo

Send real-time event data from Okendo to any platform in your tech stack using webhooks, including ESPs, CRMs, analytics tools, and middleware platforms like Zapier.

Written by Simon Mainwaring

Webhooks let you send real-time data from Okendo to any platform in your tech stack β€” even when there is no native integration. Each time a customer event occurs in Okendo, a webhook fires a POST request to an endpoint you control, delivering the event data instantly.

You can use Okendo webhooks with email platforms (ESPs), CRMs, analytics tools, data warehouses, CDPs, helpdesks, and middleware platforms like Zapier.

Before you begin

πŸ’‘ Webhooks are available on Advanced and above plans for Reviews, Loyalty, Quizzes and Surveys.

⚠️ Developer support is recommended for setting up webhooks. Your team will need to build and maintain an endpoint to receive event data, or use a middleware tool like Zapier.

Your team will need to:

  1. Set up an endpoint to receive event data in your platform of choice β€” or use a middleware tool like Zapier.

  2. Subscribe to webhook events using the Okendo API (via Postman or code).

  3. Test and verify that events are being sent and received correctly.

πŸ’‘For full technical details, refer to the Okendo developer documentation.

In this article, you will learn about;


What you can do with Okendo webhooks

Webhooks are available across Reviews, Loyalty, Quizzes, and Surveys. Common use cases include:

  • Sending review or survey data to your ESP to create segments or trigger automated flows

  • Logging loyalty transactions in a CRM to track member activity

  • Pushing quiz responses β€” including product recommendations β€” to downstream marketing or personalization tools

  • Sending survey data to an analytics platform or data warehouse for deeper attribution analysis

  • Automatically creating support tickets when negative feedback is submitted

  • Notifying teams in real time when specific events occur

πŸ’‘ If your team doesn't have developer resources, a middleware tool like Zapier can receive Okendo webhook events and route them to other platforms without custom code.


Available events by product

Reviews

Webhooks fire when a review is:

Event

Description

Created

A customer submits a review. The most common use case.

Updated

An existing review is updated.

Deleted

A review is removed from the database.

Data included: review details (ID, product, variant), review content (title, body, rating, sentiment, profanity flag, date), product attributes, reviewer info (name, email, verified status, location, avatar), attached media, review reply, reward offered, review status, helpful/unhelpful count, and applied tags.

Loyalty

Webhooks fire for the following Loyalty events:

Event

Description

Loyalty Member Created / Updated / Deleted

A member joins, has their record updated, or is removed. Includes points balance, VIP tier, enrolled date, tier expiry, and birthday.

Loyalty Transaction Adjustment Created / Updated / Deleted

A manual adjustment is made to a member's points.

Loyalty Earning Transaction Created / Updated / Deleted

A member earns points through an action. Includes action, points amount, and notification text.

Loyalty Redemption Transaction Created / Updated / Deleted

A member redeems points. Includes reward, points spent, and notification text.

Quizzes

Webhooks fire when a quiz response is:

Event

Description

Created

A customer submits a quiz response.

Updated

An existing response is updated β€” for example, when an email is added on the recommendation page to receive a coupon.

Deleted

A response is removed from the database.

Data included: quiz name, quiz ID, response ID, date, customer email and ID, order ID, marketing opt-in status, answered questions, product recommendations (including variant IDs, runner-up products, and points allocations), and reward or incentive offered.

Surveys

Webhooks fire when a survey response is:

Event

Description

Created

A customer submits a survey response.

Updated

An existing response is updated β€” for example, when an email is added on the outro page to receive a coupon.

Deleted

A response is removed from the database.

Data included: survey name, survey ID, response ID, date, channel, customer email and ID, order ID, marketing opt-in status, answered questions, and reward or incentive offered.


How to set up webhooks

Webhook configuration is done through the Okendo API. Refer to the technical documentation for full setup details:


Product-specific guides

For event details and setup guidance specific to each product, see:


FAQs & limitations

Q. Do I need a developer to set up webhooks?

A. No, but it will help β€” webhook configuration requires API access and a server endpoint to receive events. If you don't have developer resources, a middleware tool like Zapier can receive Okendo webhook events without custom code.

Q. Which Okendo products support webhooks?

Webhooks are available for Reviews, Loyalty, Quizzes, and Surveys.

Q. Can I subscribe to multiple event types at once?

A. Yes β€” each product exposes Created, Updated, and Deleted events separately. You can subscribe to any combination across any products.

Did this answer your question?