Looking at the code, it seems to be requiring both username and customer_id currently. It is supposed to return an error with something like "No username provided" if that is what the problem is. Though, it appears that the way it is written that error might not be making it back to you. You mind making a bug report here: https://q2developer.com/support/create?ticketType=Bug mention my name and I will look into it with you there.
Answered
Update to GetAccountList throwing 403 Forbidden
After reading the release notes that you can now call the GetAccountList operation while sending a customer_id query parameter, I am receiving a 403 Forbidden response. Is there a change to scope requirements after the update? My application has 'CaliperAPI:GetAccountList' enabled and is successfully completing other test calls, which leads me to think my scope/env alignment is correct otherwise. I am attempting to perform a GET call to the following url: https://stage.q2api.com/v2/GetAccountList?customer_id={}
106 Views
1
Answer
3 years ago
3 years ago