IngiaAnza kipindi cha majaribio bila malipo
easyCoexistence API rasmi

Facebook Pages API katika Python na Node.js: mifano inayofanya kazi

Python na Node.js huita Facebook Pages API kama ombi rahisi la HTTPS kwa graph.facebook.com/v26.0 kwa kutumia token ya ufikiaji ya Ukurasa. POST /{page-id}/feed na /{page-id}/photos huchapisha, /{post-id}/comments husoma na kujibu maoni, POST /{page-id}/messages hujibu kwenye Messenger, GET /{page-id}/insights husoma vipimo, na HMAC-SHA256 ya mwili ghafi wa ombi hukagua X-Hub-Signature-256 kwenye kila webhook.

easyCoexistence hutoa kazi hizi kwa Ukurasa uliounganishwa kama zana za MCP, kuanzia publish_facebook_post na reply_to_comment hadi send_social_dm na get_social_insights, husambaza matukio yake yakiwa yametiwa sahihi kwa X-EC-Signature, na humpa msimbo wako kitambulisho cha Ukurasa na msingi wa API kupitia get_social_credentials.

caption

Parameter ya text ya picha ya Ukurasa; marejeo ya picha ya Meta yanaonyesha parameter ya `message` imepitwa na wakati hapo.

X-Business-Use-Case-Usage

Kichwa cha jibu ambacho estimated_time_to_regain_access inatoa idadi ya dakika hadi maombi yaliyozuiliwa yaanze kufanya kazi tena.

RESPONSE

messaging_type kwa jibu la ujumbe ambao Ukurasa ulipokea, unaotumwa ndani ya dirisha la saa 24.

recipient.comment_id

Jinsi jibu la faragha linavyomlenga mtu aliyetoa maoni, kupitia endpoint ile ile ya /{page-id}/messages.

Mifano inahitaji nini kabla ya kuendeshwa?

Kitambulisho cha Ukurasa na token ya ufikiaji ya Ukurasa huo, zinazosomwa kutoka /me/accounts kwa kutumia token ya mtumiaji ya muda mrefu, pamoja na Python 3 yenye requests, au Node.js 18 au zaidi, ambayo fetch yake iliyojengwa ndani haihitaji package yoyote. Kila kazi pia inahitaji ruhusa yake kwenye token na jukumu lake kwenye Ukurasa, na mifano hii inaita Graph API v26.0:

Publish a post or photoPOST /{page-id}/feed and /{page-id}/photos: pages_manage_posts, CREATE_CONTENT
Read and reply to comments/{post-id}/comments and /{comment-id}/comments: pages_manage_engagement, MODERATE
Reply in MessengerPOST /{page-id}/messages: pages_messaging, MESSAGING
Read insightsGET /{page-id}/insights: read_insights, pages_read_engagement, ANALYZE
Check a webhookX-Hub-Signature-256, with the app secret and no token

Unachapishaje chapisho na picha kwa Python?

Kwa msaidizi mmoja ambao mifano inayofuata inautumia tena: graph() huongeza token ya Ukurasa, hutuma parameter za GET kwenye query string na fields za POST kama JSON, kama mifano ya Meta yenyewe inavyofanya, na hubadilisha kitu cha hitilafu cha Meta kuwa GraphError kinachobeba code na error_subcode. Hungoja na kujaribu tena kwa misimbo ya muda na ya kikomo cha kasi pekee, kwa muda ambao X-Business-Use-Case-Usage inataka wakati kichwa hicho kinarudi, na hutupa zilizobaki papo hapo.

Python: graph(), then a post and a photo
import json, os, time
import requests

GRAPH = "https://graph.facebook.com/v26.0"
PAGE_ID = os.environ["PAGE_ID"]
PAGE_TOKEN = os.environ["PAGE_TOKEN"]  # the Page's own token, from /me/accounts
RETRY = {1, 2, 4, 17, 32, 613, 80001}   # temporary or rate limited


