Send VeriProof notices to your own systems

Have VeriProof notify your own systems when a review is created, reassigned, decided, or overdue, and route that work through whatever tools your team runs.

Used by
Developers and administrators
What's shared
Notices from VeriProof to a web address you choose.
Set up by
A VeriProof administrator adds the address; your developers build what receives it

What you can be notified about

Review work

A review is opened, reassigned, decided, canceled, or overdue, or needs more information. You also hear whether the application received the decision.

Agent activity

An agent finishes a task, does something unusual, breaks a rule, or changes health status.

Applications and evidence

An application is added, approved, or retired, an evidence pack is ready, or a request to delete personal data is complete.

You choose which notices go to each address, and for which applications.

Notify reviewers your own way

By default, VeriProof tells reviewers about new work by email, and in Slack or Teams when they're connected. For any application, you can hand that job to your own tools instead. The Inbox, due dates, and escalation keep working as usual.

If your system can't take a new or reassigned review, VeriProof emails the reviewer itself and tells your administrators. The review's history shows who sent each notice.

A webhook tells you something changed. Reviewers still record every decision in VeriProof, where their authority is checked.

Security

Every notice is signed, so your system can confirm it came from VeriProof before acting on it. VeriProof sends notices only after your system proves it controls the address.

Notices carry IDs, dates, and short labels, never prompts, AI responses, reviewer comments, or personal data. When your system is allowed to see more, it looks up the review in VeriProof with its own key.

VeriProof sends only to secure public web addresses. If your system misses a notice, VeriProof keeps retrying for up to three days, and you can resend any notice from the delivery history.

Set up a webhook

An administrator who manages integrations adds the address. Your developers build the part that receives notices, using the checks included in VeriProof's TypeScript, Python, Go, and Rust developer kits.

  1. Add the address

    In Settings → Integrations → Webhook delivery, enter the web address and choose the notices and applications it covers.

  2. Confirm the address

    VeriProof sends a signed test. Your system checks the signature and replies, and notices start once it passes.

  3. Save each notice, then reply

    Your system saves each notice and replies within 10 seconds. The webhook guide covers signing options and exact formats.

Send review work where your team already looks

We'll help you pick the notices that fit the tools your reviewers and operators already use.