The JWT app type will be completely deprecated as of June 2023

We are still working on 3.x, but I went ahead and released a 2.1.0 version that supports Drupal 10.

This is a proof of concept (super rough) of how the client will need to be refactored.

https://gist.github.com/joelsteidl/fad398aab245b828a13a218e9640ad0a

Each request will need to include an access token as the Authorization header.

We are targeting the end of March 2023 for this to be available.

The 3.x version is just about ready for testing. https://git.drupalcode.org/project/zoomapi/-/tree/3.0.x

I will be working on documentation for converting from 2.x to 3.x.

Zoom has also made a lot of changes with Webhook validation that will become default in October 2023, so a lot of that is part of 3.x as well.

We have a dev release up for 3.x!

composer require 'drupal/zoomapi:3.0.x-dev@dev'

Please take a look at the 2.x to 3.x documentation → and let us know if you have any immediate questions.

We'll continue to work towards a stable release closer to June.

Thanks for all the work. For the record are post and deletes the same as post in such that it requires the json key in the options array?

That should be the case. Guzzle will automatically format the JSON.

Let me know if that isn't the case.

Doing some testing and that is the case, thanks! :)

@pixiekat Thanks so much for testing things out. I'm curious if you've had any issues so far.

I did discover one issue, actually. I was trying to put to the Update meeting status endpoint using the put() method and I received an 400 response: Request Body should be a valid JSON

I'm passing the meeting ID as the path and ['action' => 'end'] as the $option. I can't figure out why it's happening when it was working previously.

Oh, got it. It was a Guzzle configuration. For put() requests in Guzzle 6, you need to send ['json' => $data] as your $option. For form data, you would send ['form_params' => $data].

Might be helpful to include in the documentation (not meaning that as a demand or to be rude or anything; I just think other people might be interested so they don't have to hunt). :)

Upgraded a bunch of sites and it went smoothly. One thing I might suggest is to release a 2.x minor release requiring apitools ahead of the official 3.x release, since in some cases I had issues with trying to upgrade but getting caught in a loop where it would fail because it couldn't find the apitools service that zoomapi requires.

Thanks so much for following up!

Good feedback on apitools.

I'll look at getting a stable release up for that and and Zoom API 3.x. I might go straight for a stable sense the API changes on the Zoom side are required.

Please checkout the 3.0.x Alpha version. Open up issues if you have any.

Automatically closed - issue fixed for 2 weeks with no activity.