class GraphError(Exception):
    def __init__(self, err):
        super().__init__(err.get("message"))
        self.code, self.subcode = err.get("code"), err.get("error_subcode")


def wait_seconds(response, attempt):
    usage = json.loads(response.headers.get("x-business-use-case-usage", "{}"))
    minutes = [u.get("estimated_time_to_regain_access", 0) for v in usage.values() for u in v]
    return max([60 * m for m in minutes] + [30 * 2 ** attempt])


def graph(method, path, retries=3, **fields):
    fields["access_token"] = PAGE_TOKEN
    send = {"params": fields} if method == "GET" else {"json": fields}
    for attempt in range(retries + 1):
        response = requests.request(method, f"{GRAPH}/{path}", timeout=30, **send)
        body = response.json()
        if "error" not in body:
            return body
        err = GraphError(body["error"])
        if err.code not in RETRY or attempt == retries:
            raise err
        time.sleep(wait_seconds(response, attempt))


post = graph("POST", f"{PAGE_ID}/feed", message="Open until 11pm this Friday.")
photo = graph("POST", f"{PAGE_ID}/photos",
              url="https://example.com/menu.jpg", caption="This week's menu")
print(post["id"], photo["post_id"])

Unachapisha vipi kwa Node.js?

Kwa msaidizi ule ule kwenye Node.js 18 au zaidi, uliohifadhiwa kama faili la .mjs ili top-level await ifanye kazi, na fetch iliyojengwa ndani badala ya maktaba ya mteja. Wito wa picha hutuma url na caption, yaani field ya text ya edge ya photos; Meta hujibu kwa id ya picha na post_id ya chapisho la Ukurasa linalobeba picha, huku wito wa feed ukijibu kwa id ya chapisho pekee.

Node.js: graph(), then a post and a photo
// Node.js 18 or later, saved as an .mjs file: fetch and top-level await are built in.
const GRAPH = "https://graph.facebook.com/v26.0";
const { PAGE_ID, PAGE_TOKEN } = process.env; // the Page's own token, from /me/accounts
const RETRY = new Set([1, 2, 4, 17, 32, 613, 80001]); // temporary or rate limited

class GraphError extends Error {
  constructor(err) {
    super(err.message);
    this.code = err.code;
    this.subcode = err.error_subcode;
  }
}

function waitMs(response, attempt) {
  const usage = JSON.parse(response.headers.get("x-business-use-case-usage") ?? "{}");
  const minutes = Object.values(usage).flat().map((u) => u.estimated_time_to_regain_access ?? 0);
  return Math.max(30_000 * 2 ** attempt, ...minutes.map((m) => m * 60_000));
}

async function graph(method, path, fields = {}, retries = 3) {
  const url = new URL(`${GRAPH}/${path}`);
  const init = { method };
  const all = { ...fields, access_token: PAGE_TOKEN };
  if (method === "GET") {
    for (const [key, value] of Object.entries(all)) url.searchParams.set(key, String(value));
  } else {
    init.headers = { "Content-Type": "application/json" };
    init.body = JSON.stringify(all);
  }
  for (let attempt = 0; ; attempt++) {
    const response = await fetch(url, init);
    const body = await response.json();
    if (!body.error) return body;
    if (!RETRY.has(body.error.code) || attempt === retries) throw new GraphError(body.error);
    await new Promise((done) => setTimeout(done, waitMs(response, attempt)));
  }
}

const post = await graph("POST", `${PAGE_ID}/feed`, { message: "Open until 11pm this Friday." });
const photo = await graph("POST", `${PAGE_ID}/photos`, {
  url: "https://example.com/menu.jpg",
  caption: "This week's menu",
});
console.log(post.id, photo.post_id);

Unasomaje na kujibu maoni kwa Python?

