Compliance Api returning `Invalid Request` in 2020

API and Webhooks
1

Description/Error
We are testing our new integration. The Compliance Api is rejecting our requests…

Which Endpoint/s?
https://api.zoom.us/oauth/data/compliance

How To Reproduce (If applicable)
Steps to reproduce the behavior:

  1. Receive de-auth notification from Zoom for an app
  2. Post the de-auth to compliance api
  3. Get invalid-request 
HTTP/1.1 400 
Date: Thu, 09 Apr 2020 05:13:41 GMT
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Server: ZOOM
x-zm-trackingid: WEB_b1cf80f35608bbb8db341f54caa12862
X-Content-Type-Options: nosniff

{
  "reason": "Invalid Request",
  "error": "invalid_request"
}

Additional context

The request we are posting (sensitive values changed)

POST https://api.zoom.us/oauth/data/compliance HTTP/1.1
Authorization: Basic dwdwedwedwdwdwedwedwedwedw
Content-Type: application/json;charset=UTF-8

{"client_id":"aaa","user_id":"bbb","account_id":"ccc","deauthorization_event_received":{"user_data_retention":"false","user_id":"bbb","account_id":"ccc","signature":"sign82d60d47bf963ea874fb55144d2365cd9710f4","deauthorization_time":"2020-04-09T05:04:34.242Z","client_id":"aaa"},"compliance_completed":true}

Thanks!

2

Hey @mike2,

The only thing I see that looks off is the ;charset=UTF-8 in the content type.

Can you try removing that and let me know if it works?

Thanks,
Tommy

3

Hi @tommy - I tried again and keep getting the same response back

{
  "reason": "Invalid Request",
  "error": "invalid_request"
}

Also if I look at the call logs for the user that deauthorized the app nothing is logged there. Not sure what else to try.

4

Hey @mike2,

Can you private message me your actual deauth webhook and request body so I can debug further?

Thanks,
Tommy

5

Was there a resolution for this ? I am getting the same issues too

6

@alayvakil - it was a user error - I was using the wrong client_id to make the call. After I changed the client_id to the right one…surprise - it worked. The error message is not very informative, but they may have a reason for that.

1 Like
7

Hey @mike2,

Happy to hear you figured out the issue! :slight_smile:

We will work on improving our error messages.

Thanks,
Tommy

8

Hey @alayvakil,

Please see @mike2’s solution. If you are having a different issue, please start a new topic.

Thanks,
Tommy