Orders
data: The order, as Get an order answers it, with payments, every payment opened for it, and invoice where the store raised it as one.
Reviews
data: orderId, productId, email, and review with its rating, message, automatic and dateCreated. review.removed and review.flag_declined add reviewId and flag, the flag as List reviews answers it, with Shoply’s answer.
Stock
data: productId, productName, variantId, variantName, available (what is left) and threshold (the store’s low stock number).
Catalogue
data: The product, as Get a product answers it. product.deleted has only its id and name.
Customers
data: id, emailAddress, balance, tags and dateCreated. customer.tagged and customer.untagged add tag, the one put on or taken off: id, name, tone and automatic (Shoply’s own two are vip and disputed).
Affiliates
data: The affiliate: id, customerId, emailAddress, code, commission, discount, balance, active, source and dateCreated. The two affiliate.payout_ events have the payout request, as List payout requests answers it.
Subscriptions
data: The subscription, as Get a subscription answers it.
Cart Recovery
data: The checkout that was left, as List carts answers it: state says which email it last had, and recoveredOrderId the order that paid.
Win-Back
data: The buyer, as List Win-Back buyers answers it: state says which email they last had, and wonOrderId the order that brought them back.
Subscribers
data: The subscriber, as List subscribers answers it: email, customerId, subscribed, subscribedAt, source, orderId (the order whose box was ticked), unsubscribedAt and unsubscribedBy.
Payment Routing
data: provider, name, paused, pausedAt and pausedReason, the processor as it stands after the change.
Disputes
data: The dispute, as List disputes answers it: status is how it reads on the dashboard, providerStatus what the provider last said, dueAt when it stops taking an answer.
Apps
data: id (the connection), appId, name, maker, website, scopes (what the owner approved), connectedAt, and for app.disconnected disconnectedAt and reason: seller, app, deleted, or code_reused (the app’s approval was offered twice, so its token was ended).
Support Tickets
data: The ticket, as Get a support ticket answers it without its conversation: status is open (the buyer wrote last), answered or resolved, and resolvedBy says who resolved it (store, buyer or auto). ticket.message adds message: its id, from (buyer or store), body, pictures (each one’s name, read with a key) and createdAt.
Fraud protection
data: The event, as List fraud events answers it.