Soma maoni ya chapisho kwa fields, filter=stream kwa maoni ya ngazi zote kwa mpangilio wa muda, na order=reverse_chronological kwa ya hivi karibuni kwanza, kisha jibu kama Ukurasa kwa kutuma ujumbe kwenye /{comment-id}/comments ya maoni hayo yenyewe. Token lazima itoke kwa mtu anayeweza kutekeleza MODERATE, vinginevyo Meta huacha vitambulisho vya maoni, na kujibu kunahitaji pages_manage_engagement. paging.next huelekeza nyuma zaidi.

Python: read a post's comments and reply to the questions
# graph() as in the first example
post_id = post["id"]  # {page-id}_{post-id}, as the publish call returned it
page = graph("GET", f"{post_id}/comments", fields="id,message,created_time,can_reply_privately",
             filter="stream", order="reverse_chronological", limit=50)
for comment in page["data"]:
    if "?" in comment.get("message", ""):
        graph("POST", f"{comment['id']}/comments",
              message="Thanks for asking! Our hours are on the Page.")
older = page.get("paging", {}).get("next")  # follow it to read further back

Unasomaje na kujibu maoni kwa Node.js?

Wito zile zile mbili, huku kitu cha URL kikijenga query string: GET yenye fields, filter na order, kisha POST kwa /{comment-id}/comments. can_reply_privately, iliyoombwa kwenye fields, inaonyesha kama Ukurasa bado unaweza kumtumia mtoa maoni jibu la faragha, jambo la kujua kabla ya mfano wa Messenger hapo chini. Hifadhi vitambulisho vya maoni unayojibu, ili kuendesha tena programu kusijibu mara mbili.

Node.js: read a post's comments and reply to the questions
// graph() as in the first example
const postId = post.id; // {page-id}_{post-id}, as the publish call returned it
const page = await graph("GET", `${postId}/comments`, {
  fields: "id,message,created_time,can_reply_privately",
  filter: "stream",
  order: "reverse_chronological",
  limit: 50,
});
for (const comment of page.data) {
  if ((comment.message ?? "").includes("?")) {
    await graph("POST", `${comment.id}/comments`, {
      message: "Thanks for asking! Our hours are on the Page.",
    });
  }
}
const older = page.paging?.next; // follow it to read further back

Unatumaje jibu la Messenger kwa Python?

POST /{page-id}/messages yenye recipient.id iliyowekwa kuwa kitambulisho cha mtu kilichowekwa kwa Ukurasa kutoka kwenye webhook ya messages, messaging_type RESPONSE na text. Mfano unakamata kukataliwa mbili ambazo hazistahili kujaribiwa tena: hitilafu 10 yenye subcode 2534022 au 2018278 dirisha la saa 24 linapokuwa limefungwa, na 551 mtu asipopatikana. private_reply() huweka recipient.comment_id mahali pa kitambulisho, kwa ujumbe mmoja ambao maoni huruhusu ndani ya siku 7.

Python: a Messenger reply and a private reply
# graph(), GraphError and PAGE_ID as in the first example
def reply(psid, text):
    """psid: sender.id from the messages webhook, within 24 hours of the person's message."""
    try:
        return graph("POST", f"{PAGE_ID}/messages", recipient={"id": psid},
                     messaging_type="RESPONSE", message={"text": text})
    except GraphError as e:
        if (e.code == 10 and e.subcode in (2534022, 2018278)) or e.code == 551:
            return None  # the window has closed, or the person is unavailable: no retry
        raise


def private_reply(comment_id, text):
    """One Messenger message to the person who commented, within 7 days of the comment."""
    return graph("POST", f"{PAGE_ID}/messages", recipient={"comment_id": comment_id},
                 message={"text": text})

Unatumaje jibu la Messenger kwa Node.js?

