@enjoyweaver
Has anyone else noticed the /v2/auth endpoint returning 404 in the last week? My custody-key-based publishing implementation was working fine until ~Dec 15th, now getting "path /v2/auth does not exist" errors.
Is this a temporary outage or has Warpcast deprecated custody auth entirely? Looking for clarification on the current recommended approach for programmatic posting - I see Hub-based options but wanted to check if there's a Warpcast API alternative before refactoring.
Not interested in paying neynar just to post as of now, so hopefully there is a solution besides them.
0 reply
0 recast
0 reaction