Data Compliance Token

[Thrive]

curl -X POST \
  https://api.zoom.us/oauth/data/compliance \
  -H 'Authorization: Basic TERaOXMwYlRXbVBPVWx2Q1UwVV93OlFwWTBRU253TmIzN0JrVzBXS2FSemUxWnM5b1Z4eEpr' \
  -H 'Content-Type: application/json' \
  -H 'cache-control: no-cache' \
  -d '{
  "client_id": "ABcDefGHIj12A",
  "user_id": "a8yCxjayaSiw02igC8p8l0",
  "account_id": "abcdEfghIJklMn00",
  "deauthorization_event_received": {
   "user_data_retention": "false",
        "account_id": "abcdEfghIJklMn00",
        "user_id": "a8yCxjayaSiw02igC8p8l0",
        "signature": "85f9dd5684aecfa97h7bc86b7edc345204467f2jfj4df1b290093cf73fd1e6b00",
        "deauthorization_time": "2019-06-17T13:52:28.632Z",
        "client_id": "ABcDefGHIj12A"
  },
  "compliance_completed": true
}
'

I am looking at this example from the document, what token am I suppose to use for posting the data compliance? In this example, it has a value of:

TERaOXMwYlRXbVBPVWx2Q1UwVV93OlFwWTBRU253TmIzN0JrVzBXS2FSemUxWnM5b1Z4eEpr

[Thrive]

I forgot to make it Base64 of the Client ID and Client Secret. Something like this (ruby):

  headers_secret = Base64.strict_encode64("#{CLIENT_ID}:#{CLIENT_SECRET}")
  headers = { 'Authorization': "Basic #{headers_secret}" }

[MaxM]

Hey @Thrive,

Thank you for reaching out to the Zoom Developer Forum. Good Question! If we take a look at the Data Compliance API, we can see that the Signature can be found in the Deauthorization Webhook event that your application receives when a user uninstalls the app.

I hope that helps! Let me know if you have any questions.

Thanks,
Max