https://api.mercury.com/api/v1), using a Read Only API token that a Mercury admin creates. ConfigView sends only GET requests. It never moves money, issues cards or changes anything in Mercury.
You will end up with 1 secret (MERCURY_API_TOKEN) in ConfigView when setup is complete.
Scope of this integration today. ConfigView reads who has a Mercury login and their organization role, every card with its owner and status (virtual or physical, debit or credit, agent and single-use flags, whether a spend limit is set), the accounts (name, type, status), the organization (name, plan, billing cadence) and the webhook endpoints (target host, status, event types). It does not read balances, transactions, statements, payees, account or routing numbers, card numbers, expiry dates, names on cards, spend-limit amounts or your EIN.
What you need
- A Mercury user who is allowed to create API tokens (Settings > Tokens)
Step 1: Open the Mercury page in ConfigView
Open ConfigView in a second browser tab and leave it open:https://{companyname}.configview.com/admin/integrations/mercury
Step 2: Create a Read Only token
- In Mercury open Settings > Tokens and create a new token
- Choose the type Read Only. Read Only tokens do not need an IP whitelist, and ConfigView never writes, so do not choose Read and Write. (A Custom token with read scopes also works; scopes cannot be edited later.)
- Copy the whole token, including the
secret-token:prefix. Mercury shows it once. - In the ConfigView tab paste it into
MERCURY_API_TOKENunder Credentials and save
Step 3: Connect and verify
- Click Connect. ConfigView creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads the secret and makes one small call to the organization endpoint, then probes users, cards and webhooks.
- 401 from the organization call. The token is wrong, is missing the
secret-token:prefix, or Mercury deleted it after 45 unused days. Create a new one. - A probe shows as skipped. The token’s type or scopes do not cover that area. Nothing to fix unless you want it.
Data Tables
Each table has arun_at column and keeps only the newest run.
Things worth knowing
Leavers. The users list has no status field, so a removed person simply disappears from it. A card whose owner is no longer in the list is flagged by the catalog: check whether it should be cancelled. Roles. Mercury roles areadministrator, bookkeeper, customUser, cardOnlyUser and employee. There is no last-sign-in date in the API.
Spend limits. ConfigView stores only whether a card has a limit and how it resets, never the amount.
Rate limit. Mercury publishes no numeric limit. ConfigView paces itself at 60 requests a minute, waits as long as Mercury asks on HTTP 429, and reads lists 500 per page.
Token lifetime. Mercury deletes tokens unused for 45 days. The daily collectors count as use, so a connected ConfigView keeps the token alive.
What isn’t collected
- Transactions, statements, transfers, auto-transfer rules and payees (accounts of type
recipientare skipped) - Balances, account numbers and routing numbers
- Card numbers, last four digits, expiry, names on cards, spend-limit and budget amounts, merchant lock names
- EIN and DBA names
- Webhook signing secrets and full webhook URLs (host only)
- The events feed (it carries financial changes)