Skip to main content

Webhook Event

This page describes the generic structure of all webhook payloads sent by Minteo.

Payload Structure

All webhooks follow this format:

NameTypeExample /
Possible values
Description
event_idstring"EVENT#123e4567-e89b-12d3-a456-426614174000"Unique identifier for the event (prefixed with EVENT#). Use this for deduplication.
hook_idstring"HOOK#2f6d8c1b-5f8f-4b3a-9d52-87a6f3bcd8c2"Unique identifier for this specific delivery attempt (prefixed with HOOK#). Changes with each retry.
event_typestring"order.updated"
"payout.updated"
"payout.item.updated"
"payin.updated"
Type of event. See Webhook Events for available types.
dataobjectvaries by event typeEvent-specific data. Structure varies by event type (see below).
signatureobject<Signature>Signature information for payload verification.
timestampinteger1530291411Unix timestamp (seconds) when this hook was sent.
sent_atstring"2018-07-18T08:35:20.000Z"ISO 8601 timestamp when this hook was sent. Same time as timestamp, different format.

signature object

NameTypeExample /
Possible values
Description
propertiesarray of strings["order.id", "order.status", "order.amount"]List of properties used to generate the checksum. Extract these dynamically.
checksumstring"124F3E92EA81EAC6DAB684035557433BA1922A7A47FED49F2001E831B5185C7E"SHA256 hash for verifying payload authenticity. See Verifying Signatures.

Data Object Structure

The data object contains the complete entity as returned by the corresponding GET endpoint:

Event TypeData FieldEquivalent API Response
order.updateddata.orderGET /orders/{id}
Complete example payload
payout.updateddata.payoutGET /payouts/{id}
Get one payout
payout.item.updateddata.payout_itemGET /payouts/{payout_id}/items/{item_id}
Get one payout item
payin.updateddata.payinGET /payins/{id}
Get one payin

HTTP Headers

All webhook requests include:

HeaderDescription
Content-TypeAlways application/json
X-Hook-ChecksumSame value as signature.checksum. Use for convenience.