# Acceptable webhook HTTP response code of 202?

**URL:** <https://devforum.zoom.us/t/acceptable-webhook-http-response-code-of-202/77635>\
**Category:** API and Webhooks\
**Tags:** webhooks\
**Created:** [October 19, 2022, 7:50pm UTC](https://devforum.zoom.us/t/acceptable-webhook-http-response-code-of-202/77635 "2022-10-19T19:50:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![abernix](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abernix/32/10259_2.png) [@abernix](https://devforum.zoom.us/u/abernix)\
**Post date:** [October 19, 2022, 7:50pm UTC](https://devforum.zoom.us/t/acceptable-webhook-http-response-code-of-202/77635/1 "2022-10-19T19:50:03Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
This is a general question about the webhooks API expectations.

**Description**  
The documentation suggests that HTTP status code **200 or 204** must be returned. However, I am curious if there have been any considerations to also accept [“ **202 Accepted** ”](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/202).

In particular, it would be very nice if it was acceptable to return 202 since this indicates that the request will be processed but is seemingly the correct HTTP status code to return in the case where background processing might need to happen. Naturally, it means the request has been accepted. 😺

In my own case, I’m hopeful to continue to use Netlify Functions to serve our webhooks from Zoom as we have for some time. However, the processing I’d like to do on webhooks takes more than 3000ms. While Netlify Function sallows up to 10 seconds of processing (for example, to trigger other events) I have wanted to switch to using [Netlify Background Functions](https://docs.netlify.com/functions/background-functions/) to background process for up to 15 minutes.

However, the Netlify Functions return **immediately** with a 201 as soon as they have started executing the pipeline and are doing their background work.

Thoughts on adding 202 to the list of accepted HTTP status codes?

---

<div class="post-metadata">

**Author:** ![abernix](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abernix/32/10259_2.png) [@abernix](https://devforum.zoom.us/u/abernix)\
**Post date:** [November 11, 2022, 1:15pm UTC](https://devforum.zoom.us/t/acceptable-webhook-http-response-code-of-202/77635/2 "2022-11-11T13:15:10Z")

</div>

I’m realizing I made a mistake in my message above:

> [@abernix](#):
>
> However, the Netlify Functions return **immediately** with a 201 as soon as they have started executing the pipeline and are doing their background work.

This **should** have read “with a 202”, instead of 201.

Anyhow, since I haven’t heard anything back, is this generally the right place to ask a question like this? Or would I be better off taking another route?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [November 16, 2022, 10:08pm UTC](https://devforum.zoom.us/t/acceptable-webhook-http-response-code-of-202/77635/3 "2022-11-16T22:08:05Z")

</div>

HI @abernix  
Thanks for reaching out to the Zoom Developer Forum, I am happy to help here!  
And sorry that it took a long time to get to your post, but I am now on it to try to get you some information.  
I have read your message and I appreciate your feedback.  
I will now reach out to the Engineering team with all the feedback that you have shared and as soon as I have more information about it, I will come back to you with an update.  
Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [November 20, 2023, 1:44pm UTC](https://devforum.zoom.us/t/acceptable-webhook-http-response-code-of-202/77635/4 "2023-11-20T13:44:06Z")

</div>

Closed on November 20, 2023, 1:44pm UTC

This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.
