This topic was automatically generated from Slack. You can find the original thread here.
Did the new twitter updates finally nix the API access? I’d had no trouble using it after the announcement that they were cancelling it in early March, but I’ve had no luck the last couple days. I’ll investigate if its not definitely blocked and won’t investigate if its definitely blocked.
Yep unfortunately Twitter disabled our OAuth client yesterday. We’re actively working on getting it working again, but it’ll require you enter your own developer credentials (client ID and secret), in order to connect your account.
They announced the tiers last week: https://twitter.com/TwitterDev/status/1641222782594990080
tl;dr is limited write access for free, additional read and write for $100/month, as well as an Enterprise tier
Broader communications from us are coming soon, as soon as we get the updated implementation working
I only need write access so I just need to sign up for my own dev account and then pass the details to you guys via the component? Or should I just wait to see if you get your own access back? I can wait a few weeks.
Yea, you will pass the creds to us once, when you re-connect your account. Then we’ll still handle the secure storage and refresh logic for the access token, which actually authenticates you with their API.
Oh, and while I have you here…no movement on the instagram API access? Do you think I could build my own with the new pipedream/GPT componnent builder or are they fundamentally against us accessing it for some reason?
Can you tell me more about your use case? That will help get it prioritized
Every time I add a new product (records/CDs/tapes) to my shopify store I post the album cover to Instagram. https://www.instagram.com/furtherrecords/
Right now I’m using Zapier to copy my tweets to insta which isn’t ideal.
I created a twiter dev account and was able to log in to my new dev account but the only thing I can do with it atm is send DMs
When I try and use my old workflow by reconnecting my account the input fields dont match anything I’m seeing on twitter dev page
OK. so I went down that path and provided a generic pipedream webhook as the callback URL (with and without a custom response). That got me a clinet ID and key but still returned an error when connecting. error ID: bef86a514b5043fa846d089d5f3c1479
That will be the pathway, yes, but the app is not working yet. Twitter has a bug in how they handle their OAuth 2.0 popup window, and we have a couple things we need to address in order to get OAuth 1.0 working with user-provided client ID and secrets.
