Your tools. More possibility.
Put public web data where your work happens. Start with a recipe, connect your key, and make it yours.
15 connections to explore
TypeScript
Use native fetch with typed server-side code and explicit errors.
See the setup ↗C# / .NET
Connect .NET services with HttpClient and structured JSON.
See the setup ↗Next.js
Bring web data into your app with a server-only TypeScript helper.
See the setup ↗Bun
Run a TypeScript extraction script with Bun's built-in fetch.
See the setup ↗Deno
Use native TypeScript with narrowly scoped network permissions.
See the setup ↗HTML + your backend
Add a result viewer to a webpage while your API key stays on the server.
See the setup ↗Python
Bring clean web content into your scripts and data pipelines.
See the setup ↗Node.js
Call pageflock from your server with the built-in fetch API.
See the setup ↗cURL
Go from a terminal to your first extracted page.
See the setup ↗Go
Use Go's standard HTTP client in a small, typed service.
See the setup ↗Ruby
Call pageflock from Ruby with the standard Net::HTTP library.
See the setup ↗Java
Use Java 11+'s built-in HttpClient without an SDK dependency.
See the setup ↗n8n
Add public page data to an HTTP Request workflow.
See the setup ↗Make
Use an HTTP request to pass web content into a scenario.
See the setup ↗Postman
Explore requests with a ready-to-import API collection.
See the setup ↗Make your next connection.
Choose a paid plan and start gathering useful web data.