Capture API calls and network requests from any page. Discover hidden APIs, reverse engineer endpoints, and generate production-ready code in any language.
Install the SocialAPIs Network Inspector extension to capture requests from any page — including login-walled sites, single-page apps, and sites with bot protection.
Use the Chrome Extension to capture all API calls and HTML requests from any page, even behind login walls.
Search response bodies for specific terms. Filter by URL, method, status, or content type.
Get production-ready cURL, Python, JavaScript, Java, or Go code. Test requests instantly.
A browser-based traffic capture that filters down to API calls worth reverse-engineering, then turns each one into a clean cURL command (or code in your language) with one click. Built for the moment when you can see the data you want in someone's web UI and you need to figure out the API call behind it to pull the same data from your own code.
Reverse-engineering gets you started, but it doesn't survive the first time the vendor changes their API contract. For Facebook and Instagram specifically, that happens often enough that maintaining your own scrape is a real ongoing cost. Our REST API handles upstream changes on our side; you get a stable contract and an SLA. For everything outside Meta, the inspector is the right tool — it's a bridge, not a destination.
It zeroes in on the requests that are useful for reverse-engineering an API — XHR/fetch only, automatic detection of auth headers, automatic deduplication of polling requests — and turns each one into a clean cURL or code snippet in one click. Chrome devtools has all of this in principle, but you spend 20 minutes filtering out noise (images, fonts, telemetry pings). The inspector is the dedicated workflow for the 'I want to call this API from my own code' case.
Yes. It runs as a browser extension and captures requests from whichever tab you point it at. Works on public sites you have permission to scrape from, internal admin tools you're building integrations against, your own staging environment for debugging — anywhere you would normally open Chrome devtools' Network tab. Don't use it on sites whose ToS prohibit programmatic access.
It doesn't, directly. The inspector is a general developer tool — it works on any website. SocialAPIs covers Facebook + Instagram (and growing) via a hosted REST API with auth, rate limits, and SLA you can't build by reverse-engineering on your own. For everything outside Meta, the inspector is the bridge from 'I can see the data in the browser' to 'I can call the API from my code'.
cURL (the canonical share-it-with-a-teammate format), plus JavaScript (fetch + axios), Python (requests), Java (HttpClient), Go (net/http), and PHP (cURL extension). Each one is a complete, runnable snippet — headers, query string, body, and auth all included. Paste it into your code and it works.
JSON path selector · cURL → code converter · Visual CSS selector · JSON formatter