For the complete documentation index, see llms.txt. This page is also available as Markdown.

Events & Webhooks

Overview

Origin Studio publishes event notifications when changes occur within your tenant.

Events are delivered via AWS Simple Notification Service (SNS) to a subscriber endpoint configured for your tenant.

You can use these events to:

  • Trigger downstream workflows

  • Synchronize external systems

  • React to record lifecycle changes

  • Automate enrichment or publishing pipelines


How Event Delivery Works

  1. A change occurs in Origin Studio (e.g., record created).

  2. An event is published to your tenant’s SNS topic.

  3. SNS delivers a notification to your subscribed webhook endpoint.

  4. Your system processes the event payload.


Supported Event Types

Examples:

Event
Description

record.created

A new record has been created

record.updated

Workflow status changed


Event Payload Structure

Events are delivered using the AWS SNS Notification format.

The HTTP request your endpoint receives contains:

  • SNS headers

  • A JSON body containing the SNS envelope

  • The actual Origin Studio event inside the Message field


Example SNS Headers

These headers identify:

  • The SNS topic

  • The subscription

  • The message type


Example SNS Body (Envelope)

Your endpoint receives a JSON document like this:


Extracting the Actual Event

The Origin Studio event is contained inside the Message field.

Important:

The Message field is a JSON string, not a nested object.

It must be parsed a second time.


Decoded Event Payload

After parsing the Message field:


Event Payload Fields

Field
Description

event

Event type

id

Record ID

new

New state (for update events)

old

Previous state (if applicable)


Example: record.created


Configuring Your Webhook Endpoint


SNS Subscription Confirmation

When first subscribing, SNS may send a SubscriptionConfirmation message.

Example:

You must confirm the subscription by visiting the SubscribeURL.


Security & Validation

To ensure the message is authentic:

  • Validate the SNS signature using SigningCertURL

  • Confirm the TopicArn matches your expected tenant topic

  • Reject unknown topics

Refer to AWS SNS documentation for signature validation best practices.


Retry & Delivery Behavior

  • SNS retries failed deliveries

  • Retry timing follows AWS SNS retry policy

  • Events are delivered at-least-once

  • Your system should handle idempotency

Recommended:

Use the MessageId or record id + event type to prevent duplicate processing.

Last updated