API

/

Webhook

Webhook

Connect a webhook to receive application events in real time.

Register Webhook

Receive notifications via webhook when an event occurs.

You can view the full list of events in the Webhook Events section.

New event types are continuously added, and you can choose which events to handle and how.

However, when implementing event listeners, you must ensure that the system continues to operate correctly.

When an event occurs, an HTTP POST request is sent to the configured webhook URL, allowing you to perform subsequent actions accordingly.

<It is recommended to maintain idempotency in your webhook handler to prevent the same event from being processed multiple times.>

Webhook events are attempted to be delivered once to the specified URL. If delivery fails (due to a timeout or an HTTP response code other than 200), they are retried up to three times using an exponential backoff algorithm. Events are executed immediately upon creation.

<It is recommended to use the eventId as an idempotency key to ensure that retried events are not processed multiple times.>

Webhook registration is only available through the MORI BIZ dashboard.

Webhook Security (Optional)

Payload Verification

When an API key is set, MORI generates an HMAC SHA-256 hash signature using the entire webhook request payload. This signature is hex-encoded and included in the X-Mori-Signature header when the request is sent.

Load external public images and apply the Anti-AI filter.

· Match: The request has passed verification.

· Mismatch: The request may have been tampered with or forged during transmission.

Webhook Events

Events are used to record significant changes to resources.

Once an event is created, it is delivered via a webhook call.

Event Type:

{{RESOURCE}}.{{FEATURE}}.{{EVENT}}

Event Type

Description

ORDER.ANTI_AI.PROCESSED

Occurs when a watermarking order has been completed.

{

"eventId": "7dddea77-232c-4ae7-a880-ba9e11563762",

"eventType": "ORDER.ANTI_AI.PROCESSED",

"occuredAt": "2024-01-01T12:00:00.000Z",

"data": {

"orderId": 123456789,

"createdAt": "2024-01-01T11:00:00.000Z",

"updatedAt": "2024-01-01T12:00:00.000Z",

"status": "complete"

}

}

API

/

Webhook

Webhook

Connect a webhook to receive application events in real time.

Register Webhook

Receive notifications via webhook when an event occurs.

You can view the full list of events in the Webhook Events section.

New event types are continuously added, and you can choose which events to handle and how.

However, when implementing event listeners, you must ensure that the system continues to operate correctly.

When an event occurs, an HTTP POST request is sent to the configured webhook URL, allowing you to perform subsequent actions accordingly.

<It is recommended to maintain idempotency in your webhook handler to prevent the same event from being processed multiple times.>

Webhook events are attempted to be delivered once to the specified URL. If delivery fails (due to a timeout or an HTTP response code other than 200), they are retried up to three times using an exponential backoff algorithm. Events are executed immediately upon creation.

<It is recommended to use the eventId as an idempotency key to ensure that retried events are not processed multiple times.>

Webhook registration is only available through the MORI BIZ dashboard.

Webhook Security (Optional)

Payload Verification

When an API key is set, MORI generates an HMAC SHA-256 hash signature using the entire webhook request payload. This signature is hex-encoded and included in the X-Mori-Signature header when the request is sent.

Load external public images and apply the Anti-AI filter.

· Match: The request has passed verification.

· Mismatch: The request may have been tampered with or forged during transmission.

Webhook Events

Events are used to record significant changes to resources.

Once an event is created, it is delivered via a webhook call.

Event Type:

{{RESOURCE}}.{{FEATURE}}.{{EVENT}}

Event Type

Description

ORDER.ANTI_AI.PROCESSED

Occurs when a watermarking order has been completed.

{

"eventId": "7dddea77-232c-4ae7-a880-ba9e11563762",

"eventType": "ORDER.ANTI_AI.PROCESSED",

"occuredAt": "2024-01-01T12:00:00.000Z",

"data": {

"orderId": 123456789,

"createdAt": "2024-01-01T11:00:00.000Z",

"updatedAt": "2024-01-01T12:00:00.000Z",

"status": "complete"

}

}