Developers

Build on keys younever have to hold.

A REST API, signed webhooks and SDKs for Node, Python and Go. Your policies and approvals apply to every API call, so automation never means giving up control.

curl https://api.merklevault.io/v1/transactions \
  -H "Authorization: Bearer $MV_API_KEY" \
  -H "Idempotency-Key: vendor-12-2026-11" \
  -d '{"vault_id":"vlt_ops","asset":"USDC_ETH",
       "amount":"9500.00",
       "destination":{"type":"allowlist","id":"dst_vendor_12"}}'

# 202 Accepted · status: AUTO_APPROVED → SIGNING
Quickstart

From sandbox keys to a signed testnet transfer.

The sandbox runs on testnets with the same policy engine and signing flow as production.

Step 1

Create an API key

In the console, create a key with the API signer role and choose which vaults it can use.

Step 2

Run your share

Start the co-signer container on your own infrastructure. It holds share A and talks only to our signing service.

Step 3

Write a policy

Allow the key to auto-sign under a limit to allow-listed addresses. Everything else waits for people.

Step 4

Send and listen

Create a transfer and receive a webhook as it moves through each state.

Webhooks

Know the moment anything changes.

Every state change sends a signed event to your endpoint, with retries and a replay tool in the console.

transaction.pending_approvaltransaction.signedtransaction.confirmedtransaction.blockeddeposit.receivedpolicy.changed

Transaction states

1. SUBMITTED2. PENDING_POLICY3. PENDING_APPROVAL4. AUTO_APPROVED5. SIGNING6. BROADCAST7. CONFIRMED
{
  "type": "transaction.confirmed",
  "id": "evt_31b0…",
  "created_at": "2026-11-18T14:02:11Z",
  "data": {
    "transaction_id": "tx_8f2c…",
    "vault_id": "vlt_ops",
    "signers": ["client", "merkle_vault"],
    "tx_hash": "0x9b4e…c07a",
    "confirmations": 12
  }
}
# Header: MV-Signature: t=…, v1=… (HMAC-SHA256)
SDKs and tools

Use the language you already ship.

Official clients for the languages fintech teams ship most. Package names are final at general availability.

Node and TypeScript

Typed client with automatic retries and idempotency keys.

npm i @merklevault/sdk

Python

Sync and async clients for scripts, back-office jobs and notebooks.

pip install merklevault

Go

A small, dependency-free client for high-throughput services.

go get merklevault/go

Co-signer

The container that holds your share A, for Docker or Kubernetes, with HSM support.

Webhook verifier

Helpers in every SDK to check event signatures and reject replays.

OpenAPI spec

Generate a client in any language from the published specification.

API resources

The main objects you will work with.

ResourceWhat it isKey endpoints
VaultsA group of addresses that share one MPC key set and policy scopeGET /v1/vaults · POST /v1/vaults
WalletsAn asset and address inside a vault, or a customer's embedded walletPOST /v1/wallets · GET /v1/wallets/:id
TransactionsA transfer, contract call or message signature, with its approval statePOST /v1/transactions · GET /v1/transactions/:id
PoliciesThe ordered rule set that decides allow, require approval or blockGET /v1/policies · POST /v1/policies/dry-run
DestinationsApproved addresses and network counterpartiesGET /v1/destinations · POST /v1/destinations
Audit logHash-chained record of every action, verifiable offlineGET /v1/audit · GET /v1/audit/proof/:id
Developer FAQ

Before you write a line.

Is there a sandbox?

Yes. The sandbox runs on testnets with the same API, policy engine, approval flow and webhooks as production, so code you write against it works unchanged when you switch keys.

Do API transfers bypass approvals?

Never. An API key is just another initiator. Policies decide whether its request is auto-approved, sent to a human quorum or blocked, exactly as for a console user.

What is the co-signer?

A small container you run on your own infrastructure that holds your key share (share A). It talks only to the Merkle Vault signing service over mutually authenticated TLS and can use your HSM. Enterprise customers can run it fully on-premises.

How are webhooks secured?

Every event is signed with HMAC-SHA256 and includes a timestamp. The SDKs include a verifier that checks the signature and rejects replays outside a five-minute window.

Your first testnet transfer is one afternoon away.

Tell us what you're building and we'll send sandbox keys and a co-signer image.