Docs menu

Datasets API endpoint

Search the Facebook Pages dataset API

Use Crawlora's Search the Facebook Pages dataset API to search or inspect stored structured datasets as JSON. This page includes request parameters, cURL examples, response schema, validation behavior, credit cost, and a Playground link for testing before integration. Dataset endpoints read indexed records and do not apply proxy routing.

GETapiKey2 credits/requestDatasetsdatasets.facebookPagesSearchResponseDoc/datasets/facebook-pages/search

Endpoint facts

Method: GET
API path: /datasets/facebook-pages/search
Auth: apiKey
Credits: 2 credits/request
Platform: Datasets
Response schema: #/definitions/datasets.facebookPagesSearchResponseDoc

Overview

Searches public Facebook Page contact records stored in a search index — website, email, phone, WhatsApp, category and like count, discovered through business-search enumeration, domain-scoped scans, and Wikidata seeding, then hydrated from each Page's public About tab. Sort enum: `relevance`, `likes_desc`, `likes_asc`, `hydrated_at_desc`, `hydrated_at_asc`. Developers commonly use this endpoint for repeatable dataset search, filtering, facets, local business enrichment, analytics, exports, and internal tools that need structured records beyond the limited manual refinement available in the Google Maps app. Authentication uses the x-api-key header, usage is metered with the credit cost shown on this page, and the request does not trigger live scraping or proxy routing.

Stored structured dataset search API Try Search the Facebook Pages dataset API in Playground Crawlora API pricing Datasets API documentation

Request parameters

Request parameters are generated from the active endpoint catalog. Dataset parameters filter, page, facet, or locate stored structured records; they do not configure a live scraper or proxy path.

Parameter	Type	Required	Default	Description
q	string	No		Full-text query over title and address, max 256 characters
page_id	string	No		Exact Facebook Page id filter, max 128 characters
identifier	string	No		Exact Page username/identifier filter (case-insensitive), max 128 characters
category	string	No		Exact Page category filter (case-insensitive), max 128 characters
discovery_source	string	No		Exact filter for how the Page was discovered (e.g. business_search, warc_domain_scan, wikidata), max 128 characters
has_website	boolean	No		Filter by a linked website
has_email	boolean	No		Filter by a public contact email
has_phone	boolean	No		Filter by at least one public phone number
has_whatsapp	boolean	No		Filter by a public WhatsApp contact
min_likes	integer	No		Minimum Page like count
max_likes	integer	No		Maximum Page like count
hydrated_after	string	No		Records last refreshed on or after this date (RFC3339 or YYYY-MM-DD)
hydrated_before	string	No		Records last refreshed on or before this date (RFC3339 or YYYY-MM-DD)
sort	string	No		Sort enum: relevance, likes_desc, likes_asc, hydrated_at_desc, hydrated_at_asc Allowed values: relevance, likes_desc, likes_asc, hydrated_at_desc, hydrated_at_asc
page	integer	No	1	Page number, defaults to 1
page_size	integer	No	20 and maxes at 100	Page size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/datasets/facebook-pages/search?q=coffee&has_website=true&has_email=true&has_phone=true&has_whatsapp=true&sort=relevance&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost: 2 credits/request
Charged response: Successful 2xx responses

Plan	Price	Included credits	Daily cap	Rate limit	Overage
Free	$0/mo	2,000	500 daily credits	5/min	No overage
Starter	$9/mo	20,000	5,000 daily credits	15/min	$0.75/1,000 overage credits when enabled
Growth	$29/mo	100,000	25,000 daily credits	45/min	$0.45/1,000 overage credits when enabled
Pro	$79/mo	400,000	No daily cap	120/min	$0.30/1,000 overage credits
Business	$199/mo	1,200,000	No daily cap	300/min	$0.20/1,000 overage credits
Enterprise	$499/mo	5,000,000	No daily cap	1,000/min	$0.12/1,000 overage credits

Infrastructure behavior

This endpoint reads stored indexed dataset records. It does not execute a live upstream Google Maps request, browser session, or proxy-routed scraping job.

Data source: stored Crawlora dataset records
Proxy strategy: no proxy routing is applied
Browser rendering: not used for dataset search or lookup requests
Live scraping: not triggered by dataset list, search, nearby, facet, or detail endpoints
Validation: invalid filters, coordinates, pagination, and enum values return documented errors
Billing: credits are charged only for successful 2xx responses
Observability: responses include request context where available

Response behavior

