Overview
The Management API is how your systems act on a Walley order once it has been created. Capture it when you ship, refund it when goods come back, change it before it leaves the warehouse, and read its current state whenever you need to. It works the same way no matter which Walley product created the order.
What you can doβ
π Get order
Read an order and everything on it: items, addresses, invoices and current status. Start here when you need to know what an order accepts next.
π¦ Capture order
Confirm what you ship, in full or item by item. Capturing is what triggers the payout and creates the invoice for the customer.
πΈ Refund order
Give money back after capture, for the whole order, for single items, or as an adjustment when you only need to correct the amount.
βοΈ Reauthorize order
Change the items or the amount before anything is captured. Use it to add, remove or replace rows while the order is still in the warehouse.
π« Cancel order
Release every item you have not captured. The customer is not charged and the reservation is returned.
Common use casesβ
Recipes that walk through a real scenario end to end, from the first call to the final state of the order.
π Change an order
Adjust items and amounts before delivery.
π Deliver in parts
Ship what you have and keep the rest reserved.
β©οΈ Refund a delivered order
Return goods and pay the customer back.
Start hereβ
- Quickstart takes you from credentials to your first response in about five minutes.
- Endpoints lists the test and production base URIs.
- Authentication walks through the OAuth2 client credentials flow. You create the API key in Merchant Hub.
- Order lifecycle explains the statuses that decide which of the actions above an order accepts.
- Asynchronous operations explains why a change is not visible the moment Walley accepts it, and how to retry safely.
Getting accessβ
Your organization needs access to the Management API before you can create an API key. Contact Merchant Services to get set up.