Skip to main content

Webhook payload update & new order events

· 2 min read
Albert Tiñena
Albert Tiñena
Chief Technology Officer (CTO)
David Sancho
David Sancho
Principal Engineer & Technical Architect

OpenTiendas webhooks have been updated to provide a more robust and scalable event model for external integrations.

This release introduces a new webhook envelope format shared across all events, making it easier to implement idempotency, consume multiple event types from a single endpoint, and clearly separate event metadata from resource data.

It also adds the first Order webhooks, allowing external systems to react in real time to key order lifecycle changes.

A unified webhook envelope for all events​

All OpenTiendas webhooks now use a common payload structure.

{
  "event_id": "evt_123",
  "type": "order.created",
  "created_at": "2026-03-16T10:12:33Z",
  "data": {
    ...
  }
}

This new format introduces:

  • event_id: a unique event identifier, useful for implementing idempotency
  • type: the event type, allowing consumers to process multiple webhook types from the same destination URL
  • created_at: the timestamp indicating when the event was generated, useful for logging, debugging, and event tracing.
  • data: the resource payload associated with the event

This change applies to all webhooks, including already existing ones such as:

  • review.created
  • review.published

Why this change matters​

The new envelope structure makes webhook integrations more reliable and easier to scale.

It allows integrators to:

  • Detect and ignore duplicate deliveries using the event_id
  • Route logic based on type without requiring separate endpoints
  • Keep event metadata separated from the actual business resource
  • Standardize webhook handling across all current and future event types

New order webhooks​

With the Orders resource now available, OpenTiendas also introduces new webhook events related to the order lifecycle.

These events allow external systems such as ERPs, fulfillment tools, or automation workflows to react in real time to key order state changes.

The following events are now available:

  • order.created
  • order.paid
  • order.fulfilled
  • order.canceled

You can find the full list of available Order events, payload examples, and event-specific notes in the webhook reference:

👉 Webhook Events Reference

Documentation updates​

The developer documentation has been updated accordingly.

👉 Webhooks

What's next​

With the webhook system now standardized and Order events available, upcoming improvements will focus on:

  • Expanding API coverage to support broader ERP and integration use cases
  • Continuing to evolve the API as a robust integration platform

👉 API Overview