- Defaults to `relevance` sort when `q` is supplied, otherwise `likes_desc`. - `min_likes` must not exceed `max_likes`. - Date filters accept an RFC3339 timestamp or a bare `YYYY-MM-DD` calendar date. - The maximum result window is `10000`; `page * page_size` must not exceed `10000`. - Only successfully hydrated Pages are ever returned. - Does not trigger live scraping. Example response: ```json { "code": 200, "msg": "OK", "data": { "dataset": "facebook-pages", "items": [ { "page_id": "104958closes123", "identifier": "bata.official", "title": "Bata", "source_url": "https://www.facebook.com/bata.official", "website": "https://www.bata.com", "email": "customercare@bata.com", "phones": ["+91-1800-121-9800"], "address": "Mumbai, India", "category": "Shoe Store", "whatsapp": "", "likes": 5200000, "discovery_source": "wikidata", "status": "ok", "discovered_at": "2026-07-30T00:00:00Z", "hydrated_at": "2026-08-15T00:00:00Z" } ], "page": 1, "page_size": 20, "total": 1231862, "sort": "likes_desc" } } ```

Error behavior

Crawlora does not silently return invalid dataset search results when filters, pagination, coordinates, or stored record lookups cannot be satisfied.

Status	Common failure case
400	Invalid input, missing required parameter, invalid enum, bad coordinate pair, or result window beyond the dataset limit
404	Requested stored dataset item is not present
429	Plan or endpoint rate limit exceeded
500	Internal dataset query or storage error

When possible, Crawlora returns structured error context so your integration can adjust filters, page size, location inputs, or lookup identifiers.

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
429	Too Many Requests	#/definitions/app.Response
500	Internal Server Error	#/definitions/app.Response

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "dataset": "facebook-pages",
    "items": [
      {
        "page_id": "104958closes123",
        "identifier": "bata.official",
        "title": "Bata",
        "source_url": "https://www.facebook.com/bata.official",
        "website": "https://www.bata.com",
        "email": "customercare@bata.com",
        "phones": [
          "+91-1800-121-9800"
        ],
        "address": "Mumbai, India",
        "category": "Shoe Store",
        "whatsapp": "",
        "likes": 5200000,
        "discovery_source": "wikidata",
        "status": "ok",
        "discovered_at": "2026-07-30T00:00:00Z",
        "hydrated_at": "2026-08-15T00:00:00Z"
      }
    ],
    "page": 1,
    "page_size": 20,
    "total": 1231862,
    "sort": "likes_desc"
  }
}

Request schema

No body schema

Response schema

#/definitions/datasets.facebookPagesSearchResponseDoc

Field	Type	Required	Example
code	integer	No	200
data	datasets.FacebookPageSearchResponse	No
data.dataset	string	No
data.items	array	No
data.items[].address	string	No
data.items[].category	string	No
data.items[].discovered_at	string	No
data.items[].discovery_source	string	No
data.items[].email	string	No
data.items[].hydrated_at	string	No
data.items[].identifier	string	No
data.items[].likes	integer	No
data.items[].page_id	string	No
data.items[].phones	array	No
data.items[].source_url	string	No
data.items[].status	string	No
data.items[].title	string	No
data.items[].website	string	No
data.items[].whatsapp	string	No
data.page	integer	No
data.page_size	integer	No
data.sort	string	No
data.total	integer	No
msg	string	No	OK

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/datasets/facebook-pages/search?q=coffee&has_website=true&has_email=true&has_phone=true&has_whatsapp=true&sort=relevance&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Responsible public web data workflows

Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.

Read Crawlora terms

More Datasets endpoint docs Stored structured dataset search API Crawlora API pricing Try Search the Facebook Pages dataset API in Playground Stored Datasets List API documentation Airbnb Markets Dataset Facets API documentation Airbnb Markets Dataset Country API documentation Nearby Airbnb Markets Dataset API documentation Airbnb Markets Dataset Search API documentation Facet Apple Podcasts shows dataset API documentation

Open in Playground Back to group

Docs menu

Datasets API endpoint

Search the Facebook Pages dataset API

GETapiKey2 credits/requestDatasetsdatasets.facebookPagesSearchResponseDoc/datasets/facebook-pages/search

Endpoint facts

Method: GET
API path: /datasets/facebook-pages/search
Auth: apiKey
Credits: 2 credits/request
Platform: Datasets
Response schema: #/definitions/datasets.facebookPagesSearchResponseDoc

Overview

Stored structured dataset search API Try Search the Facebook Pages dataset API in Playground Crawlora API pricing Datasets API documentation

Request parameters

Request parameters are generated from the active endpoint catalog. Dataset parameters filter, page, facet, or locate stored structured records; they do not configure a live scraper or proxy path.

Parameter	Type	Required	Default	Description
q	string	No		Full-text query over title and address, max 256 characters
page_id	string	No		Exact Facebook Page id filter, max 128 characters
identifier	string	No		Exact Page username/identifier filter (case-insensitive), max 128 characters
category	string	No		Exact Page category filter (case-insensitive), max 128 characters
discovery_source	string	No		Exact filter for how the Page was discovered (e.g. business_search, warc_domain_scan, wikidata), max 128 characters
has_website	boolean	No		Filter by a linked website
has_email	boolean	No		Filter by a public contact email
has_phone	boolean	No		Filter by at least one public phone number
has_whatsapp	boolean	No		Filter by a public WhatsApp contact
min_likes	integer	No		Minimum Page like count
max_likes	integer	No		Maximum Page like count
hydrated_after	string	No		Records last refreshed on or after this date (RFC3339 or YYYY-MM-DD)
hydrated_before	string	No		Records last refreshed on or before this date (RFC3339 or YYYY-MM-DD)
sort	string	No		Sort enum: relevance, likes_desc, likes_asc, hydrated_at_desc, hydrated_at_asc Allowed values: relevance, likes_desc, likes_asc, hydrated_at_desc, hydrated_at_asc
page	integer	No	1	Page number, defaults to 1
page_size	integer	No	20 and maxes at 100	Page size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/datasets/facebook-pages/search?q=coffee&has_website=true&has_email=true&has_phone=true&has_whatsapp=true&sort=relevance&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost: 2 credits/request
Charged response: Successful 2xx responses

