Ana içeriğe geç

Why a connected Messenger / Instagram channel might be silent

GET 
/api/channels/:channel/meta/connection-check

A Meta social channel can connect successfully, report healthy and receive nothing at all. There is no error, because from the API's side nothing failed: what is switched off is a setting in the tenant's own Instagram app or Facebook Page Setup that we can neither read nor write.

This endpoint reports ONLY what Meta actually answered. The four settings behind most of these outages have no API at all, so they are absent from the response and named by the panel instead, with the place they live — a row claiming "Connected Tools looks fine" from a successful token read would be worse than no row.

unknown is a first-class verdict and the reason the screen is worth trusting. "We could not ask" and "we asked and it is fine" look identical as a green tick and send the reader somewhere else entirely. feature_status is ALWAYS unknown: Meta documents the call and its sample answer and never says what hop_v2, msgr_multi_app or ig_multi_app mean, so the booleans are handed over verbatim for a person to compare against the switches themselves.

READ-ONLY: it asks Meta and repairs nothing, so it can be run twice to see whether a fix worked. Its single side effect is a happy accident — the Conversations listing it makes is also the call Meta requires before a CREATOR account will receive webhooks, so on the account type most likely to need this check, running it is also the fix.

Request​

Responses​

One row per readable check.