Connect a wallet to load your organisation's treasury.
Developers
Preview · illustrativeWire the treasury into your own systems. Scoped API keys, webhooks for authorization and settlement events, and role-based access so automation runs under the same policy as people.
API keys
| Label | Key | Scope | Created |
|---|---|---|---|
| Production · read | mw_live_7f3a…9c21 | treasury:read, cards:read | Aug 2 |
| Automation · spend | mw_live_a18b…44df | cards:read, webhooks | Jul 28 |
| Sandbox | mw_test_02c9…7be0 | all · Base Sepolia | Jul 14 |
Webhook endpoints
https://acme.xyz/hooks/mintwareActive
authorization.*, settlement.*
https://acme.xyz/hooks/policyActive
policy.updated, signer.added
Example event
// POST from Mintware → your endpoint
{
"type": "authorization.approved",
"id": "evt_2s9f…",
"data": {
"card": "•••• 4821",
"merchant": "Amazon Web Services",
"amount_usd": 4182.00,
"decided_in_ms": 118,
"settles_against": "USDC · Growth ULV"
}
}Events
authorization.approvedA card authorization cleared edge-auth within policy.authorization.declinedAn authorization was refused — over limit, blocked merchant, or frozen card.settlement.completedAn approved authorization settled on-chain against treasury liquidity.vault.rebalancedTreasury capital moved between a ULV pool and the idle buffer.policy.updatedThe quorum threshold, a spending limit, or a signer set changed.Every key and webhook runs against the Base Sepolia sandbox before it touches mainnet — replay authorization and settlement flows end-to-end without moving real value.
Illustrative. The developer platform is in development — the keys, endpoints, and events shown here are a mockup, not real credentials or a live API.