Mwili ule ule wa ombi kwa JavaScript, pamoja na recipient, messaging_type na message zilizotumwa kama JSON na graph(). Meta hujibu ombi lililokubaliwa kwa recipient_id na message_id, ambazo inafaa kuzihifadhi pamoja na mazungumzo. Jibu la faragha lina kiungo cha kurudi kwenye maoni linalojibu, na mazungumzo yanaendelea ndani ya dirisha la kawaida la saa 24 mara mtu huyo anapoandika tena.

Node.js: a Messenger reply and a private reply
// graph(), GraphError and PAGE_ID as in the first example
async function reply(psid, text) {
  // psid: sender.id from the messages webhook, within 24 hours of the person's message
  try {
    return await graph("POST", `${PAGE_ID}/messages`, {
      recipient: { id: psid },
      messaging_type: "RESPONSE",
      message: { text },
    });
  } catch (e) {
    const closed =
      e instanceof GraphError && ((e.code === 10 && [2534022, 2018278].includes(e.subcode)) || e.code === 551);
    if (closed) return null; // the window has closed, or the person is unavailable: no retry
    throw e;
  }
}

function privateReply(commentId, text) {
  // one Messenger message to the person who commented, within 7 days of the comment
  return graph("POST", `${PAGE_ID}/messages`, {
    recipient: { comment_id: commentId },
    message: { text },
  });
}

Unasomaje takwimu za Ukurasa kwa Python?

GET /{page-id}/insights yenye orodha ya vipimo vilivyotenganishwa kwa koma, period=day, na dirisha la since na until kwa sekunde za UNIX; ombi moja linafunika hadi siku 90. Vipimo vitatu kati ya hivi vilichukua nafasi ya vile ambavyo Meta iliviondoa: page_media_view kutoka page_impressions, page_total_media_view_unique kutoka page_impressions_unique na page_follows kutoka page_fans, wakati page_post_engagements inahesabu hisia, maoni na kushirikiwa.

Python: four Page metrics for the last 28 days
# graph() and PAGE_ID as in the first example
until = int(time.time())
since = until - 28 * 86400  # one request can cover up to 90 days
metrics = "page_media_view,page_total_media_view_unique,page_post_engagements,page_follows"
data = graph("GET", f"{PAGE_ID}/insights", metric=metrics, period="day", since=since, until=until)
for metric in data["data"]:
    for point in metric["values"]:
        print(metric["name"], point["end_time"][:10], point["value"])

Unasomaje takwimu za Ukurasa kwa Node.js?

Wito ule ule, huku since na until zikikokotolewa kutoka Date.now() kwa sekunde. Kila kipimo hurudi na jina lake, period yake na orodha ya values ya jozi za value na end_time, moja kwa kila siku; since ikiwekwa, end_time ya kwanza huangukia siku inayofuata, ili data ya siku hiyo ijumuishwe. Token inahitaji read_insights na pages_read_engagement, kutoka kwa mtu mwenye jukumu la ANALYZE.

Node.js: four Page metrics for the last 28 days
// graph() and PAGE_ID as in the first example
const until = Math.floor(Date.now() / 1000);
const since = until - 28 * 86400; // one request can cover up to 90 days
const data = await graph("GET", `${PAGE_ID}/insights`, {
  metric: "page_media_view,page_total_media_view_unique,page_post_engagements,page_follows",
  period: "day",
  since,
  until,
});
for (const metric of data.data) {
  for (const point of metric.values) {
    console.log(metric.name, point.end_time.slice(0, 10), point.value);
  }
}

Unathibitishaje sahihi ya webhook kwa Python?

Hesabu upya X-Hub-Signature-256 kutoka mwili ghafi wa ombi na app secret, kisha linganisha hizo mbili kwa muda usiobadilika. Meta hutia sahihi kila POST kwa HMAC-SHA256 ya payload, yenye ufunguo wa App Secret kutoka mipangilio ya msingi ya App Dashboard, na kuiandika baada ya sha256=. Pitisha mwili kama bytes, kabla ya uchanganuzi wowote wa JSON: request.body katika Django na await request.body() katika FastAPI zote zinatoa bytes ambazo Meta ilitia sahihi.

