Proxycurl Shut Down: The Architecture That Decided the Case
For the developers who built on it and the ones still finding it in old code: what the API was, what ended it, and where the work goes now.
For the developers who built on it and the ones still finding it in old code: what the API was, what ended it, and where the work goes now.
Sizing it up before you build on it: what the API covers, how an account connects, what a linked account costs, and where its MCP server stops.
Two official APIs answer to the name, only one searches people, and the rows it returns have no job title in them.
The seat is not the expensive part. What the seat quietly refuses to do is what decides whether it pays.
Publishing is the one thing LinkedIn hands out with no application at all, and reading the same posts back is the thing it stopped handing out.
It is not on linkedin.com, it is not one set of docs, and its foundations were last touched in 2023.
The connection takes a minute, and then you discover no Zap can start from anything happening on LinkedIn.
Two different nodes answer to that name, and the one n8n ships cannot send a thing.
Searching for a LinkedIn jobs API is the obvious first move, and it returns the one product that cannot read a job listing.
The cheapest way to pull LinkedIn data is also the one most likely to cost you the account you meant to use it from.