Connect Mercury to Rig

    Mercury is a business bank, and its API gives Rig read access to your accounts and every transaction on them. Rig syncs both into your warehouse so cash and spend questions sit beside your other finance data. Mercury connects with a read-only API token.

    Before you start

    • You need a Mercury user who can create API tokens. If you do not see the option in settings, ask an admin, usually whoever set up the Mercury account.
    • Create a Read Only token. Rig only reads, and Mercury does not ask for an IP whitelist on read-only tokens.

    Step 1: Create a read-only Mercury API token

    1. Sign in to Mercury, click your organisation name at the top left and choose All Settings.
    2. In the left-hand navigation, open Tokens.
    3. Click Create an API Token and choose the Read Only permission tier.
    4. Copy the token before closing the dialog. Mercury cannot show it again.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Mercury, open the card and click Connect.
    3. Mercury API token: Paste the whole token, exactly as Mercury shows it.
    4. Earliest transaction date (YYYY-MM-DD): The first date to load transactions from. Leave 2020-01-01 as it is for everything since then, or enter a later date for less history.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Mercury lands in its own mercury schema in your warehouse:

    • Accounts: your Mercury accounts.
    • Transactions: the transactions on those accounts, from the earliest date you set.

    Good to know

    • Mercury has three token tiers: Read Only, Read and Write, and Custom. A Read and Write token needs an IP whitelist, and Rig has no use for one.
    • Mercury deletes tokens that sit unused. Any request made with a token prevents that, so a scheduled sync keeps the token in use.
    • If a token leaks, revoke it in Mercury and create a new one, then update it in Rig.
    • To disconnect Mercury, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Track cash balance and runway
    • Categorise and analyse spend
    • Monitor large and unusual transactions

    More ideas for using Mercury

    Mercury documentation

    Was this guide helpful?