Python: check X-Hub-Signature-256
import hashlib, hmac, os

APP_SECRET = os.environ["APP_SECRET"].encode()  # App Dashboard, Settings, Basic


def signed_by_meta(raw_body: bytes, header: str) -> bool:
    """raw_body: the request body exactly as received. header: X-Hub-Signature-256."""
    expected = "sha256=" + hmac.new(APP_SECRET, raw_body, hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected.encode(), (header or "").encode())

# Django:  signed_by_meta(request.body, request.headers.get("X-Hub-Signature-256"))
# FastAPI: signed_by_meta(await request.body(), request.headers.get("X-Hub-Signature-256"))

Unathibitishaje sahihi ya webhook kwa Node.js?

Ukaguzi uleule kwa node:crypto, ambayo inahitaji mwili kama Buffer: kwenye Express, express.raw huuweka bila kuchanganuliwa kwenye njia hiyo. timingSafeEqual hutupa hitilafu kwa ingizo za urefu tofauti, kwa hiyo ukaguzi wa urefu unafanyika kwanza. Jibu 200 haraka na fanya kazi baadaye, kwani Meta hujaribu tena uwasilishaji ulioshindwa na inaweza kutuma tukio mara mbili; makala ya uthibitishaji inaeleza mkono wa hub.challenge unaokuja kabla ya tukio lolote.

Node.js: check X-Hub-Signature-256
import crypto from "node:crypto";

const APP_SECRET = process.env.APP_SECRET; // App Dashboard, Settings, Basic

function signedByMeta(rawBody, header = "") {
  // rawBody: a Buffer holding the request body exactly as received. header: X-Hub-Signature-256
  const digest = crypto.createHmac("sha256", APP_SECRET).update(rawBody).digest("hex");
  const expected = Buffer.from(`sha256=${digest}`);
  const given = Buffer.from(header);
  return given.length === expected.length && crypto.timingSafeEqual(given, expected);
}

// Express: app.post("/webhook", express.raw({ type: "application/json" }), (req, res) => {
//   if (!signedByMeta(req.body, req.get("X-Hub-Signature-256"))) return res.sendStatus(401);
//   res.sendStatus(200); // then work on JSON.parse(req.body) after answering
// });

Ni misimbo gani ya hitilafu ambayo msimbo unapaswa kuchukua hatua?

Ile ambayo miongozo ya hitilafu ya Meta inatofautisha, kwa sababu kila moja inahitaji jibu tofauti: kujaribu tena token iliyokataliwa au parameter mbaya hushindwa tena tu, wakati wito uliozuiliwa hufanikiwa baada ya kusubiri. graph() hujaribu tena misimbo ya muda na ya kikomo cha kasi, na hutupa nyingine ili mwitaji ashughulikie:

190, 102The token was refused, and the subcode says why. A new sign-in is the fix
10, 200 to 299A permission was not granted or was removed. Grant it again
4, 17, 32, 613An app, user or Page rate limit. Stop, wait, then resume gradually
80001Page calls made with a Page token are throttled; the header gives the minutes
368Blocked for policy violations. Wait, and review what was being sent
100An invalid parameter. Fix the request before sending it again
551The person is not available on Messenger. Do not retry
1, 2A temporary issue on Meta's side. Wait and retry

Unaendeshaje kazi hizo hizo kupitia easyCoexistence?

Kama zana za MCP ambazo Claude, ChatGPT au wakala wako mwenyewe huita kwenye Ukurasa uliounganishwa, huku token ikihifadhiwa na easyCoexistence. Token za Page hazitolewi kamwe, kwa hiyo mifano hapo juu inaendeshwa kwa token kutoka programu yako mwenyewe ya Meta; get_social_credentials hurudisha kitambulisho cha Page na msingi wa Graph API. Zana ya kila kazi:

