# Meeting API authentication

**URL:** <https://devforum.zoom.us/t/meeting-api-authentication/110309>\
**Category:** Twilio Migration\
**Created:** [May 20, 2024, 4:23pm UTC](https://devforum.zoom.us/t/meeting-api-authentication/110309 "2024-05-20T16:23:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![r.asgari.g](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/r.asgari.g/32/59547_2.png) [@r.asgari.g](https://devforum.zoom.us/u/r.asgari.g)\
**Post date:** [May 20, 2024, 4:23pm UTC](https://devforum.zoom.us/t/meeting-api-authentication/110309/1 "2024-05-20T16:23:21Z")

</div>

I’m going through the Meeting API docs and there is no guide on authentication. [Meeting API](https://developers.zoom.us/docs/meeting-sdk/apis/#tag/Meetings)

I have already tried this manually with OAuth (creating the authorize URL, getting the “code” and creating a token using code, client\_id and client\_secret) and it works properly but I don’t understand how I can achieve this when my backend service wants to authenticate and call the API?

To give you an idea of what I mean, this is my use case:

- I want my backend to create a meeting on behalf of the host
- My backend needs to call different API methods to get info, process recordings etc

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [May 23, 2024, 4:23am UTC](https://devforum.zoom.us/t/meeting-api-authentication/110309/2 "2024-05-23T04:23:47Z")

</div>

@r.asgari.g I don’t understand the question.

Could you elaborate on the user story? And this is for meeting SDK & meeting API right?