\
**Category:** API and Webhooks\
**Created:** [June 13, 2022, 9:37pm UTC](https://devforum.zoom.us/t/authentication-returning-html-not-json/70458 "2022-06-13T21:37:27Z")\
**Posts on this page:** 3\
**Page:** 1
**Author:**  [@brittanypoint600](https://devforum.zoom.us/u/brittanypoint600)\
**Post date:** [June 13, 2022, 9:37pm UTC](https://devforum.zoom.us/t/authentication-returning-html-not-json/70458/1 "2022-06-13T21:37:27Z")
**Description**
Hello, We are using an ETL tool (Rivery) to connect to the Zoom API. However, when we submit the Authentication request, we get HTML back instead of JSON. Is this something you can help us understand how to navigate?
My understanding is that it should return JSON that includes an authentication code which we need to pass back to get an access code.
**API Endpoint/s?**
Hoping to use the meetings endpoint, but haven’t gotten past the authentication stage.
**How To Reproduce**
_Steps to reproduce the behavior:_
\*1. URL: [https://zoom.us/oauth/authorize](https://zoom.us/oauth/authorize)
REST URL Parameters: response\_type=code, redirect\_uri, client\_id
\*2. Using Rivery ETL REST API
\*3. Expecting JSON code, but returning HTML
We are getting a “Success 200” status, but the returning code isn’t JSON.
Thank you!
Brittany
---
**Author:**  [@MultiplayerSession](https://devforum.zoom.us/u/MultiplayerSession)\
**Post date:** [June 14, 2022, 1:57pm UTC](https://devforum.zoom.us/t/authentication-returning-html-not-json/70458/2 "2022-06-14T13:57:35Z")
[OAuth applications](https://marketplace.zoom.us/docs/guides/auth/oauth/) that aren’t [server-to-server OAuth applications](https://marketplace.zoom.us/docs/guides/build/server-to-server-oauth-app) require the user to use a web browser to authorize the use of your application. The `https://zoom.us/oauth/authorize` endpoint is not for APIs, you [redirect the user’s web browser](https://marketplace.zoom.us/docs/guides/auth/oauth/#step-1-request-user-authorization) there, and depending on what happens next, Zoom will redirect the web browser back to the redirect URL you specified and then your application can call the `https://zoom.us/oauth/token` endpoint to swap the authorization code you got back in the redirection for an access token and a refresh token, which you can use without further user interaction in a web browser.
---
**Author:**  [@system](https://devforum.zoom.us/u/system)\
**Post date:** [July 14, 2022, 11:57pm UTC](https://devforum.zoom.us/t/authentication-returning-html-not-json/70458/3 "2022-07-14T23:57:35Z")
Closed on July 14, 2022, 11:57pm UTC
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.