Recipes

Recipes chain the individual Moov guides into one complete flow, from creating an account to watching the money land.

Each recipe is a sequence of API calls you can run in test mode with your own API keys. Every step shows one request with the current API version (X-Moov-Version: v2026.07.00) and links to the guide that covers that step in depth. If you haven't made an API call yet, start with the quick start and the glossary, which explains accounts, sources, payment methods, and transfers.

Before you start

All recipes assume you have:

  • A Moov account in test mode. Sign up if you don't have one.

  • An API key. Recipes run on your server, so every request uses Basic authentication with your public and secret key, which doesn't need scopes, plus the API version:

    -u "{publicKey}:{secretKey}" \
    -H "X-Moov-Version: v2026.07.00"
    

    Never send your secret key from a browser or mobile app. Client-side code such as Moov.js and Drops uses access tokens instead; see authenticate API requests.

  • To use an SDK instead of cURL, install it from SDKs and create a client with your public key as the username and your secret key as the password. Each recipe step shows only the call, using this client:

    import { Moov } from "@moovio/sdk";
    
    const moov = new Moov({
      security: {
        username: "",
        password: "",
      },
    });
    
  • Your partner account ID; see find your account ID. Transfers are created under the partner account, so POST /accounts/{accountID}/transfers uses your partner account ID.

  • A webhook endpoint, or a plan to poll. Recipes point out which webhook events to listen for at each stage.

In this section