Skip to Main Content

API, CLI, SDK & Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

GoogleMeet API test using APEX RESTfull datasource

Engineerr1983May 9 2024

Hi,

I'm trying to test Google Meet APIs using Postman application. I've tested all APIs available for Google Meet in Google Cloud Console as shown below:

All of them contain different functionality.

As an example (ConferenceRecords) lists all conferences or get one of them by its id, I've tested it successfully using postman

and listed all conferences or listed one of them by its id.

The authorization was OAuth2.0 and the parameters like (CallBack URL // Auth URL // Access Token URL) client id and secret were filled accordingly.

And each time I had to create access token to authenticate the request successfully

The access token considered to be a parameter which was created automatically

After the postman test was succeeded, I've tried to create the RESTfull data source as in APEX tutorials - in APEX tutorial it depends on REST catalog, but Google Meet does not have such catalog, so I've created the REST Datasource from scratch -

The type was (OracleREST data source) not Simple HTTP, and the (URL End point) the same value as in Google Meet REST API page

Base and Service path were filled automatically

The Auth type was OAuth2.0, and the Auth Token URL as shown below, the same as the one used in postman.

But when I hit (Discover) button, it gave me an error message (Auth failed).

In case I click Advance button and put the (Access Token) as a parameter it will give the same error.

If I click on (Create manually), it will be created,

On the REST data source page, in (Operations tab), I tried to test the operation (GET) again, but again it will give the same error

But in Postman the test was succeeded.

I'm not sure if the OAuth2.0 in Google Cloud workspace might cause this, but in postman all the tests were succeeded

However, it contains 2 redirect URIs as shown above, and the Authorized Java script origins points to Oracle apex website as far as it is the application that would be connected to the Google REST APIs.

Not sure if these URLs might cause the error because it was working fine in Postman.

Any ideas?

Thanks

Comments
Post Details
Added on May 9 2024
0 comments
197 views