# Refund API, webhooks and automations for developers > Send signed refund webhooks to your tools, call the REST API and let your AI assistant work with Lumtry cases over MCP. Explore the developer tools. - Canonical URL: https://lumtry.com/developers - Last updated: 2026-09-24 ## Put refunds to work in the tools you already use. Send refund events to the tools you already use, and let your AI assistant or your own code work with Lumtry cases. Three ways in, one set of rules. Your AI assistant, your apps and your other systems see the same cases, and nothing skips your approvals. - **MCP server**: Let an AI assistant read cases and propose decisions over the Model Context Protocol. - **Public API**: Four operations to open, list, read and update refund cases with a workspace API key. - **Webhooks**: 13 signed event types pushed to your endpoint, retried and replayable. ### Open a case from your own code. A small, stable surface for cases, authenticated with a workspace API key. The reference is served by your API at /public/v1/docs. - Open a refund case. A duplicate key returns the original case with 200. - List your workspace's cases. - Read one case with its state and items. - Record that the return arrived. - Idempotency-Key on every POST, kept for 24 hours. A reused key with a different body returns 409. - X-Correlation-ID is echoed back, or generated for you, on every response. - X-RateLimit headers on every response. Plan ceilings: Free 120, Starter 600, Growth 1,200 and Scale 2,400 requests per minute. ### Every event, signed and retried. Owners and Admins add endpoints in the dashboard. Each delivery is signed, sequenced and retried at 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours before it is dead-lettered and can be replayed. - Refund cases - Approvals - Labels and agents Reject a timestamp more than 5 minutes old, then compare the HMAC in constant time. Every provider that sends Lumtry a webhook is checked against its own signature scheme first. An invalid signature gets a 401 and no business processing. ### Know what your rules will do, before they run. Two ways to work on your policy without touching a live case. - **Simulate a policy**: Replays your recent decisions through a draft policy, with no model call. Free on every plan. - **Explain a miss**: Drafts one candidate rule fix that lands as a pending suggestion. It never publishes on its own, and needs the AI rule suggestions entitlement. ## Related - [Home](https://lumtry.com/index.md): Decide refunds by a versioned policy, send the exceptions to your team in Slack or the dashboard, and keep every step on the record. Start free. - [MCP server](https://lumtry.com/developers/mcp.md): Connect an AI assistant or your own agent to your refund workspace through the Model Context Protocol. Read cases and propose actions, never move money. - [Features](https://lumtry.com/features.md): Versioned refund policy, AI reasoning only where rules leave room, Slack and dashboard approvals, Stripe and PayPal execution and a full audit trail. See it all. - [Pricing](https://lumtry.com/pricing.md): Lumtry plans by case volume and seats, from Free to Enterprise, with add-ons and capped outcome fees. Start free or hear when billing opens. - [About](https://lumtry.com/about.md): Why Lumtry exists: refunds should be decided by a policy you can defend, reasoning you can inspect and approvals your team controls. Read the story. - [Privacy](https://lumtry.com/privacy.md): How Lumtry collects, uses, shares and protects personal information, isolates tenant data, records AI rationale and lists sub-processors. Read the policy. - [Terms](https://lumtry.com/terms.md): The binding terms for using Lumtry: policy plus AI reasoning with a human approval gate, plans and billing, and the limits of liability. Read them in full. - [Trust](https://lumtry.com/trust.md): How Lumtry secures merchant data, keeps AI inside a deterministic refund policy, lists every sub-processor and explains data flow and retention. Review it. - [Solutions](https://lumtry.com/solutions.md): Four ways Lumtry puts policy, approvals and an audit trail around the money you give back: refunds, returns and labels, chargebacks, retention and abuse. - [Demo](https://lumtry.com/demo.md): Run a sample refund through intake, AI signals, policy, approval and audit in your browser. Change a rule, rerun the case and share the link. Try it now. - [Integrations](https://lumtry.com/connectors.md): Connect Lumtry to Shopify, WooCommerce, BigCommerce, Amazon, eBay, Stripe, PayPal, Slack, Gorgias, Zendesk, EasyPost and Shippo. Browse every integration. - [Contact](https://lumtry.com/contact.md): Questions about Lumtry, launch pricing, integrations or security? Send a message and the team replies by email. Tell us about your refund volume. - [Get started](https://lumtry.com/get-started.md): Pick the refund problem to fix first, choose a plan and create your Lumtry account. Start on the Free plan and connect your store when you are ready. - [Refund cost calculator](https://lumtry.com/calculator.md): Estimate a year of manual refund handling and return abuse leakage from your own numbers, then see which Lumtry plan fits your volume. Run the numbers. - [Roadmap](https://lumtry.com/roadmap.md): What Lumtry has shipped, what is coming next and what is further out across refunds, returns, disputes and integrations. Get notified when items ship. - [Compare](https://lumtry.com/compare.md): Lumtry side by side with the tools SMB merchants use for refunds today, built from each vendor's own public pages. Find the right fit for your store. - [Guides](https://lumtry.com/guides.md): Answer-first guides to refunds, returns, chargebacks, approvals and audit trails for Shopify, WooCommerce and BigCommerce merchants. - [Glossary](https://lumtry.com/glossary.md): Plain definitions of refund, return, chargeback, RMA, store credit, audit trail, idempotency key, MCP and other refund operations terms. - [llms.txt](https://lumtry.com/llms.txt)