Skip to main content

Overview

Bluvo webhooks notify your application in real-time when events occur — wallets connecting, balances updating, withdrawals completing, and more. Instead of polling the API, your server receives an HTTP POST with a signed JSON payload the moment something happens. Webhooks are managed through the Bluvo Portal. There is no REST API for webhook management — all configuration (creating endpoints, selecting events, rotating secrets) is done in the dashboard.

Supported events

Creating a webhook endpoint

1

Open the Webhooks page

In the Bluvo Portal, navigate to Settings > Webhooks.
2

Add an endpoint

Click Add Endpoint, enter the URL of your receiver, and select the events you want to subscribe to.
3

Copy your signing secret

After creation, copy the webhook signing secret. You’ll need this to verify signatures. Store it securely — it won’t be shown again.
You can create up to 3 webhook endpoints per project.

Payload structure

Every webhook delivery sends a POST request with a JSON body following this envelope:

Headers

Each delivery includes two signature headers:

Building a receiver

Here’s a minimal Express.js receiver that verifies the signature and processes events:
Always use express.raw() or equivalent to access the raw request body for signature verification. Parsing the body as JSON first will alter the string and break the signature check.

Idempotency

Use the eventId field to deduplicate deliveries. The same event may be delivered more than once (e.g., if your server returns a timeout before Bluvo receives the 200 response). Your receiver should be idempotent — processing the same eventId twice should have no side effects.

Next steps

Verify Signatures

Secure your endpoint with HMAC-SHA256 verification.

Retries & Logs

Understand the retry schedule and view delivery logs.

Event Reference

Browse detailed payload schemas for every event.