#1

Hi, I’m Jaap and I’m new here.

Twitter V2 API doesn’t send the “access-control-allow-origin” header when you make a request. I’ve searched the forum for an answer, and yes I think I’ve found it: “Twitter API V2 doesn’t support CORS, you should make requests via a back-end, Twitter doesn’t support front-end requests yet”.

Is this still true? I’ve read some posts that maybe Twitter will support this in the future.

You can now configure your Twitter API v2 app in the Twitter Developer Portal as a “Public Client”, you only need to send your ClientId not your ClientSecret, so imho it would make sense if you can make Twitter API v2 requests directly from within the browser. WebAssembly (WASM) is the next great thing (I think :wink:) so making requests from within the browser to the Twitter API would be a fantastic option.

So my question actually is, is there any news on this front?

Twiitter
CORS error in oauth2/token?
#2

This post was flagged by the community and is temporarily hidden.

#3

Hi @J_aa_p,

I still don’t have an update here, but we are still planning on implementing this in the future. Thanks for checking in.

Best,

Jessica

1 Like
#4

Thank you for your reply and ‘closing’ this issue as there was already a better thread covering this. And I’ve added a possible solution there too, see: CORS error in oauth2/token? - #11 by J_aa_p