History - MX Documentation

History webhooks notify you when any new data is available after a successful history fetch. The webhook will include a count of new transactions and updated transactions. These webhooks fire only after a completed history fetch. Actions performed on the member through other endpoints will not trigger the webhook.

Field	Data type	Description
`action`	String	The action that triggered the webhook. For example, `member_data_updated`.
`completed_at`	Integer	The date and time when the process that triggered the webhook was finished.
`completed_on`	String	The date on which the process that triggered the webhook was finished.
`member_guid`	String	The unique identifier for the member that has new or updated transaction data. Defined by MX.
`transactions_created_count`	Integer	The number of newly created transactions.
`transactions_updated_count`	Integer	The number of newly updated transactions.
`type`	String	The type of webhook being delivered. Possible values include `AGGREGATION`, `BALANCE`, `HISTORY`, and `STATEMENT`.
`user_guid`	String	The unique identifier for the user. Defined by MX.

Example Payload

JSON

{
  "action": "member_data_updated",
  "completed_at": 1531947410,
  "completed_on": "2018-07-18",
  "member_guid": "MBR-48d9a481-f2a2-7e13-2685-62869cf0d33a",
  "transactions_created_count": 3,
  "transactions_updated_count": 2,
  "type": "HISTORY",
  "user_guid": "USR-eaf4ac68-d17d-5e9b-7b46-959a5b315a9e"
}