# Facebook Events API Reference Canonical: https://monsterapi.co/docs/api/facebook-events Read the Facebook Events reference. Review parameters, response fields, examples, and current credit prices. OpenAPI specification: [Facebook](https://monsterapi.co/docs/openapi/platforms/facebook.yaml). --- Current operation prices: [public catalog](https://monsterapi.co/account/api/v1/public/api-prices). Prices use credits per request. --- # Facebook: Event venue and ticket details `GET /facebook/api/events/about` Documentation: https://monsterapi.co/docs/api/facebook#facebook-event-venue-and-ticket-details Operation ID: `facebook_events_about` Returns event description, schedule, venue, creator, attendance and ticket link when available. Pass event_id. ## Authentication Send your billing API key in the `Authorization: Bearer ` header. Your account login is separate. ## Inputs - `event_id` (query, required): Numeric event ID. ## Responses - 200: Requested information in data and its named fields; unavailable optional values are null. - 400: A request parameter is invalid. Refused at the gateway: the request target, path and query string together, is longer than 8,192 bytes; or the headers, the target counted among them, exceed 16,384 bytes or 64 fields - 401: #/components/responses/GatewayUnauthorized - 402: #/components/responses/GatewayPaymentRequired - 403: #/components/responses/GatewayForbidden - 404: The requested object is absent, or Facebook does not show it to logged-out visitors. An empty page of an object that exists does not return `404`. - 405: `method_not_allowed`: the endpoint answers GET alone, and any other method, HEAD included, is refused Refused at the gateway: the path exists, but no operation on it takes the method of the request, HEAD included; `Allow` names the methods that do - 409: #/components/responses/GatewayConflict - 429: `rate_limited`: Facebook limited the requests or asked a logged-out visitor to sign in. Wait for the seconds in `Retry-After`, then repeat the request. Facebook publishes no numbers for these limits. Refused at the gateway: the account calls faster than its rate limit allows - 500: The requested information could not be returned. - 501: The requested information is unavailable without signing in or is not supported. - 503: The requested information is temporarily unavailable. Repeat the request later. `code` gives the cause: - `upstream_error`: no answer came from Facebook, or Facebook answered with a server error. Wait for the seconds in `Retry-After`, then repeat the request. - `upstream_stale`: the service is renewing its access to this information. - `no_proxies`: the service cannot get this kind of information at the moment. - `overloaded`: the service is handling too many requests at the same time. Repeat the request after a short pause, or send fewer requests at the same time. Refused at the gateway: the check could not complete, the account is suspended, or the platform did not answer; each may pass later, and `Retry-After` comes only when the platform did not answer ## Credits Check the live price in the documentation before sending. Platform 2xx and 4xx responses can use credits, including empty data. Gateway refusals and 5xx responses do not use credits. Each pagination request is a separate call. https://monsterapi.co/docs/pricing ## Request template Replace path placeholders and add the required query parameters from the Inputs section before sending. ```shell curl --get 'https://api.monsterapi.co/facebook/api/events/about' \ -H 'Authorization: Bearer ' ``` --- # Facebook: Event identity and schedule `GET /facebook/api/events/header` Documentation: https://monsterapi.co/docs/api/facebook#facebook-event-identity-and-schedule Operation ID: `facebook_events_header` Returns event identity, start time, location, cover and attendance summary when available. Pass event_id. ## Authentication Send your billing API key in the `Authorization: Bearer ` header. Your account login is separate. ## Inputs - `event_id` (query, required): Numeric event ID. ## Responses - 200: Requested information in data and its named fields; unavailable optional values are null. - 400: A request parameter is invalid. Refused at the gateway: the request target, path and query string together, is longer than 8,192 bytes; or the headers, the target counted among them, exceed 16,384 bytes or 64 fields - 401: #/components/responses/GatewayUnauthorized - 402: #/components/responses/GatewayPaymentRequired - 403: #/components/responses/GatewayForbidden - 404: The requested object is absent, or Facebook does not show it to logged-out visitors. An empty page of an object that exists does not return `404`. - 405: `method_not_allowed`: the endpoint answers GET alone, and any other method, HEAD included, is refused Refused at the gateway: the path exists, but no operation on it takes the method of the request, HEAD included; `Allow` names the methods that do - 409: #/components/responses/GatewayConflict - 429: `rate_limited`: Facebook limited the requests or asked a logged-out visitor to sign in. Wait for the seconds in `Retry-After`, then repeat the request. Facebook publishes no numbers for these limits. Refused at the gateway: the account calls faster than its rate limit allows - 500: The requested information could not be returned. - 501: The requested information is unavailable without signing in or is not supported. - 503: The requested information is temporarily unavailable. Repeat the request later. `code` gives the cause: - `upstream_error`: no answer came from Facebook, or Facebook answered with a server error. Wait for the seconds in `Retry-After`, then repeat the request. - `upstream_stale`: the service is renewing its access to this information. - `no_proxies`: the service cannot get this kind of information at the moment. - `overloaded`: the service is handling too many requests at the same time. Repeat the request after a short pause, or send fewer requests at the same time. Refused at the gateway: the check could not complete, the account is suspended, or the platform did not answer; each may pass later, and `Retry-After` comes only when the platform did not answer ## Credits Check the live price in the documentation before sending. Platform 2xx and 4xx responses can use credits, including empty data. Gateway refusals and 5xx responses do not use credits. Each pagination request is a separate call. https://monsterapi.co/docs/pricing ## Request template Replace path placeholders and add the required query parameters from the Inputs section before sending. ```shell curl --get 'https://api.monsterapi.co/facebook/api/events/header' \ -H 'Authorization: Bearer ' ``` --- # Facebook: Event link preview `GET /facebook/api/events/mobile` Documentation: https://monsterapi.co/docs/api/facebook#facebook-event-link-preview Operation ID: `facebook_events_mobile` Returns event link-preview metadata, including title, description and image when available. Pass event_id. ## Authentication Send your billing API key in the `Authorization: Bearer ` header. Your account login is separate. ## Inputs - `event_id` (query, required): Numeric event ID. ## Responses - 200: Requested information; unavailable optional values are null. - 400: A request parameter is invalid. Refused at the gateway: the request target, path and query string together, is longer than 8,192 bytes; or the headers, the target counted among them, exceed 16,384 bytes or 64 fields - 401: #/components/responses/GatewayUnauthorized - 402: #/components/responses/GatewayPaymentRequired - 403: #/components/responses/GatewayForbidden - 404: The requested object is absent, or Facebook does not show it to logged-out visitors. An empty page of an object that exists does not return `404`. - 405: `method_not_allowed`: the endpoint answers GET alone, and any other method, HEAD included, is refused Refused at the gateway: the path exists, but no operation on it takes the method of the request, HEAD included; `Allow` names the methods that do - 409: #/components/responses/GatewayConflict - 429: `rate_limited`: Facebook limited the requests or asked a logged-out visitor to sign in. Wait for the seconds in `Retry-After`, then repeat the request. Facebook publishes no numbers for these limits. Refused at the gateway: the account calls faster than its rate limit allows - 500: The requested information could not be returned. - 501: The requested information is unavailable without signing in or is not supported. - 503: The requested information is temporarily unavailable. Repeat the request later. `code` gives the cause: - `upstream_error`: no answer came from Facebook, or Facebook answered with a server error. Wait for the seconds in `Retry-After`, then repeat the request. - `upstream_stale`: the service is renewing its access to this information. - `no_proxies`: the service cannot get this kind of information at the moment. - `overloaded`: the service is handling too many requests at the same time. Repeat the request after a short pause, or send fewer requests at the same time. Refused at the gateway: the check could not complete, the account is suspended, or the platform did not answer; each may pass later, and `Retry-After` comes only when the platform did not answer ## Credits Check the live price in the documentation before sending. Platform 2xx and 4xx responses can use credits, including empty data. Gateway refusals and 5xx responses do not use credits. Each pagination request is a separate call. https://monsterapi.co/docs/pricing ## Request template Replace path placeholders and add the required query parameters from the Inputs section before sending. ```shell curl --get 'https://api.monsterapi.co/facebook/api/events/mobile' \ -H 'Authorization: Bearer ' ``` --- # Facebook: Place events with pagination `GET /facebook/api/events/place/page` Documentation: https://monsterapi.co/docs/api/facebook#facebook-place-events-with-pagination Operation ID: `facebook_events_place_page` Returns events for a place with names, dates, locations and cover images. Pass location_id and optionally cursor to continue. ## Authentication Send your billing API key in the `Authorization: Bearer ` header. Your account login is separate. ## Inputs - `location_id` (query, required): Numeric city page ID. An ID that is not a city page, such as a page profile ID, returns `upstream_shape`. A city page without events returns an empty `events` list. - `cursor` (query, optional): `next_cursor` from [/events/place/render](https://monsterapi.co/docs/api/facebook-events#facebook-place-details-and-event-previews) or this endpoint. Pass it unchanged with the same `location_id`. ## Responses - 200: Requested information in data and its named fields; unavailable optional values are null. - 400: A request parameter is invalid. Refused at the gateway: the request target, path and query string together, is longer than 8,192 bytes; or the headers, the target counted among them, exceed 16,384 bytes or 64 fields - 401: #/components/responses/GatewayUnauthorized - 402: #/components/responses/GatewayPaymentRequired - 403: #/components/responses/GatewayForbidden - 404: The requested object is absent, or Facebook does not show it to logged-out visitors. An empty page of an object that exists does not return `404`. - 405: `method_not_allowed`: the endpoint answers GET alone, and any other method, HEAD included, is refused Refused at the gateway: the path exists, but no operation on it takes the method of the request, HEAD included; `Allow` names the methods that do - 409: #/components/responses/GatewayConflict - 429: `rate_limited`: Facebook limited the requests or asked a logged-out visitor to sign in. Wait for the seconds in `Retry-After`, then repeat the request. Facebook publishes no numbers for these limits. Refused at the gateway: the account calls faster than its rate limit allows - 500: The requested information could not be returned. - 501: The requested information is unavailable without signing in or is not supported. - 503: The requested information is temporarily unavailable. Repeat the request later. `code` gives the cause: - `upstream_error`: no answer came from Facebook, or Facebook answered with a server error. Wait for the seconds in `Retry-After`, then repeat the request. - `upstream_stale`: the service is renewing its access to this information. - `no_proxies`: the service cannot get this kind of information at the moment. - `overloaded`: the service is handling too many requests at the same time. Repeat the request after a short pause, or send fewer requests at the same time. Refused at the gateway: the check could not complete, the account is suspended, or the platform did not answer; each may pass later, and `Retry-After` comes only when the platform did not answer ## Credits Check the live price in the documentation before sending. Platform 2xx and 4xx responses can use credits, including empty data. Gateway refusals and 5xx responses do not use credits. Each pagination request is a separate call. https://monsterapi.co/docs/pricing ## Request template Replace path placeholders and add the required query parameters from the Inputs section before sending. ```shell curl --get 'https://api.monsterapi.co/facebook/api/events/place/page' \ -H 'Authorization: Bearer ' ``` --- # Facebook: Place details and event previews `GET /facebook/api/events/place/render` Documentation: https://monsterapi.co/docs/api/facebook#facebook-place-details-and-event-previews Operation ID: `facebook_events_place_render` Returns place information, event previews, categories and continuation. Pass location_id. ## Authentication Send your billing API key in the `Authorization: Bearer ` header. Your account login is separate. ## Inputs - `location_id` (query, required): Numeric city page ID. Facebook answers an ID that is not a city page, such as a page profile ID, with a server error, and the request returns `upstream_error`. In every measurement, a repeated request with such an ID got the same refusal. ## Responses - 200: Requested information; unavailable optional values are null. - 400: A request parameter is invalid. Refused at the gateway: the request target, path and query string together, is longer than 8,192 bytes; or the headers, the target counted among them, exceed 16,384 bytes or 64 fields - 401: #/components/responses/GatewayUnauthorized - 402: #/components/responses/GatewayPaymentRequired - 403: #/components/responses/GatewayForbidden - 404: The requested object is absent, or Facebook does not show it to logged-out visitors. An empty page of an object that exists does not return `404`. - 405: `method_not_allowed`: the endpoint answers GET alone, and any other method, HEAD included, is refused Refused at the gateway: the path exists, but no operation on it takes the method of the request, HEAD included; `Allow` names the methods that do - 409: #/components/responses/GatewayConflict - 429: `rate_limited`: Facebook limited the requests or asked a logged-out visitor to sign in. Wait for the seconds in `Retry-After`, then repeat the request. Facebook publishes no numbers for these limits. Refused at the gateway: the account calls faster than its rate limit allows - 500: The requested information could not be returned. - 501: The requested information is unavailable without signing in or is not supported. - 503: The requested information is temporarily unavailable. Repeat the request later. `code` gives the cause: - `upstream_error`: no answer came from Facebook, or Facebook answered with a server error. Wait for the seconds in `Retry-After`, then repeat the request. - `upstream_stale`: the service is renewing its access to this information. - `no_proxies`: the service cannot get this kind of information at the moment. - `overloaded`: the service is handling too many requests at the same time. Repeat the request after a short pause, or send fewer requests at the same time. Refused at the gateway: the check could not complete, the account is suspended, or the platform did not answer; each may pass later, and `Retry-After` comes only when the platform did not answer ## Credits Check the live price in the documentation before sending. Platform 2xx and 4xx responses can use credits, including empty data. Gateway refusals and 5xx responses do not use credits. Each pagination request is a separate call. https://monsterapi.co/docs/pricing ## Request template Replace path placeholders and add the required query parameters from the Inputs section before sending. ```shell curl --get 'https://api.monsterapi.co/facebook/api/events/place/render' \ -H 'Authorization: Bearer ' ```