API Use vs a Pageview — and why more people use APIs on Linkspider
Both an API call and a pageview end with a server sending data back — but the way they get there, who they serve, and what they cost are very different. Here is the plain distinction.
What is a pageview?
A pageview is a human opening a rendered page in a browser. A person types a URL, clicks a link, or taps a result; the browser downloads HTML, CSS, JavaScript, images, and fonts; the page is laid out and painted on screen; and the human reads it. Every pageview carries that full rendering weight and assumes a person is sitting at the other end.
What is API use?
API use is a machine asking another machine for data — and getting just the data, no interface. A program sends a request (often with an authentication token in the headers), the server returns structured JSON or XML, and the calling code reads the fields it needs. There is no HTML, no layout, no fonts, no rendering — no human in the loop. It is raw data delivered directly to software that knows what to do with it.
The core differences
| Aspect | Pageview | API Use |
|---|---|---|
| Consumer | A human in a browser | A program / script |
| Payload | Full rendered page (HTML, CSS, JS, images) | Structured data only (JSON / XML) |
| Rendering | Laid out & painted on screen | None — parsed by code |
| Speed | Limited by human reading + page weight | Milliseconds, data only |
| Scale | One person at a time | Thousands of calls in parallel |
| Auth | Session cookie / login screen | Token in request headers |
| Best for | Reading, browsing, exploring | Automation, extraction, pipelines |
Why more people use APIs on Linkspider
- 1Edge-authenticated tokens. Linkspider service tokens are bound to Cloudflare Access, so every API request is authenticated at the edge before it reaches an origin — there is no login screen to navigate, just headers to attach.
- 2Built for real internet work. Crawl, extract, and data pipelines are inherently programmatic — the crawl-and-extract toolkit is designed to be driven by API calls, not clicked through a page.
- 3Speed and scale. A pageview serves one person once; an API call can be repeated thousands of times a minute, concurrently, against large target sets — exactly what Pro and Business subscribers run.
- 4No rendering overhead. Because the response is pure data, there is no HTML, CSS, or image weight to ship — faster round-trips and lower cost per request.
- 5Reproducible and automatable. A script with a token runs identically every time and slots straight into a pipeline, where a pageview depends on a human being present and clicking.
In short: a pageview is a person reading a rendered page; an API call is a machine receiving raw data. Because Linkspider's services — crawl, extraction, storage, billing — are meant to be wired into automated workflows behind an edge-authenticated token, the API is the natural way most customers reach them.