Renvias · Webhook receiving & forwarding

Services

Everything you need to never lose a webhook

Renvias sits between your platforms and your systems: it receives, stores, forwards and shows you what happened to every event.

Universal receiving

One receiving url for WhatsApp, Messenger, Instagram, Telegram, Mercado Libre, Openpay or any json.

Everything is stored

Every event is stored with its original json and headers before it is forwarded.

Multiple forwarding urls

Send the same event to your CRM, your bot and your system at the same time, without changing the format.

Automatic retries

If your url fails, Renvias keeps retrying for hours. You can also resend manually from the panel.

Identifiers

Statistics

Received, delivered, pending and failed by day, hour, identifier and platform.

Multi-company

Workspaces per client, with their own users, identifiers and urls. Ideal for agencies and integrators.

API for your system

With an API key, query what was received and the statistics, and manage identifiers and urls.

Security

Each workspace only sees its identifiers, hashed API keys, activity log and test and production environments.

How it works

Ready in four steps

Without changing your system: you only change the url you set in your platform.

Create your account

Add your identifier

The phone_number_id, page or account that sends the events.

Point your platform

Set the Renvias receiving url in your platform's webhook.

Add your urls

Choose where to forward and you are done: everything reaches your systems.

Platforms

Receive from the platforms you already use

Renvias recognizes each platform, stores the event in its collection and forwards it exactly as it arrived.

WhatsApp Business API messages and statuses by phone_number_id.

Messenger

Messages from your Facebook page.

Instagram

Direct messages from your Instagram account.

Updates from your bot with the identifier in the url.

Mercado Libre

Order, question and shipping notifications from your account.

Openpay

Charge and payment notifications.

Renvias does not modify your events: your system receives each platform's original json.

Platform

A panel to see what happens to every event

What was received, its forwarding urls and the status of each delivery in one place.

Everything received, with its json

Search by platform, identifier, status and dates; open any event and see the json and headers exactly as they arrived.

Sent, pending and failed
One-click manual resend
History with number of attempts

Received object

{"object": "whatsapp_business_account",
  "entry": [{
    "changes": [{ "value": {
      "metadata": { "phone_number_id": "1234567890" },
      "messages": [{ "type": "text" }]
    }}]
  }]}
# Stored and forwarded to your urls

Forwarding urls your way

Every event that arrives for an identifier is sent to all its urls, with the original json and headers.

Multiple urls per identifier
Button to test delivery
Without changing the original format

Webhooks · Sales

Active

https://crm.example.com/webhook 200 OK
https://bot.example.com/inbox 200 OK
https://test.example.com/hook Testing

For agencies and integrators

Manage all your clients from a single account. Each client has its workspace, its users and its identifiers.

Team with administrator, editor or reader role
Workspaces grouped by client
Account activity log

Luna Pharmacies

4 identifiers

Sol Real Estate

2 identifiers

North Clinic

3 identifiers

Delta School

1 identifier

Developers

Query and manage Renvias with an API key

Your software can query what was received and its statistics, resend, and manage identifiers and urls, with the same rules as the panel.

API keys

Create and revoke them from the panel.

What was received

Query, filter and resend any event.

Urls per identifier

Add, query and delete your forwarding urls.

terminal

# Query what WhatsApp sent
curl -X POST https://renvias.com/API/V1/RecibidosAPI \
  -H "Content-Type: application/json" \
  -d '{"llaveAcceso": "YOUR_API_KEY", "solicitud": "mostrarRecibidos", "Estado": "PENDIENTE"}'

# Add a forwarding url to an identifier
{"solicitud": "crearWebhook",
  "Nombre": "Mi sistema",
  "Url": "https://your-system.com/webhook"}

Frequently asked questions

We answer your questions

It is a middleman for your webhooks: it receives what your platforms send, stores it and forwards it to all the urls you choose, retrying when your system does not respond.

No. Your url receives the json and headers exactly as the platform sent them.

The event is stored as pending and Renvias retries it for several hours. If the attempts run out it is marked as failed and you can resend it manually.

It is the value the platform uses to identify your account in each event: the WhatsApp phone_number_id, your page id or the one you choose for Telegram. With it you see what is yours and define where it is forwarded.

Yes. Create a workspace per client, add users and register their identifiers.

No. Renvias only receives and forwards your platforms' events; you send messages from your own system.

Sales · WhatsApp

Orders bot · Telegram

Page · Messenger

1,248

99.4%

3