JAVATEL Inc.株式会社ジャバテル
Home › Resource › SlimeTree-RLM › Meta › Graph API Generic Client

Public MIT

Meta Graph API Generic Client × SlimeTree-RLM Downstream Analysis

Debug multi-app operations from a single screen

Facebook / Instagram / Pages / Threads / WhatsApp — a Swiss Army Knife to hit any Graph API endpoint from one UI. Response text is processed downstream by SlimeTree-RLM as D / µ / R, with curl-equivalent display, Webhook verification, and history. For cross-app / cross-page debugging and operations.

1. Access token + API version

Save one arbitrary token (User Access Token / Page Access Token / System User Token / Threads Token) and reuse it. The token stays in localStorage only.

Not set

2. Common operation templates (click to apply)

GET /me Self / Page info
GET /me/accounts Your Pages list + Page Token
GET /me/permissions Granted scopes
GET /me/posts Your posts
GET /{page_id}/insights Insights
GET /me (Instagram) IG profile
GET /me/media IG media list
GET /me (Threads) Threads profile
GET /me/threads Threads posts list
POST /{page_id}/feed Page post
POST / (batch) Batch request
DELETE /{object_id} Delete object

3. Request builder

Query parameters

Body (POST only, JSON or form-urlencoded)

mode: form

4. Response / curl / RLM downstream

Final status: —
Elapsed: —
Response bytes: —
Send count: 0
curl equivalent command 
(nothing sent yet)
Response (JSON) 
(no response yet)
SlimeTree-RLM downstream analysis (text fields in the response)

Extracts text fields such as message / text / caption / biography from the response and classifies each as D / µ / R via the RLM. Useful for spam-comment detection, Insights anomaly checks, post-text audit, and similar use cases.

4.5 RLM analysis mode NEW: Pattern B (cross-vendor) — via the shared module

Switch the behavior when "Analyze response text with RLM" is pressed.

5. Webhook verification helper

A helper to verify the GET handshake during Meta Webhook registration (hub.mode=subscribe & hub.verify_token & hub.challenge). When you spin up a local server, generate a Verify Token and Challenge → see what body the server must return.

Response the server must return (including curl test) 
(Enter Verify Token + Challenge, then click "Generate Challenge")

6. History (most recent 10, localStorage)

(no history yet)

7. Why a Graph API generic client matters

  • Cross multiple Meta services with one token + UI: Facebook / Instagram / Pages / Threads / WhatsApp all share the Graph structure; only the host differs. Confirm API-level connectivity before firing up each specialized tool (Gateway / Threads bot, etc.)
  • Run routine ops instantly via templates: One-click for routines like "list my Pages + get Token", "single-line Insights", "Webhook verification", and more
  • RLM downstream analysis: Classify retrieved post text / comments / DMs as D = normal / µ = suppression-worthy / R = LLM-check recommended → useful for after-the-fact auditing of past statements and auto-marking spam comments
  • curl-equivalent display to port elsewhere: Confirm it works in the browser → copy-paste straight into cron / GitHub Actions / Lambda
  • History: "What was that request again?" — restored instantly via localStorage; shareable across developers (export feature can hand off JSON)
  • Webhook verification helper: When registering a new webhook, immediately visualizes "what the server must return" and reduces Meta-side registration mistakes

8. Source / Related