Facebook KeyAPI Data Workflows

Problem

Mapping Facebook lookup, ranking, comparison, and reporting needs directly to web scraping or guessed API calls often leads to incorrect parameters, stale routes, and inconsistent response fields. This skill targets engineers and automation flows: given a business goal, it identifies the relevant Facebook profile, page, group, post, photo, Reel, or event, then retrieves structured data through KeyAPI REST.

Workflow

The core sequence is goal → scenario → docs → call → analysis:

• Decompose the request into Goal, Entity, Scope, Metric, Pagination depth, and output format.
• Select the closest Facebook scenario instead of guessing an endpoint.
• Resolve the current HTTP method, /v1/... path, parameters, pagination, and response shape from KeyAPI docs or the docs-resolution helper.
• Prefer the helper script when available; otherwise execute the same documented REST request with the host HTTP client.
• Separate observed API facts from inferred conclusions so results are not mistaken for certainty.

Boundaries

It is suitable for querying and comparing public Facebook profiles, pages, groups, posts, photos, Reels, and events. It does not bypass login, scrape private data, or replace KeyAPI official documentation. For broad reports, confirm sections, time windows, and maximum scope first; if KEYAPI_TOKEN is unavailable, pause live execution and use the setup flow rather than falling back to web browsing.