Facebook API
Facebook page events
The events a page has published, one page at a time: name, when, where, kind and whether it is online, past or cancelled.
Endpoint
GET/v1/facebook/eventslive · proven2 creditsParameters
Query parameters
| Name | Required | Description | Example |
|---|---|---|---|
url | yes | Page URL | https://www.facebook.com/nasa |
cursor | no | Opaque cursor from the previous page | |
dry_run | no | Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution. | 1 |
Examples
Make the request
curl "https://www.monocrawl.com/v1/facebook/events?url=https%3A%2F%2Fwww.facebook.com%2Fnasa" \ -H "x-api-key: mn_your_key_here"
TypeScript
const key = process.env.MONOCRAWL_API_KEY;
if (!key) throw new Error('Set MONOCRAWL_API_KEY on your server.');
const res = await fetch(
"https://www.monocrawl.com/v1/facebook/events?url=https%3A%2F%2Fwww.facebook.com%2Fnasa",
{ headers: { "x-api-key": key } },
);
const body = await res.json();
if (!body.success) {
// one error shape for every endpoint — see /docs/errors
throw new Error(`${body.error.type}: ${body.error.message}`);
}
console.log(body.data, "credits left:", body.credits_remaining);Python
import os
import requests
res = requests.get(
"https://www.monocrawl.com/v1/facebook/events?url=https%3A%2F%2Fwww.facebook.com%2Fnasa",
headers={"x-api-key": os.environ["MONOCRAWL_API_KEY"]},
timeout=60,
)
body = res.json()
if not body["success"]:
# one error shape for every endpoint — see /docs/errors
raise RuntimeError(f"{body['error']['type']}: {body['error']['message']}")
print(body["data"], "credits left:", body["credits_remaining"])Response
Response fields and example
This example is illustrative, not a captured live response. Variable-cost operations may settle a charge different from the list price below. A successful response puts the platform payload in data and reports the exact credits used, remaining balance, request id and cache status beside it.
{
"success": true,
"platform": "facebook",
"endpoint": "/v1/facebook/events",
"data": {
"_meta": {
"billing": {
"charged": 0,
"list_price": 0,
"reason": "example"
}
},
"cursor": null,
"dropped": 0,
"items": []
},
"credits_used": 2,
"credits_remaining": 99,
"request_id": "req_…",
"cached": false
}The example is illustrative and shows a documented subset of data. The fields below are optional across supported sources; nullable fields can also be absent. Preserve unknown values and accept additional fields.
Schema basis: observed response shapes, not an exhaustive field specification. See schema coverage and validation limits.
Download the data JSON Schema. Validate response.data, not the whole envelope. A valid shape does not establish that every field or source record was returned.
| Field inside data | Type | Meaning |
|---|---|---|
_meta | object | null | Optional meta supplied by this operation. Null means unknown. |
_meta.billing | object | null | Optional billing supplied by this operation. Null means unknown. |
_meta.billing.charged | number | null | Optional charged supplied by this operation. Null means unknown. |
_meta.billing.list_price | number | null | Optional list price supplied by this operation. Null means unknown. |
_meta.billing.reason | string | null | Optional reason supplied by this operation. Null means unknown. |
cursor | string | null | Opaque next-page token; pass it back unchanged. Null does not prove complete history. |
dropped | number | null | Optional dropped supplied by this operation. Null means unknown. |
items | array | null | Source array was empty in the reviewed captures; item fields remain unspecified. |
Optional fields reviewed from preserved successful responses. Additive fields and source variations remain allowed; validate the fields your workflow requires.
The example is invented and illustrates types only; zero and empty values are not claims about a real result.
Failures use the typed error envelope. A confirmed uncharged or refunded failure reports zero; a pending reconciliation can report an unknown charge. Read credits_used and error.details.billing_status, and keep request_id for recovery. Response contract · Error reference