Neynar

Celebrating the experimental launch of hubs.neynar.com

I am curious how you think we should manage Warpcast authentication within Pipedream. Given we won't be rotating access tokens, it seems treating the App Bearer Token like a standard API key is the best path. Thoughts / feedback?

https://pipedream.com/apps/warpcast

does anyone know if you have to worry about expiration / rotation of bearer tokens?

based on linked cast, seems like expiration isn't an issue

does anyone know if you have to worry about expiration / rotation of bearer tokens?

based on linked cast, seems like expiration isn't an issue

https://warpcast.com/tod/0x4f6d563b

trendies cofounder

ex-dydx senior swe

https://warpcast.com/trendies

for context, asking because i want to automatically moderate casts in a channel

planning to use warpcast endpoint /v2/debug-cast-embeds for warning + hiding casts (found this endpoint from network tab when hiding a post, name seems off but couldn't find other relevant api calls)

good question! this is specific to Warpcast's implementation of authenticated APIs. 

If you're using signers to write to the protocol as a bot or on behalf of users, then there's no expiration for the signer itself. Only users can revoke signers today. We've requested for developer revocations as a feature.