Why am I receiving a '400 bad request, invalid token' response from Trello while testing the proxy endpoint in a Trello integration?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

I’m testing out the proxy endpoint using a trello integration, but it looks like the query params that Trello expects into the url are not being set?

I get back a 400 bad request, ‘invalid token’ response text, which seems to come from Trello.

My request looks like:
GET 'https://api.pipedream.com/v1/connect/<our_project>/proxy/LzEvbWVtYmVycy9tZS9ib2FyZHM=?account_id=<apn_xxx>&external_user_id=
Headers

2

How exactly does Pipedream know where to add the expected parameters in the proxy url? Trello apparently needs key={yourKey}&token={yourToken}'

3

This may be related to Trello using OAuth 1.0 instead of 2.0, which is pretty non-standard, but I’m checking it out.

4

Any update on this? I can create a bug issue if needed

5

Yea I did get a chance to dig in, and unfortunately OAuth 1.0 isn’t supported in the Connect Proxy right now (there are very few apps that still rely on it). Feel free to create an issue in GH and we can track it there.

6

Created here: