Why webhooks push notifications in Rest API - See It in Action

Why Webhooks Push Notifications

📖 Scenario: Imagine you run an online store. You want to know immediately when a customer places an order so you can start packing it. Instead of checking the website all the time, you use a webhook to get notified instantly.

🎯 Goal: Build a simple program that shows how webhooks push notifications to your system when an event happens, like a new order.

📋 What You'll Learn

Create a dictionary called event_data with keys 'event' and 'order_id' and values 'order_placed' and 12345

Create a variable called webhook_url and set it to 'https://example.com/webhook'

Write a function called send_webhook_notification that takes url and data as parameters and prints a message showing the URL and data sent

Call the function send_webhook_notification with webhook_url and event_data

Print the message exactly as: Sending webhook to https://example.com/webhook with data {'event': 'order_placed', 'order_id': 12345}

💡 Why This Matters

🌍 Real World

Webhooks are used in many apps to notify other systems instantly when something important happens, like a new order, a payment, or a message.

💼 Career

Understanding webhooks is important for developers working with APIs, integrations, and real-time data updates in web and mobile applications.

1

Create the event data dictionary

Create a dictionary called event_data with these exact entries: 'event': 'order_placed' and 'order_id': 12345

Rest API

# Create the event_data dictionary
# Your code here

Hint

Use curly braces {} to create a dictionary with the keys and values exactly as shown.

2

Set the webhook URL

Create a variable called webhook_url and set it to the string 'https://example.com/webhook'

Rest API

event_data = {'event': 'order_placed', 'order_id': 12345}
# Create the webhook_url variable
# Your code here

Hint

Assign the URL string to the variable webhook_url.

3

Write the function to send webhook notification

Write a function called send_webhook_notification that takes two parameters: url and data. Inside the function, write a print statement that shows: Sending webhook to {url} with data {data} using an f-string.

Rest API

event_data = {'event': 'order_placed', 'order_id': 12345}
webhook_url = 'https://example.com/webhook'
# Define the send_webhook_notification function
# Your code here

Hint

Use def to create the function and an f-string inside print to show the message.

4

Call the function and print the notification

Call the function send_webhook_notification with the variables webhook_url and event_data to print the notification message.

Rest API

event_data = {'event': 'order_placed', 'order_id': 12345}
webhook_url = 'https://example.com/webhook'

def send_webhook_notification(url, data):
    print(f"Sending webhook to {url} with data {data}")
# Call the function to send the webhook notification
# Your code here

Hint

Call the function with the two variables exactly as named.

Practice

1. Why do webhooks push notifications instead of waiting for your app to ask for updates?

easy

A. To avoid sending any data to your app

B. To send updates instantly and save time and resources

C. To require your app to check for updates repeatedly

D. To make your app slower by adding delays

Solution

1. Step 1: Understand the purpose of webhooks

   Webhooks are designed to send data immediately when an event happens, instead of waiting for your app to ask.

2. Step 2: Compare push vs pull methods

   Push (webhooks) saves time and resources by sending updates instantly, unlike pull which requires repeated checking.

3. Final Answer:

   To send updates instantly and save time and resources -> Option B

4. Quick Check:

   Push notifications = instant updates [OK]

Hint: Webhooks push to save time and avoid repeated checks [OK]

Common Mistakes:

• Thinking webhooks slow down the app
• Confusing push with pull methods
• Believing webhooks avoid sending data

2. Which HTTP method do webhooks commonly use to send notifications?

easy

A. POST

B. DELETE

C. GET

D. PUT

Solution

1. Step 1: Identify the HTTP method for sending data

   Webhooks send event data to your app, which requires a method that can carry data in the request body.

2. Step 2: Match HTTP methods to their purpose

   POST is used to send data to a server, unlike GET which only requests data without sending a body.

3. Final Answer:

   POST -> Option A

4. Quick Check:

   Webhooks use POST to send data [OK]

Hint: Webhooks send data using POST requests [OK]

Common Mistakes:

• Choosing GET which only retrieves data
• Confusing PUT or DELETE with sending notifications
• Not knowing HTTP methods' purposes

3. Consider this webhook setup: Your app receives a POST request with event data immediately when a user updates their profile. What is the main benefit of this approach?

medium

A. Your app gets real-time updates without delay

B. Your app must ask repeatedly for updates

C. Your app ignores updates until manually refreshed

D. Your app receives outdated information

Solution

1. Step 1: Analyze the webhook behavior

   The webhook sends a POST request immediately when the event happens, so your app gets notified right away.

2. Step 2: Understand the benefit of instant notifications

   This means your app does not need to ask repeatedly and can update its data in real time.

3. Final Answer:

   Your app gets real-time updates without delay -> Option A

4. Quick Check:

   Instant POST = real-time updates [OK]

Hint: Instant POST means real-time updates [OK]

Common Mistakes:

• Thinking app must poll for updates
• Assuming updates are delayed
• Believing webhook sends outdated info

4. You set up a webhook but your app never receives notifications. Which of these is a likely cause?

medium

A. Your app is polling the webhook URL repeatedly

B. Your app is sending POST requests to the webhook

C. Webhooks use GET requests instead of POST

D. The webhook URL is incorrect or unreachable

Solution

1. Step 1: Check webhook delivery requirements

   Webhooks send POST requests to a URL your app provides. If the URL is wrong or unreachable, notifications won't arrive.

2. Step 2: Eliminate incorrect causes

   Your app does not send POST requests to the webhook; the webhook sends them. Webhooks use POST, not GET. Polling is unrelated to webhook delivery.

3. Final Answer:

   The webhook URL is incorrect or unreachable -> Option D

4. Quick Check:

   Wrong URL = no notifications [OK]

Hint: Check webhook URL correctness first [OK]

Common Mistakes:

• Thinking app sends POST to webhook
• Confusing HTTP methods used
• Assuming polling affects webhook delivery

5. You want your app to update user data immediately when a payment is completed. Which approach best uses webhooks to achieve this?

hard

A. Send GET requests from your app to the payment server repeatedly

B. Make your app check the payment status every minute

C. Set up a webhook that sends a POST notification to your app when payment completes

D. Ignore payment updates and refresh data manually

Solution

1. Step 1: Identify the goal

   You want immediate updates when payment completes, so your app must get notified instantly.

2. Step 2: Choose the webhook approach

   Setting up a webhook that sends a POST notification on payment completion pushes updates instantly, avoiding delays and repeated checks.

3. Final Answer:

   Set up a webhook that sends a POST notification to your app when payment completes -> Option C

4. Quick Check:

   Webhook POST = instant payment update [OK]

Hint: Use webhook POST for instant payment updates [OK]

Common Mistakes:

• Relying on polling instead of webhooks
• Using GET requests incorrectly
• Ignoring real-time update needs