Plan	Price	Included credits	Daily cap	Rate limit	Overage
Free	$0/mo	2,000	500 daily credits	5/min	No overage
Starter	$9/mo	20,000	5,000 daily credits	15/min	$0.75/1,000 overage credits when enabled
Growth	$29/mo	100,000	25,000 daily credits	45/min	$0.45/1,000 overage credits when enabled
Pro	$79/mo	400,000	No daily cap	120/min	$0.30/1,000 overage credits
Business	$199/mo	1,200,000	No daily cap	300/min	$0.20/1,000 overage credits
Enterprise	$499/mo	5,000,000	No daily cap	1,000/min	$0.12/1,000 overage credits

Infrastructure behavior

This endpoint reads stored indexed dataset records. It does not execute a live upstream Google Maps request, browser session, or proxy-routed scraping job.

Data source: stored Crawlora dataset records
Proxy strategy: no proxy routing is applied
Browser rendering: not used for dataset search or lookup requests
Live scraping: not triggered by dataset list, search, nearby, facet, or detail endpoints
Validation: invalid filters, coordinates, pagination, and enum values return documented errors
Billing: credits are charged only for successful 2xx responses
Observability: responses include request context where available

Response behavior

Error behavior

Crawlora does not silently return invalid dataset search results when filters, pagination, coordinates, or stored record lookups cannot be satisfied.

Status	Common failure case
400	Invalid input, missing required parameter, invalid enum, bad coordinate pair, or result window beyond the dataset limit
404	Requested stored dataset item is not present
429	Plan or endpoint rate limit exceeded
500	Internal dataset query or storage error

When possible, Crawlora returns structured error context so your integration can adjust filters, page size, location inputs, or lookup identifiers.

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
429	Too Many Requests	#/definitions/app.Response
500	Internal Server Error	#/definitions/app.Response

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "dataset": "facebook-pages",
    "items": [
      {
        "page_id": "104958closes123",
        "identifier": "bata.official",
        "title": "Bata",
        "source_url": "https://www.facebook.com/bata.official",
        "website": "https://www.bata.com",
        "email": "customercare@bata.com",
        "phones": [
          "+91-1800-121-9800"
        ],
        "address": "Mumbai, India",
        "category": "Shoe Store",
        "whatsapp": "",
        "likes": 5200000,
        "discovery_source": "wikidata",
        "status": "ok",
        "discovered_at": "2026-07-30T00:00:00Z",
        "hydrated_at": "2026-08-15T00:00:00Z"
      }
    ],
    "page": 1,
    "page_size": 20,
    "total": 1231862,
    "sort": "likes_desc"
  }
}

Request schema

No body schema

Response schema

#/definitions/datasets.facebookPagesSearchResponseDoc

Field	Type	Required	Example
code	integer	No	200
data	datasets.FacebookPageSearchResponse	No
data.dataset	string	No
data.items	array	No
data.items[].address	string	No
data.items[].category	string	No
data.items[].discovered_at	string	No
data.items[].discovery_source	string	No
data.items[].email	string	No
data.items[].hydrated_at	string	No
data.items[].identifier	string	No
data.items[].likes	integer	No
data.items[].page_id	string	No
data.items[].phones	array	No
data.items[].source_url	string	No
data.items[].status	string	No
data.items[].title	string	No
data.items[].website	string	No
data.items[].whatsapp	string	No
data.page	integer	No
data.page_size	integer	No
data.sort	string	No
data.total	integer	No
msg	string	No	OK

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/datasets/facebook-pages/search?q=coffee&has_website=true&has_email=true&has_phone=true&has_whatsapp=true&sort=relevance&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Responsible public web data workflows

Read Crawlora terms

Open in Playground Back to group

Search the Facebook Pages dataset API

Endpoint facts

Overview

Request parameters

cURL example

Authentication

Billing

Infrastructure behavior

Response behavior

Error behavior

Failure responses

Example JSON response

Code examples

Responsible public web data workflows

Related

Search the Facebook Pages dataset API

Endpoint facts

Overview

Request parameters

cURL example

Authentication

Billing

Infrastructure behavior

Response behavior

Error behavior

Failure responses

Example JSON response

Code examples

Responsible public web data workflows

Related