← Go back

Guide // MandateGuard

How do webhook notifications work for agent spend approvals?

By the Ingenious AI team · Published 2026-11-14 · Reviewed 2026-11-14

▸ Run the free live demo See pricing

Free covers 1 agent and 1 policy with the full authorize flow, signed receipts and the approval inbox — no card required to start.

Short answer

Webhook notifications solve the approval queue's real problem — latency. When an agent's request returns REQUIRE_APPROVAL, MandateGuard can notify your configured https webhook so the pending decision surfaces in the channel your team already watches, instead of waiting for someone to remember the inbox. The webhook notifies; it never decides. Approval still happens in the inbox or via the API and still releases a bound one-time token. Set the webhook up before go-live, test it with a deliberate over-threshold purchase, and keep the daily inbox check as the backstop for when notifications fail.

What does the approval webhook do?

MandateGuard's workspace webhook is an https URL you configure on the workspace that receives approval notifications — when a spend needs a human decision and when decisions resolve. It is a notification channel, not an approval channel: the decision itself is made by a person through the inbox or API, and approval releases the bound one-time token. The webhook exists so that the moment an agent's purchase starts waiting on a human, the humans find out where they already work.

The latency problem webhooks solve

Approval thresholds create a queue, and queues fail by latency, not by judgement: the decision takes thirty seconds, but discovering the decision is needed takes a day. An agent whose purchase waits overnight teaches its operators to pre-approve informally, raise thresholds carelessly or route purchases around the agent entirely. The webhook attacks the latency directly by pushing the pending event to the systems your team already watches — an ops channel, a ticketing integration, an internal dashboard. The decision stays human and considered; it simply happens while the context is fresh and the agent's work is still warm.

What the webhook is — and is not

Precision about the boundary keeps the control honest. The webhook is an outbound notification from MandateGuard to your https endpoint when approval events occur on your workspace. It is not a decision API, not a token delivery you should automate against, and not a substitute for the inbox. The failure mode to avoid is the enthusiastic integration that sees a pending event and pattern-matches it into an automatic approval for known vendors: that rebuilds, in your own code, exactly the unsupervised spending the mandate exists to prevent, with the extra danger that it looks reviewed. If a category of spend is genuinely routine, the honest fix is the threshold or the policy, changed deliberately and receipted as a policy change.

Wiring it into operations

Configure the webhook URL on the workspace (https required), then build the thinnest useful handler: verify the event, post a readable card to the channel your approvers watch — vendor, amount, task reference, and a link to the inbox — and log delivery. Resist adding workflow machinery at first; a notification that reliably reaches a human beats an orchestration that sometimes does. Name the approver roster in the channel so a pending item has an owner, and agree the service expectation in plain terms: approvals are cleared during working hours, and anything waiting at day end is the first item next morning. Test the whole path with a deliberate over-threshold purchase before the agent's first real week.

Approvals on the go and the audit trail

Webhook notification pairs naturally with the inbox: the channel alerts, the inbox decides, the chain records. Because decisions and outcomes are receipted regardless of how the approver was summoned, the audit trail needs no special webhook annotation — the approval appears with its facts and timing. Timing itself is worth a periodic look: if approvals routinely take most of a day even with notifications, the bottleneck is roster or routine, not tooling. If they are consistently near-instant, check the decisions are real — open a sample of approved cards and confirm the approver could have judged them from what the card showed.

Failure handling

Design for the webhook to fail safely, because it will occasionally. If your endpoint is down, approvals still wait in the inbox and nothing spends by default; the inbox routine is the backstop, which is why it should exist even with webhooks live. Monitor handler errors and delivery gaps the way you monitor any production integration, and re-test after changing endpoints. MandateGuard validates the webhook URL's https scheme when set; keep certificates current on your side. The security posture to preserve is asymmetric: notification failures may slow spending, but must never accelerate it.

Where webhooks sit among the surfaces

MandateGuard offers four human surfaces: the inbox for decisions, the receipt views for history, verify-chain for integrity, and the webhook for timeliness. Paid plans add trust and export surfaces for review and evidence. Webhooks are the only push surface, which makes them small but load-bearing: they are the difference between a mandate that waits to be checked and a mandate that taps the approver on the shoulder. Wire them early, keep them dumb, and let the policy — not the notification layer — carry the intelligence of the system.

Five actions to take now

  1. Configure the workspace webhook URL (https) before enabling agent purchases
  2. Handle pending and decided approval events in your ops channel
  3. Keep the inbox as the decision surface — webhooks notify, humans decide there or via API
  4. Test the webhook with a deliberate over-threshold purchase
  5. Monitor webhook delivery failures like any production integration

Worked example: fifteen minutes instead of a day

A three-person team runs its purchasing agent against a webhook pointed at their ops channel. At 10:04 the channel posts: approval pending, cloud vendor, 212 dollars, task reference naming the staging expansion. The founder approves from the inbox at 10:19 between meetings. The agent redeems its token and the provisioning completes before lunch — total human time, about a minute.

Without the webhook, the same request would have waited for the founder's end-of-day inbox check, and the staging expansion would have slipped a day. The webhook did not make the decision faster by automating it; it made it faster by delivering the moment to the place a decision-maker already was.

Frequently asked questions

What events does the webhook carry?

Approval notifications for the workspace — pending approvals and their resolution — so your systems can surface waiting decisions promptly.

Can we approve from the webhook payload?

Decisions are made through the inbox or API with workspace credentials. The webhook's job is timely notification; treat auto-approval logic as a policy violation.

Must the URL be https?

Yes — MandateGuard requires webhook URLs to start with https, and validates that when you set it.

What if our endpoint is down?

The approval still waits safely in the inbox; nothing is auto-approved by silence. Monitor your endpoint and keep the inbox routine as the backstop.

Is a webhook available on the free plan?

Yes — the free plan lists webhook on approval alongside the inbox, receipts and the full authorize flow for one agent.

Keep reading

Put the policy in force: spend envelopes · intent registry · approval inbox · how the proof works · all MandateGuard guides