Publishpublish_facebook_post with message, link, image_url or video_url, now or at scheduled_at
Commentslist_social_comments, then reply_to_comment; private set to true sends the one Messenger message
Messengersend_social_dm, with recipient_id set to the sender's ID from the forwarded event
Insightsget_social_insights with metrics and a period, or object_id for one post
Eventsset_social_webhook_destination; each forward carries X-EC-Signature, made with the Page's own secret

Makosa ya kawaida

  • Kuita endpoint za Ukurasa kwa token ya mtumiaji. Nyingi zinatarajia token ya Ukurasa wenyewe, na wito unaofanywa kwa token ya mtumiaji au ya programu huhesabiwa dhidi ya vikomo hivyo vya kasi badala ya vya Ukurasa.
  • Kuchapisha maandishi yale yale mara mbili mfululizo. Meta hukataa machapisho mawili yanayofanana mfululizo kwa hitilafu 506, kwa hiyo kazi inayoendeshwa tena lazima ibadilishe maudhui au iruke chapisho.
  • Kujumlisha watazamaji wa kila siku wa kipekee. page_total_media_view_unique huhesabu watazamaji wa kipekee katika kila kipindi, kwa hiyo thamani za kila siku hazijumlishi mwezi mzima; omba period days_28 badala yake.
  • Kupeleka token ya Ukurasa kwenye kivinjari au programu. Wito huu ni wa kuwekwa kwenye seva, ambako token inabaki mbali na mtu yeyote anayeweza kusoma mteja.
Kufanya hili ukitumia EasyCoexistence

Kuanzia US$ 9 hadi US$ 0.75 kwa kila muunganisho kwa mwezi, inashuka unapoongeza miunganisho, na siku 3 za kwanza ni bure.

Maswali yanayoulizwa mara kwa mara

Je, ninahitaji SDK kuita Facebook Pages API?

Hapana. Graph API ni HTTPS yenye JSON, kwa hiyo maombi kwa Python na fetch iliyojengwa ndani ya Node.js 18 au zaidi yanatosha, kama mifano kwenye makala hii inavyoonyesha.

Je, msimbo uleule unaweza kuchapisha kwenye Ukurasa kadhaa?

Ndiyo. /me/accounts hurudisha token tofauti kwa kila Ukurasa, kwa hiyo weka moja kwa kila Ukurasa na pitisha PAGE_ID na PAGE_TOKEN zinazolingana; wito unaofanywa kwa token ya Ukurasa huhesabiwa dhidi ya kikomo cha kasi cha Ukurasa huo wenyewe.

PSID ya jibu la Messenger inatoka wapi?

Kutoka kwenye webhook ya messages: sender.id katika kila tukio la messaging ni kitambulisho cha mtu kilichowekwa kwa Ukurasa, cha kipekee kwa mtu huyo na Ukurasa huo. Vitambulisho vya watumiaji kutoka Facebook Login vimewekwa kwa programu na haviwezi kutumika na Messenger Platform.

easyCoexistence inagharimu kiasi gani kwa Ukurasa wa Facebook?

Kila Ukurasa uliounganishwa unahesabiwa kama muunganisho mmoja, kwa US$ 9 hadi US$ 0.75 kwa kila muunganisho kwa mwezi kulingana na idadi uliyonayo, na siku 3 za kwanza ni bure; zana za MCP zinakuja nazo.

Endelea kusoma

Unganisha chaneli yako ya kwanza ndani ya dakika mbili.

Hakuna ukaguzi wa majukwaa wa kusubiri. Unganisha WhatsApp, Instagram, TikTok au chaneli nyingine, kisha mwombe AI wako achapishe, ajibu au atoe ripoti, na uone akifanya kazi.

  • Siku 3 bila malipo
  • Ghairi wakati wowote
  • API rasmi pekee
  • Hufuatiliwa saa 24/7

Imethibitishwa kwenye