Chapisha kwenye Instagram, TikTok na Facebook kutoka Node.js kwa API moja
Ukitumia easyCoexistence, backend yako ya Node.js au TypeScript huchapisha kwenye Instagram, Facebook, TikTok, YouTube na LinkedIn kupitia API rasmi ya kila mtandao. Akaunti huingia mara moja kupitia kiungo kilichowekwa mtandaoni; ombi moja la fetch kisha hurudisha token mpya kwa kila kazi kwenye TikTok, YouTube na LinkedIn, na matukio yaliyosainiwa huleta maoni na DM kwenye njia yako. Mawakala waliojengwa kwa TypeScript MCP SDK hupata akaunti hizo hizo kama zana.
Video ambazo endpoint ya kuchapisha ya TikTok inakubali kwa kila akaunti, zisizozidi sita kwa dakika.
Muda ambao chapisho la ukurasa wa Facebook linaweza kupangwa mbele kwa published false na scheduled_publish_time.
Kichwa cha jibu kinachobeba URN ya chapisho jipya la LinkedIn, kinachotumwa na hali 201.
Muda ambao TikTok huwasha tukio la comment.update baada ya maoni kuundwa, kufutwa au kubadilishwa mwonekano wake.
Muda ambao kiungo cha kuunganisha cha Partner API kinabaki wazi kabla kipindi hakijaisha.
Backend ya Node.js huunganisha akaunti na kupata token zao vipi?
Backend yako hufungua kipindi cha kuunganisha na mmiliki wa akaunti anamaliza kwenye kivinjari. POST kwenda /connect-sessions, ukiwa na ec_live_ key yako kama bearer token, chaneli kama tiktok au linkedin, redirect_url na external_ref ya mteja wako, hurudisha url kwenye easycoexistence.com. Hapo mmiliki huingia kupitia skrini ya idhini ya mtandao husika na kurudi kwenye redirect_url yako na status=connected na channel_id. Jaribio lililoghairiwa linaweza kujaribiwa tena kutoka kiungo kile kile hadi lisipoisha muda, saa moja baada ya kuundwa.
Kila kazi kisha huanza na GET /channels/{id}?credentials=1. Jibu lina token halali sasa hivi (si kwenye Instagram na Facebook, ambazo token zake hazitolewi kamwe) pamoja na sehemu ambazo kila mtandao unahitaji: graph_api_base na account_id_on_meta kwa Instagram na Facebook, api_base na business_id kwa TikTok, channel_id kwa YouTube, author_urn na required_headers kwa LinkedIn. Matukio yaliyosainiwa channel.connected, channel.disconnected, channel.removed na channel.suspended, yanayotumwa kwenye URL ya matukio uliyoweka kwenye dashboard yako, humwambia programu yako akaunti inapobadilika.
const EC = "https://easycoexistence.com/api/v1";
const KEY = { Authorization: `Bearer ${process.env.EC_API_KEY}` }; // ec_live_...
type Network = "instagram" | "facebook" | "tiktok" | "youtube" | "linkedin";
// A hosted sign-in link for one of your customers on one network
export async function connectLink(customerId: string, channel: Network): Promise<string> {
const r = await fetch(`${EC}/connect-sessions`, {
method: "POST",
headers: { ...KEY, "Content-Type": "application/json" },
body: JSON.stringify({
channel,
redirect_url: "https://app.example.com/connected",
external_ref: customerId,
}),
});
const session = (await r.json()) as { url: string; error?: { message: string } };
if (!r.ok) throw new Error(session.error?.message);
return session.url; // they come back with ?session=...&status=connected&channel_id=...
}
// At the start of every job: the API base and a token that is valid now
export async function credentials(channelId: string) {
const r = await fetch(`${EC}/channels/${channelId}?credentials=1`, { headers: KEY });
const body: any = await r.json(); // the credential fields differ by network
if (!r.ok) throw new Error(body.error.message);
if (!body.credentials.access_token) throw new Error(body.credentials.note);
return body.credentials;
}Unachapishaje kwenye Instagram na Facebook kutoka Node.js?
Instagram huchapisha kupitia container. Kwa Reel, iunde kwa media_type REELS, video_url na caption, kisha kagua status_code hadi isome FINISHED, kisha piga media_publish ukiwa na id ya container kama creation_id. Meta inapendekeza kukagua takriban kila dakika moja na kuacha baada ya dakika tano. ERROR au EXPIRED maana yake container haitachapishwa, na ile isiyochapishwa kwa saa 24 huisha yenyewe.
Ukurasa wa Facebook huchukua picha kwa wito mmoja kwenda /{page-id}/photos, pamoja na url ya picha na caption, huku maandishi na viungo vikienda kwenye /{page-id}/feed. Zote mbili zinakubali published false na scheduled_publish_time, na Meta yenyewe huchapisha chapisho wakati ukifika, kati ya dakika 10 na siku 30 mbele. Token husafiri kama bearer header, toleo la Graph API tayari lipo ndani ya graph_api_base, na media lazima ipatikane kwenye URL ya umma ambayo Meta huipakua.
type Meta = { graph_api_base: string; access_token: string };
async function graph(c: Meta, path: string, body?: object) {
const r = await fetch(`${c.graph_api_base}/${path}`, {
method: body ? "POST" : "GET",
headers: { Authorization: `Bearer ${c.access_token}`, "Content-Type": "application/json" },
body: body && JSON.stringify(body),
});
const data: any = await r.json();
if (!r.ok) throw new Error(data.error?.message ?? `Graph API ${r.status}`);
return data;
}
export async function postReel(channelId: string, videoUrl: string, caption: string) {
const c = await credentials(channelId);
const ig = c.account_id_on_meta;
const { id } = await graph(c, `${ig}/media`, { media_type: "REELS", video_url: videoUrl, caption });
for (let check = 0; check < 5; check++) {
await new Promise((wake) => setTimeout(wake, 60_000)); // about once a minute, as Meta advises
const { status_code } = await graph(c, `${id}?fields=status_code`);
if (status_code === "FINISHED") return graph(c, `${ig}/media_publish`, { creation_id: id });
if (status_code === "ERROR" || status_code === "EXPIRED") throw new Error(`Reel container ${status_code}`);
}
throw new Error("The Reel is still processing after five minutes");
}
export async function schedulePagePhoto(channelId: string, url: string, caption: string, at: Date) {
const c = await credentials(channelId);
return graph(c, `${c.account_id_on_meta}/photos`, {
url,
caption,
published: false,
scheduled_publish_time: Math.floor(at.getTime() / 1000), // 10 minutes to 30 days ahead
});
}Unachapishaje kwenye LinkedIn na kupakia kwenye YouTube kutoka Node.js?
LinkedIn inataka header mbili za ziada pamoja na bearer token katika kila wito: LinkedIn-Version, yenye thamani ya YYYYMM ambayo easyCoexistence hurudisha katika required_headers, na X-Restli-Protocol-Version iliyowekwa 2.0.0. Chapisho ni POST kwenda /rest/posts ukiwa na author URN, maandishi kama commentary, visibility PUBLIC, mkondo mkuu wa feed kama distribution na lifecycleState PUBLISHED. LinkedIn hujibu 201 na kuweka URN ya chapisho jipya kwenye header ya x-restli-id, na URN yoyote iliyowekwa kwenye path ya URL lazima iwe URL-encoded.
YouTube inachukua maombi mawili. POST kwenda kwenye upload endpoint yenye uploadType=resumable na part=snippet,status hutuma metadata na kurudisha anwani ya kikao kwenye header ya Location. PUT ya baiti za faili kwenda anwani hiyo hurudisha video resource pamoja na id yake. Kupakia kama private pamoja na tarehe ya publishAt huacha uchapishaji kwa ratiba ya YouTube yenyewe, kwa hiyo hakuna kitu chako kinachohitaji kufanya kazi saa hiyo.
import { readFile } from "node:fs/promises";
export async function postOnLinkedIn(channelId: string, text: string) {
const c = await credentials(channelId);
const r = await fetch(`${c.api_base}/posts`, {
method: "POST",
headers: {
Authorization: `Bearer ${c.access_token}`,
"LinkedIn-Version": c.required_headers["LinkedIn-Version"],
"X-Restli-Protocol-Version": "2.0.0",
"Content-Type": "application/json",
},
body: JSON.stringify({
author: c.author_urn, // urn:li:organization:... or urn:li:person:...
commentary: text,
visibility: "PUBLIC",
distribution: { feedDistribution: "MAIN_FEED", targetEntities: [], thirdPartyDistributionChannels: [] },
lifecycleState: "PUBLISHED",
isReshareDisabledByAuthor: false,
}),
});
if (r.status !== 201) throw new Error(`LinkedIn ${r.status}: ${await r.text()}`);
return r.headers.get("x-restli-id"); // the new post's URN
}
export async function scheduleOnYouTube(channelId: string, file: string, title: string, publishAt: string) {
const c = await credentials(channelId);
const auth = { Authorization: `Bearer ${c.access_token}` };
const start = await fetch(
"https://www.googleapis.com/upload/youtube/v3/videos?uploadType=resumable&part=snippet,status",
{
method: "POST",
headers: { ...auth, "Content-Type": "application/json; charset=UTF-8", "X-Upload-Content-Type": "video/mp4" },
body: JSON.stringify({
snippet: { title },
status: { privacyStatus: "private", publishAt, selfDeclaredMadeForKids: false },
}),
},
);
const session = start.headers.get("location");
if (!start.ok || !session) throw new Error(`YouTube ${start.status}: ${await start.text()}`);
const done = await fetch(session, {
method: "PUT",
headers: { ...auth, "Content-Type": "video/mp4" },
body: await readFile(file),
});
const video = (await done.json()) as { id: string };
return video.id;
}Unapokeaje maoni na DM kwenye route ya Node.js?
Kila chaneli hutuma kwenye URL uliyotoa PUT /channels/{id}/webhook, na wito huo hurudisha signing_secret ya chaneli mara moja tu. Kila utoaji ni POST yenye platform, account_id, external_id na entry, pamoja na header ya X-EC-Signature yenye umbo t=<unix>,v1=<hex>, ambapo v1 ni HMAC-SHA256 ya t, nukta na body ghafi. Chukua body kama maandishi kabla ya kuichambua, kataa t ya zaidi ya dakika tano, kisha linganisha kwa timingSafeEqual.
Kwa Instagram na Facebook, entry ni entry ya webhook ya Meta kama Meta ilivyoituma: changes kwa maoni na mentions, messaging kwa DM. Kwa TikTok ina tukio la comment.update, ambalo TikTok huliwasha ndani ya dakika tano baada ya maoni, pamoja na comment_id na video_id kama strings ili JavaScript isizungushe nambari hizo za 64-bit. Kuna jaribio moja tu kwa kila tukio na hakuna nakala iliyohifadhiwa, kwa hiyo jibu 204 mara moja na uchakate kutoka kwenye foleni.
import { createHmac, timingSafeEqual } from "node:crypto";
const secrets = new Map<string, string>(); // channel id -> signing_secret, kept in your database
export async function forwardEvents(channelId: string, url: string) {
const r = await fetch(`${EC}/channels/${channelId}/webhook`, {
method: "PUT",
headers: { ...KEY, "Content-Type": "application/json" },
body: JSON.stringify({ url }),
});
const body = (await r.json()) as { signing_secret: string; error?: { message: string } };
if (!r.ok) throw new Error(body.error?.message);
secrets.set(channelId, body.signing_secret); // returned only this once
}
function verify(raw: string, header: string | null, secret: string): boolean {
const parts = Object.fromEntries((header ?? "").split(",").map((kv) => kv.split("=", 2)));
const t: string = parts.t ?? "";
const v1: string = parts.v1 ?? "";
if (!/^[0-9]+$/.test(t) || Math.abs(Date.now() / 1000 - Number(t)) > 300) return false;
const mac = createHmac("sha256", secret).update(`${t}.${raw}`).digest("hex");
return mac.length === v1.length && timingSafeEqual(Buffer.from(mac), Buffer.from(v1));
}
// POST /hooks/social as a web-standard handler (Next.js, Hono, Bun and others)
export async function POST(req: Request) {
const raw = await req.text(); // the signature covers these exact bytes
const event = JSON.parse(raw); // { platform, account_id, external_id, entry }
const secret = secrets.get(event.account_id);
if (!secret || !verify(raw, req.headers.get("x-ec-signature"), secret)) {
return new Response("invalid signature", { status: 401 });
}
await enqueue(event); // one attempt per event and no retries: acknowledge first
return new Response(null, { status: 204 });
}Unajibuje maoni na DM kutoka Node.js?
Kwa wito mpya wa credentials na ids zilizo kwenye tukio. Kwenye Instagram na Facebook, jibu la DM huenda kwenda /{account-id}/messages, kwa kutumia account_id_on_meta, pamoja na sender id kama recipient, ndani ya saa 24 tangu ujumbe wao wa mwisho. Page huongeza messaging_type RESPONSE, na Instagram inaruhusu baiti 1,000 za maandishi kwa kiwango cha juu. Maoni hupata jibu la umma, kwenye /{comment-id}/replies kwa Instagram au /{comment-id}/comments kwa Facebook, au jibu moja la faragha ndani ya siku 7.
Mazungumzo ya TikTok yanabaki ya umma, kwa sababu TikTok haina DM. business/comment/reply/create/, pamoja na header ya Access-Token, business_id, video_id na comment_id, huchapisha jibu lenye hadi herufi 1,200. Soma sehemu ya code ya jibu, ambapo 0 maana yake imefanikiwa, badala ya HTTP status. Chukua hatua tu kwa comment_action insert yenye comment_type comment, kwa sababu majibu yako mwenyewe nayo hufika kama matukio.
export async function reply(event: any, text: string) {
const c = await credentials(event.account_id);
if (event.platform === "tiktok") {
const e = event.entry.content; // the comment.update event, ids as strings
if (e.comment_action !== "insert" || e.comment_type !== "comment") return; // your replies arrive as "reply"
const r = await fetch(`${c.api_base}/business/comment/reply/create/`, {
method: "POST",
headers: { "Access-Token": c.access_token, "Content-Type": "application/json" },
body: JSON.stringify({ business_id: c.business_id, video_id: e.video_id, comment_id: e.comment_id, text }),
});
const out = (await r.json()) as { code: number; message: string };
if (out.code !== 0) throw new Error(out.message); // 0 is success, whatever the HTTP status
} else if (event.platform === "facebook") {
for (const m of event.entry.messaging ?? []) {
if (!m.message || m.message.is_echo) continue; // only what people sent the Page
await graph(c, `${c.account_id_on_meta}/messages`, {
recipient: { id: m.sender.id },
messaging_type: "RESPONSE", // within 24 hours of their last message
message: { text },
});
}
}
}Unachapishaje kwenye TikTok na kumpa wakala wa TypeScript zana hizi?
Yote mawili hupitia seva ya MCP ya easyCoexistence kwenye https://easycoexistence.com/api/mcp, ambayo inakubali OAuth 2.1 pekee: usajili wa client wenye nguvu, authorization code na PKCE, access tokens zinazodumu saa moja na refresh tokens. Kwa @modelcontextprotocol/client, SDK rasmi ya TypeScript kwa toleo la 20 la Node na kuendelea, OAuthClientProvider hushikilia client, tokens na PKCE verifier. Muunganisho wa kwanza humpeleka mtumiaji kuingia na kutupa UnauthorizedError, na finishAuth pamoja na query ya callback huukamilisha.
Uchapishaji wa TikTok uko hapa kwa sababu TikTok hupakua media kutoka kwenye viambishi vya URL vilivyothibitishwa kwa programu ya msanidi nyuma ya token. publish_tiktok_post huchukua kiungo chako cha HTTPS na kumpa TikTok anwani iliyosainiwa kwenye njia ya media iliyothibitishwa ya easyCoexistence, na get_tiktok_publish_status hufuatilia chapisho. Client huyo huyo humpa wakala kila zana ya mitandao ya akaunti. Itisha list_social_accounts kwanza, ambayo account_id yake ni channel_id ya Partner API.
import { createInterface } from "node:readline/promises";
import { Client, StreamableHTTPClientTransport, UnauthorizedError, type OAuthClientProvider } from "@modelcontextprotocol/client";
const MCP = new URL("https://easycoexistence.com/api/mcp");
const saved: Record<string, any> = {}; // persist this, so the browser sign-in happens once
const provider: OAuthClientProvider = {
redirectUrl: "http://localhost:8090/callback",
clientMetadata: { client_name: "My social agent", redirect_uris: ["http://localhost:8090/callback"] },
state: () => (saved.state = crypto.randomUUID()),
clientInformation: () => saved.client,
saveClientInformation: (info) => { saved.client = info; },
tokens: () => saved.tokens,
saveTokens: (tokens) => { saved.tokens = tokens; },
saveCodeVerifier: (verifier) => { saved.verifier = verifier; },
codeVerifier: () => saved.verifier,
redirectToAuthorization: (url) => console.log("Sign in to easyCoexistence:", url.href),
};
const client = new Client({ name: "my-social-agent", version: "1.0.0" });
const transport = new StreamableHTTPClientTransport(MCP, { authProvider: provider });
try {
await client.connect(transport);
} catch (error) {
if (!(error instanceof UnauthorizedError)) throw error;
const rl = createInterface({ input: process.stdin, output: process.stdout });
const back = new URL(await rl.question("Paste the address you were sent back to: ")).searchParams;
rl.close();
if (back.get("state") !== saved.state) throw new Error("state mismatch");
await transport.finishAuth(back);
await client.connect(new StreamableHTTPClientTransport(MCP, { authProvider: provider }));
}
const result = await client.callTool({
name: "publish_tiktok_post",
arguments: {
account_id: process.env.TIKTOK_CHANNEL_ID, // the Partner API channel id
video_url: "https://cdn.example.com/launch.mp4",
caption: "New drop #behindthescenes",
},
});
console.log(result.content); // a share_id to follow with get_tiktok_publish_statusMakosa ya kawaida
- Kukokotoa HMAC juu ya JSON iliyochambuliwa na kuandikwa upya. Sahihi inafunika body ghafi baiti kwa baiti, kwa hiyo piga req.text() kwanza na uchambue baadaye, vinginevyo kila utoaji utashindwa ukaguzi.
- Kubadilisha ids za TikTok kuwa nambari. Ids za maoni na video ni 64-bit na Number() huzizungusha, kwa hiyo weka strings ambazo tukio hubeba unapojibu au kutafuta maoni.
- Kuhifadhi channel_id pekee kutoka kwenye redirect. Kuingia kwa Facebook au LinkedIn kunaweza kuongeza Page kadhaa mara moja, kwa hiyo orodhesha kwa GET /channels?external_ref= na uhifadhi kila moja.
- Kujibu DM ya Messenger au Instagram kutoka kwenye batch ya usiku. Nje ya saa 24 tangu ujumbe wa mwisho wa mtu, utumaji unashindwa, kwa hiyo jibu kutoka kwenye kidhibiti cha tukio dirisha likiwa wazi.
easyCoexistence huwapa backend za Node.js na mawakala wa AI ufikiaji wa wateja kwenye WhatsApp, Instagram, Facebook, TikTok, YouTube, LinkedIn na chaneli nyingine zinazoongezwa, kila moja kupitia API yake rasmi. Unganisha akaunti kwa Partner API, pata token mpya na matukio yaliyosainiwa, na acha mawakala wa TypeScript wachukue hatua kupitia seva ya MCP, huku kila muunganisho ukifuatiliwa saa 24. US$ 9 hadi US$ 0.75 kwa muunganisho kwa mwezi, inashuka kadri unavyoongeza muunganisho, na siku 3 za kwanza bila malipo.
Maswali yanayoulizwa mara kwa mara
Je, ninahitaji SDK kuita API hizi kutoka Node?
Hapana. Partner API na API za mitandao ni HTTPS ya kawaida, kwa hiyo fetch ya kimataifa katika Node 18 na kuendelea inatosha. @modelcontextprotocol/client huja tu kwa zana za MCP, zikiwemo uchapishaji wa TikTok.
Kwa nini uchapishaji wa TikTok unapitia seva ya MCP?
TikTok hupakua video na picha kutoka kwenye domain au URL prefix iliyothibitishwa kwa programu ya msanidi, na programu hiyo ni ya easyCoexistence. publish_tiktok_post hutoa faili lako la HTTPS kutoka anwani hiyo iliyothibitishwa, kwa hiyo domain yako mwenyewe haihitaji uthibitishaji.
Je, kuingia mara moja kunaweza kuunganisha Page kadhaa za Facebook au LinkedIn?
Ndiyo. Kila Page, na kwenye LinkedIn wasifu wa mwanachama mwenyewe, huwa chaneli yake na muunganisho wake. Redirect hubeba channel_id ya kwanza, na GET /channels?external_ref= huorodhesha zote.
easyCoexistence inagharimu kiasi gani kwa Node.js?
US$ 9 hadi US$ 0.75 kwa muunganisho kwa mwezi, inashuka kadri unavyoongeza muunganisho, na bei ni ile ile kwenye kila mtandao. Partner API na kiunganishi cha MCP vinakuja pamoja nayo, bila viti, na siku 3 za kwanza ni bila malipo.
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