Why webhooks push notifications in Rest API - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do webhooks push notifications instead of polling?

Imagine you want to get updates from a service as soon as something changes. Why would a webhook push notifications instead of you asking repeatedly (polling)?

A Because polling is faster and more efficient than pushing notifications.

B Because pushing notifications saves resources by sending updates only when needed, avoiding constant checking.

C Because webhooks cannot send data automatically and require manual requests.

D Because pushing notifications requires the client to ask for updates every few seconds.

💡 Hint

Think about how often you want to check your mailbox versus being told when mail arrives.

Webhooks push notifications to save resources and provide real-time updates. Polling requires repeated requests, which can waste bandwidth and delay updates.

❓ Predict Output

intermediate

What is the output of this webhook simulation code?

Consider this Python code simulating a webhook notification system. What will it print?

Rest API

def webhook_notify(event):
    if event == 'update':
        return 'Notification sent'
    else:
        return 'No notification'

print(webhook_notify('update'))

A No notification

B Notification failed

C Error: undefined variable

D Notification sent

💡 Hint

Look at the event value passed to the function.

The function returns 'Notification sent' only if the event is 'update'. Since 'update' is passed, it prints that.

🔧 Debug

advanced

Why does this webhook notification code fail to send updates?

Look at this JavaScript code snippet meant to send webhook notifications. Why does it fail?

Rest API

async function sendWebhook(data) {
  fetch('https://example.com/webhook', {
    method: 'POST',
    body: JSON.stringify(data),
  });
}

sendWebhook({ event: 'update' });

A Because fetch is missing headers specifying content type, so server rejects the request.

B Because fetch requires await or then to handle the promise, otherwise it fails silently.

C Because the URL is incorrect and causes a DNS error.

D Because the method should be GET, not POST.

💡 Hint

Check what the server expects in the request headers.

Without 'Content-Type: application/json' header, the server may reject the JSON body, causing the webhook to fail.

📝 Syntax

advanced

Which option correctly defines a webhook handler function in Python?

Choose the correct Python function syntax to handle webhook POST requests.

A

def webhook_handler(request):
    if request.method == 'POST':
        return 'Received'
    else:
        return 'Invalid method'

B

def webhook_handler(request):
    if request.method = 'POST':
        return 'Received'
    else:
        return 'Invalid method'

C

def webhook_handler(request):
    if request.method == 'POST'
        return 'Received'
    else:
        return 'Invalid method'

D

def webhook_handler(request):
    if request.method == 'POST':
        return 'Received'
    else
        return 'Invalid method'

💡 Hint

Remember Python requires colons after if and else statements and uses '==' for comparison.

Option A uses correct syntax with colons and comparison operator '=='. Others have missing colons or wrong operators.

🚀 Application

expert

How many webhook notifications are sent in this scenario?

A webhook is set to notify on 'create' and 'delete' events. The system processes these events in order: ['create', 'update', 'delete', 'create', 'delete']. How many notifications will be sent?

A 5

B 3

C 4

D 2

💡 Hint

Count only events that match 'create' or 'delete'.

Only 'create' and 'delete' events trigger notifications. The list ['create', 'update', 'delete', 'create', 'delete'] has four such events: two 'create' and two 'delete'.

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