🔑 [New Plugin] OAuth 1.0a Request Signing Handler

Showcase
21

I’ve used the same setup as the demo for testing. It’s the twitter API, and I’ve used the same Base URL as the demo as well, which is this: https://api.twitter.com/1.1/users/search.json?q=soccer.

This is the setup on the API connector side:

image
image1758×1344 195 KB

22

Just to add to this, I’ve tried with a different endpoint, which is the one documented here: GET /2/users/:id/tweets | Docs | Twitter Developer Platform

Here’s the setup, for it:

image
image1724×1362 199 KB

I’ve tried the same thing where I generated the auth header and copied&pasted it to the authorization key value. This time, I get the following error:

There was an issue setting up your call.

Raw response for the API
Status code 401
{
“title”: “Unauthorized”,
“type”: “about:blank”,
“status”: 401,
“detail”: “Unauthorized”
}

Regenerating the keys produced the same result.

23

Please bear with me until early next week, I will have a look.

24

Hey @masaki_takamatsu,

See Twitter Elevated Access? - #6 by mccjon to try out.