# Issue with Zoom API - Migration from JWT to Server-to-Server OAuth - PHP cUrl -code":200,"message":"Account does not enabled REST API." **URL:** \ **Category:** Meetings\ **Tags:** php\ **Created:** [September 13, 2023, 7:56pm UTC](https://devforum.zoom.us/t/issue-with-zoom-api-migration-from-jwt-to-server-to-server-oauth-php-curl-code-200-message-account-does-not-enabled-rest-api/95052 "2023-09-13T19:56:07Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Lunchdog](https://avatars.discourse-cdn.com/v4/letter/l/ea666f/32.png) [@Lunchdog](https://devforum.zoom.us/u/Lunchdog)\ **Post date:** [September 14, 2023, 3:45pm UTC](https://devforum.zoom.us/t/issue-with-zoom-api-migration-from-jwt-to-server-to-server-oauth-php-curl-code-200-message-account-does-not-enabled-rest-api/95052/7 "2023-09-14T15:45:26Z")
A request for account\_credentials requires an account\_id in the URL, and a ClientID/ClientSecret in the request itself: " To use account credentials to get an access token for your app, call the Zoom OAuth token API with the `account_credentials` `grant_type` , your `account_id` , and your client ID and client secret, [base64 encoded](https://www.base64encode.org/) (encode your client ID and client secret with a colon between them, e.g. `client_id:client_secret` )." > **[Server-to-Server OAuth](https://developers.zoom.us/docs/internal-apps/s2s-oauth/)** > > The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform. By the way, it’s far easier to create/compose these requests using Postman, or if you’re sold on just PHP, something like Guzzle. --- _[View the full topic](https://devforum.zoom.us/t/issue-with-zoom-api-migration-from-jwt-to-server-to-server-oauth-php-curl-code-200-message-account-does-not-enabled-rest-api/95052)._