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 → SIGNINGimport { MerkleVault } from "@merklevault/sdk";
const mv = new MerkleVault({ apiKey: process.env.MV_API_KEY });
const tx = await mv.transactions.create({
vaultId: "vlt_ops",
asset: "USDC_ETH",
amount: "9500.00",
destination: { type: "allowlist", id: "dst_vendor_12" },
});
// tx.status === "AUTO_APPROVED"from merklevault import MerkleVault
mv = MerkleVault(api_key=os.environ["MV_API_KEY"])
tx = mv.transactions.create(
vault_id="vlt_ops",
asset="USDC_ETH",
amount="9500.00",
destination={"type": "allowlist", "id": "dst_vendor_12"},
)
# tx.status == "AUTO_APPROVED"client := merklevault.New(os.Getenv("MV_API_KEY"))
tx, err := client.Transactions.Create(ctx, &merklevault.TxRequest{
VaultID: "vlt_ops",
Asset: "USDC_ETH",
Amount: "9500.00",
Destination: merklevault.Allowlist("dst_vendor_12"),
})
// tx.Status == "AUTO_APPROVED"From sandbox keys to a signed testnet transfer.
The sandbox runs on testnets with the same policy engine and signing flow as production.
Create an API key
In the console, create a key with the API signer role and choose which vaults it can use.
Run your share
Start the co-signer container on your own infrastructure. It holds share A and talks only to our signing service.
Write a policy
Allow the key to auto-sign under a limit to allow-listed addresses. Everything else waits for people.
Send and listen
Create a transfer and receive a webhook as it moves through each state.
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 states
{
"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)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/sdkPython
Sync and async clients for scripts, back-office jobs and notebooks.
pip install merklevaultGo
A small, dependency-free client for high-throughput services.
go get merklevault/goCo-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.
The main objects you will work with.
| Resource | What it is | Key endpoints |
|---|---|---|
| Vaults | A group of addresses that share one MPC key set and policy scope | GET /v1/vaults · POST /v1/vaults |
| Wallets | An asset and address inside a vault, or a customer's embedded wallet | POST /v1/wallets · GET /v1/wallets/:id |
| Transactions | A transfer, contract call or message signature, with its approval state | POST /v1/transactions · GET /v1/transactions/:id |
| Policies | The ordered rule set that decides allow, require approval or block | GET /v1/policies · POST /v1/policies/dry-run |
| Destinations | Approved addresses and network counterparties | GET /v1/destinations · POST /v1/destinations |
| Audit log | Hash-chained record of every action, verifiable offline | GET /v1/audit · GET /v1/audit/proof/:id |
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.