Skip to main content
Anonymous
December 9, 2020

consume entitlement returns 400

Hello,
I'm following the API documentation for the consume_entitlement endpoint.
The documentation says that it should return a 200 with a success boolean.

The verify_entitlement works the same and it returns a 200 with success true/false
I'm always getting 400 Bad Request for the consume_entitlement endpoint.

Any help with this?

1 reply

shogokivnz
New Participant
December 12, 2020
Hi for me is a little different the consume_entitlement work correctly but I'm getting 400 bad request erros when calling
GetLoggedInUserFriends, GetUserProof, GetViewerPurchases any idea why is this happening? The device is a Quest, the weird thing is that I have two branch one the production that is working correctly on all the request but when I change to the alpha branch that is literally the same code base save some minor changes I get the 400 errors
Terms & ConditionsAccessibility statement