This may not be a bug on your part, just wondering if you've seen this? We've been using the access_token acquired by the usual oauth2 exchange auth code for tokens flow, server side. Is this even the correct token to use here? It seems no matter what we put in for Bearer we get this response. I would expect a 400 or 401 response, not { parts: [], errors: 0 } Thanks for any info you can provide!