Twitch Drops: notifying the users of entitlements

[sfusco]

I’m trying to follow the docs here:

Drops

(values below have been scrubbed for security)

First, I create an access token:

curl -X POST
‘https://id.twitch.tv/oauth2/token?client_id=xxx&client_secret=xxx&grant_type=client_credentials’

this returns json:

{“access_token”:“xxx”,“expires_in”:5289569}

Then, using that access token, I try to get a drops url using a new / unique manifest id as a guid

curl -X POST
‘https://api.twitch.tv/helix/entitlements/upload?manifest_id=47302ab8-6968-42ca-80a6-fa09f9ac3c15&type=bulk_drops_grant’
-H ‘Authorization: Bearer xxx’

That returns this:

{“error”:“Not Found”,“status”:404,“message”:“{\n "status": 404,\n "message": "Service not found",\n "error": "Not Found"\n}”}

I have tried various combinations of moving the query string parameters into the form body as json, posting the form body as x-www-form-urlencoded, none of it works.

If I omit all the parameters I get this:

curl -X POST
https://api.twitch.tv/helix/entitlements/upload
-H ‘Authorization: Bearer xxx’

{
“error”: “Bad Request”,
“status”: 400,
“message”: “The parameter "type" was malformed: value must be one of "bulk_drops_grant"”
}

If I add in the type parameter I get this:

curl -X POST
https://api.twitch.tv/helix/entitlements/upload
-H ‘Authorization: Bearer xxx’
-H ‘Content-Type: application/x-www-form-urlencoded’
-d type=bulk_drops_grant

{
“error”: “Bad Request”,
“status”: 400,
“message”: “Missing required parameter "manifest_id"”
}

Then if I add the manifest_id parameter, I’m back to the 404

curl -X POST
https://api.twitch.tv/helix/entitlements/upload
-H ‘Authorization: Bearer xxx’
-H ‘Content-Type: application/x-www-form-urlencoded’
-d ‘type=bulk_drops_grant&manifest_id=47302ab8-6968-42ca-80a6-fa09f9ac3c15’

{
“error”: “Not Found”,
“status”: 404,
“message”: “{\n "status": 404,\n "message": "Service not found",\n "error": "Not Found"\n}”
}

Is this just a bug? Does my account need to be provisioned specially somehow?

[matwalsh]

@sfusco have you completed the steps at https://dev.twitch.tv/docs/drops/ specifically about registering your game and company and enabling/configuring drops? I believe that error message indicates that no drops configuration was found for your client ID. Alternatively if you have configured your drops service, are you using that clientID to generate your app token?

[sfusco]

Well, we have multiple client ids for our different environments. My guess is we only registered the production one for drops, and not this test one. I will need to double check which ids are registered when I get back to the office on Monday.