A place for developers to talk about building on Farcaster.

/dev

Are there any other devs who find the shortened cast hash in Warpcast (like https://warpcast.com/pirosb3/0x730fb767) a bit limiting?

It's user-friendly, but for development purposes, I need access to the full cast hash.

Does anyone have any tips or workarounds?

Engineer @farcaster, co-founder @bountycaster. Sharing what I learn about AI + development. Previously: Phantom, 0x. NYC 🗽

You can pass the link to our v2/cast api and get back the full cast details

building farcaster infra @ /neynar 🪐 | casting @ /rish

Wouldn't it work here? https://vasco.wtf/cast/0x4e4aba11

here's the link to the API doc: docs.neynar.com/reference/cast

sorry maybe I didn't understand your request, can chat more on TG if needed :) 

we agree that having the cast hash embedded in the cast is more useful, we brought it up in the dev call with Warpcast team yesterday. It's on their backlog, if that helps. 

What I was suggesting is a workaround since you asked for one

Thanks @rish

I appreciate the link to the API documentation. Just to clarify my preference: I lean towards using the full, non-shortened cast hash version because it adheres to the standard Farcaster format, unlike the shortened version provided by Warpcast.

I am not sure exactly how vasco is doing it but this curl request should work: 
curl --request GET \
     --url 'https://api.neynar.com/v2/farcaster/cast?type=url&identifier=https%3A%2F%2Fwarpcast.com%2Fpirosb3%2F0x9912f245' \
     --header 'accept: application/json' \
     --header 'api_key: NEYNAR_API_DOCS'