---
id: overview
title: "Overview"
sidebar_label: Overview
hide_title: true
description: "Overview of the Walley Management API for capturing, refunding and changing orders"
---

import Ingress from "../../../src/components/ingress/ingress.react";
import Link from "@docusaurus/Link";

<Ingress title="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.
</Ingress>

## What you can do

<div className="overview-cards">
  <Link className="overview-card" to="/docs/manage/orders/get">
    <h3>🔎 Get order</h3>
    <p>
      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.
    </p>
  </Link>
  <Link className="overview-card" to="/docs/manage/orders/capture">
    <h3>📦 Capture order</h3>
    <p>
      Confirm what you ship, in full or item by item. Capturing is what triggers
      the payout and creates the invoice for the customer.
    </p>
  </Link>
  <Link className="overview-card" to="/docs/manage/orders/refund">
    <h3>💸 Refund order</h3>
    <p>
      Give money back after capture, for the whole order, for single items, or
      as an adjustment when you only need to correct the amount.
    </p>
  </Link>
  <Link className="overview-card" to="/docs/manage/orders/reauthorize">
    <h3>✏️ Reauthorize order</h3>
    <p>
      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.
    </p>
  </Link>
  <Link className="overview-card" to="/docs/manage/orders/cancel">
    <h3>🚫 Cancel order</h3>
    <p>
      Release every item you have not captured. The customer is not charged and
      the reservation is returned.
    </p>
  </Link>
</div>

## Common use cases

Recipes that walk through a real scenario end to end, from the first call to
the final state of the order.

<div className="overview-cards overview-cards--compact">
  <Link
    className="overview-card overview-card--compact"
    to="/docs/manage/usecases/pre-delivery/change-order"
  >
    <h4>📃 Change an order</h4>
    <p>Adjust items and amounts before delivery.</p>
  </Link>
  <Link
    className="overview-card overview-card--compact"
    to="/docs/manage/usecases/delivery/partly-deliver"
  >
    <h4>🚚 Deliver in parts</h4>
    <p>Ship what you have and keep the rest reserved.</p>
  </Link>
  <Link
    className="overview-card overview-card--compact"
    to="/docs/manage/usecases/post-delivery/refund-order"
  >
    <h4>↩️ Refund a delivered order</h4>
    <p>Return goods and pay the customer back.</p>
  </Link>
</div>

## Start here

1. [Quickstart](/docs/manage/getting-started/quickstart) takes you from
   credentials to your first response in about five minutes.
2. [Endpoints](/docs/manage/getting-started/endpoints) lists the test and
   production base URIs.
3. [Authentication](/docs/manage/getting-started/authentication) walks through
   the OAuth2 client credentials flow. You create the API key in
   [Merchant Hub](/docs/merchanthub/access/apikeys).
4. [Order lifecycle](/docs/manage/concepts/order-lifecycle) explains the
   statuses that decide which of the actions above an order accepts.
5. [Asynchronous operations](/docs/manage/concepts/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.

:::info Contact Merchant Services
**[help@walley.se](mailto:help@walley.se)**<br />
**[+46 10 161 01 25](tel:+46101610125)**
:::
