Your app reacts the moment money moves.
Subscribe to events like escrow funded, task submitted and payout sent. Every payload is signed so you can verify it, and failed deliveries retry automatically with backoff - no polling required.
Wire up a webhook in three steps.
Add an endpoint
Register an HTTPS URL in your dashboard or via the API and pick the events you care about.
Verify the signature
Each delivery carries a signature header. Recompute it with your signing secret and reject anything that does not match.
Respond 2xx fast
Acknowledge quickly and do the heavy work async. A non-2xx or timeout triggers an automatic retry.
Events you can subscribe to.
The moments in a deal where your app needs to do something.
escrow.funded
Funds are held in escrow for a project - the safe signal to start work or notify a worker.
task.submitted
A worker delivered. Trigger review, kick off QA or notify the client automatically.
escrow.released
Work was accepted and escrow released - reconcile and update your own records.
payout.sent
A payout left the platform. Confirm completion to your user and close the loop.
reputation.updated
A review landed and a reputation score changed - refresh profiles and rankings.
identity.verified
A user cleared KYC/AML. Unlock features that require a verified identity.
Built for delivery you can trust.
Signed, retried and idempotent - the three things webhook integrations usually get wrong.
Signed, every time
Each payload is signed with your endpoint secret. Verify the signature before acting, so you only ever process events that genuinely came from Internetivo.
See verificationRetries with backoff
If your endpoint is down or slow, deliveries retry on an increasing backoff schedule until they succeed or expire - so a brief outage never loses an event.
Why webhooks beat polling.
Real-time, efficient and safe.
Instant
React the moment an event happens instead of polling the API on a timer and lagging behind.
Efficient
No wasted requests checking for changes that have not happened - the network pushes only what matters.
Idempotent
Each delivery carries a unique id. Dedupe on it so a retried event is processed exactly once.
Secure
HTTPS plus signature verification means only genuine, untampered events reach your code.
Webhook questions.
How do I verify a payload is genuine?
Every delivery includes a signature computed from the body and your endpoint signing secret. Recompute it on your side and compare - if it does not match, reject the request. The SDK ships a one-line helper for this.
What happens if my endpoint is down?
Deliveries retry automatically on an increasing backoff schedule until they succeed or the retry window expires. You can also replay recent events from the dashboard.
Will I ever get the same event twice?
Possibly - retries and network conditions can cause duplicates. Each event has a unique id, so dedupe on it to keep processing exactly-once.
How fast must I respond?
Return a 2xx quickly. Do your real work asynchronously - a slow response or a non-2xx is treated as a failure and retried.
Stop polling. Start listening.
Register an endpoint, verify the signature and let the network push escrow and payout events straight to your app.