Webhooks

🔔 Webhooks

Webhooks allow external systems to receive real-time updates when specific events occur within the Networked platform. Instead of polling APIs repeatedly, your application can subscribe to events and react instantly to user activities, content changes, or subscription lifecycle events.

📘 How It Works

When a subscribed event is triggered (e.g., a new user joins, a post is created, or a subscription creates), we will send an HTTP POST request to the URL you’ve registered. The request will contain a JSON payload describing the event and its data.

✅ Use Cases

Automatically update your CRM when a new user signs up.

Trigger push notifications when someone comments on a post.

Sync calendar systems when event is created.

Monitor billing systems for payment reminders.

To start receiving webhooks:

Contact your Networked Customer Success Executive with the list of webhook events you wish to subscribe to and your desired endpoint URL(s).

Our team will configure the webhook settings on your behalf and confirm once setup is complete.

Ensure your endpoint responds with an HTTP 200 status code to acknowledge receipt of webhook deliveries.

📦 Payload Structure

Each webhook payload contains:

event: The event type (e.g., user.joined)

timestamp: UNIX timestamp of the event

data: The event-specific object payload

{
  "event": "user.joined",
  "timestamp": "1750689600",
  "data": {
    // the data may change depending upon events and for this event also check specific section  
    "user_id": "usr_123456",
    "name": "Jane Doe"
  }
}

Continue below to explore supported events by category (User, Feed, Event, Subscription). Each event includes sample payloads and field descriptions to help you implement robust, real-time integrations.

🔐 Webhook Signature Verification

To ensure the authenticity and integrity of all webhook requests sent by Networked, we include a secure HMAC-SHA256 signature in each request header. This allows you to verify that the payload hasn’t been tampered with and that it truly originated from Networked.

📤 What We Send

Every webhook request includes the following custom header:

Header Name	Description
`x-webhook-signature`	HMAC-SHA256 hash of the payload body
`x-webhook-timestamp`	(Optional) UNIX timestamp used for replay checks

🧪 How to Verify the Signature

To validate the webhook, follow these steps on your server:

1. Reconstruct the Payload

Capture the raw request body (as a string), not a parsed JSON object. For example:

{ "event": "user.joined", "timestamp": 1750689600, "data": { ... } }

2. Generate a Signature Locally

Use your shared webhook secret key to generate an HMAC-SHA256 hash of the request body.

Sample Code – Node.js

3. Compare Signatures Securely

Match your locally generated signature with the one sent in the x-webhook-signature header.

🛡️ Optional: Protect Against Replay Attacks

If you're using x-webhook-timestamp, you can:

Validate that the timestamp is within a 5-minute window.

Combine the timestamp with the payload during hashing:

✅ Example Verification Workflow

📌 Notes

The webhook secret is unique to each partner. Keep it secure.

We may occasionally rotate secrets and notify you in advance.

Always log and monitor failed verifications.

💬 Need Help?

If you have any questions or need support implementing verification, reach out to your Networked Customer Executives.

🔔 Webhooks#

📘 How It Works#

✅ Use Cases#

⚙️ How to Subscribe#

📦 Payload Structure#

🔐 Webhook Signature Verification#

📤 What We Send#

🧪 How to Verify the Signature#

1. Reconstruct the Payload#

2. Generate a Signature Locally#

Sample Code – Node.js#

3. Compare Signatures Securely#

🛡️ Optional: Protect Against Replay Attacks#

✅ Example Verification Workflow#

📌 Notes#

💬 Need Help?#