Vault Warehouse integrations
Customer-safe HTTP and MCP operations generated from the registered Vault Warehouse contract.
Vault exposes the same authorized Warehouse operations through HTTP and MCP. The operation reference is generated from the registered handlers and tools. The MCP tool schema is the matching customer-safe tool catalog.
This reference describes implemented contract shapes. A documented operation still needs current caller authority and its required verified source before it can succeed. A schema or synthetic example does not establish provider support or authorize customer go-live.
HTTP reference
Customer-scoped routes, inputs, responses, and error envelope.
Authentication and scope
Registered confidential clients, delegated MCP consent, organization keys, and immutable Test authority.
Examples
Contract-checked Warehouse reads, imports, deposit and redemption handoffs.
Outcomes and errors
Complete effects, denied calls, unknown outcomes, and bounded reads.
Product configuration
Packaging permissions, native component imports, and exact readback.
Deposits and redemptions
A player deposit through disputes and ship-back, and a mixed redemption.
Packing exceptions
Held redemption cards, per-card answers, retries and a Test walkthrough.
Polling and recovery
Deposit facts, bounded order reads, checkpoints and retry handling.
Signed event delivery
Receiver verification, durable ingestion, duplicates and polling catch-up.
What changed
Deposit and redemption changes, marked additive or breaking.
Use the environment guide for host selection and QA limits. Signed event delivery requires enabled integration setup. The polling guide also retrieves current factual deposit and order information independently of receiver delivery.