Platforms / Research

Web data, through one API.

Explore 22 documented endpoints for Web. Choose an operation, inspect its inputs, and test the response before adding it to your application.

Web logo

Web API

Public-data endpoint catalog

Documented endpoints
22
Credits per success
From 0

STARTING ENDPOINT

GET /v1/web/scrape

One API key. Shared response metadata. Availability varies by operation during preview.

API catalog

Choose the data you need.

Open an endpoint for its request parameters, examples, and credit cost. Each operation has its own data contract.

Coverage is rolling out during preview. Test the endpoint you need before integrating. Unavailable operations return an explicit error and use no credits.

Web logo

Web Scrape API

Web scrape.

GET1 credit / successView endpoint →
Web logo

Web Search API

Search Web using the documented query and filters, and return structured results.

GET2 credits / successView endpoint →
Web logo

Web Map API

Web map.

GET1 credit / successView endpoint →
Web logo

Web Extract API

Web extract.

GET5 credits / successView endpoint →
Web logo

Web Crawl API

Web crawl.

POST1 credit / successView endpoint →
Web logo

Web Batch Scrape API

Web batch scrape.

POST1 credit / successView endpoint →
Web logo

Web Jobs API

Web jobs.

GET0 credits / successView endpoint →
Web logo

Web Jobs {Job Id} API

Web jobs {job id}.

GET0 credits / successView endpoint →
Web logo

Web Jobs {Job Id} API

Web jobs {job id}.

DELETE0 credits / successView endpoint →
Web logo

Web Agent API

Web agent.

POST25 credits / successView endpoint →
Web logo

Web Monitors API

Web monitors.

POST0 credits / successView endpoint →
Web logo

Web Monitors API

Web monitors.

GET0 credits / successView endpoint →
Web logo

Web Monitors {Monitor Id} API

Web monitors {monitor id}.

GET0 credits / successView endpoint →
Web logo

Web Monitors {Monitor Id} API

Web monitors {monitor id}.

PATCH0 credits / successView endpoint →
Web logo

Web Monitors {Monitor Id} API

Web monitors {monitor id}.

DELETE0 credits / successView endpoint →
Web logo

Web Monitors {Monitor Id} Checks API

Web monitors {monitor id} checks.

GET0 credits / successView endpoint →
Web logo

Web Sessions API

Web sessions.

POST5 credits / successView endpoint →
Web logo

Web Sessions API

Web sessions.

GET0 credits / successView endpoint →
Web logo

Web Sessions {Session Id} API

Web sessions {session id}.

GET0 credits / successView endpoint →
Web logo

Web Sessions {Session Id} API

Web sessions {session id}.

DELETE0 credits / successView endpoint →
Web logo

Web Sessions {Session Id} Execute API

Web sessions {session id} execute.

POST0 credits / successView endpoint →
Web logo

Web Parse API

Web parse.

POST1 credit / successView endpoint →

API playground

Inspect a response before you integrate.

Select an operation and enter its required parameters. Browser tests are protected by Turnstile; an unavailable source returns an error instead of sample data.

Web API22 endpoints documented
View docs
GET/v1/web/scrape?url=https%3A%2F%2Fexample.com
curl -X GET 'https://socialquery.dev/v1/web/scrape?url=https%3A%2F%2Fexample.com' \
  -H "x-api-key: $SOCIALQUERY_API_KEY"
- · idle
// Edit the params above and hit "Try it" to run a live request against the API

From browser to code

Use the same request in your application.

  1. 01 Create a SocialQuery API key and store it on your server.
  2. 02 Send the documented inputs with your x-api-key header.
  3. 03 Check the response status, data, credits, and request ID.
Read the quickstart →

Example request

curl -X GET 'https://socialquery.dev/v1/web/scrape?url=https%3A%2F%2Fexample.com' \
  -H "x-api-key: $SOCIALQUERY_API_KEY"

FAQ

Questions teams ask

Practical answers to help you get started.

Are all Web endpoints available?

+

This is the documented catalog. Live coverage is rolling out during preview and depends on the operation. Test the specific request you need before using it in production.

How are requests charged?

+

The endpoint lists its credit cost before you call it. The response includes credits used and your remaining balance. Unavailable operations use no credits.

Do I need a separate key for each platform?

+

No. Use your SocialQuery key for available endpoints across the catalog. Keep it server-side and pass it in the x-api-key header.

Explore related platforms

Next step

Build with Web data.

Start with a documented endpoint and 100 free signup credits.

Start with free credits