Messenger profile API: greeting, Get Started button, ice breakers and persistent menu
A Facebook Page's Messenger profile is set through /{page-id}/messenger_profile with a Page access token and pages_messaging: POST writes properties such as get_started, greeting, ice_breakers, persistent_menu and commands, GET reads them with fields, and DELETE removes the ones named in a fields array. Meta allows 10 calls per 10 minutes per Page, and only the properties sent are overwritten.
easyCoexistence replies to a Page's Messenger conversations with send_social_dm inside the 24-hour window, from Claude, ChatGPT or your own code, with new messages forwarded to your endpoint as they arrive.
Messenger Profile API calls allowed per Page in each 10-minute interval.
Most ice breakers the API sets; when both are set, API ice breakers take precedence over the Get Started button.
Most top-level items in a persistent menu; each item's title is limited to 30 characters.
How long a Page-level persistent menu update can take; a menu set for one person updates in real time.
Greeting text, which Meta's greeting reference says no longer works on Messenger for Android and iOS.
What does the Messenger profile hold?
The settings a Page's Messenger experience starts from. Meta's Messenger Profile API lists these properties, each set and read on the same endpoint; for an app in Development Mode, the settings are visible only to people with a role on the app:
How are properties read, set and deleted?
With three methods on one endpoint, called with the Page's token. POST takes a JSON body of properties and overwrites only those it names, GET takes fields as a comma-separated list, and DELETE takes a JSON body whose fields array names what to remove; POST and DELETE answer with result success. Setting a Get Started button and a menu in one call:
POST /{page-id}/messenger_profile
{
"get_started": { "payload": "GET_STARTED" },
"persistent_menu": [
{
"locale": "default",
"composer_input_disabled": false,
"call_to_actions": [
{ "type": "postback", "title": "Talk to an agent", "payload": "AGENT" },
{ "type": "web_url", "title": "Shop now", "url": "https://example.com/shop" }
]
}
]
}
{ "result": "success" }How does the Get Started button work?
It sits on the welcome screen, which shows the Page's name, profile picture and cover photo and how long the business usually takes to reply. A tap posts Get Started into the conversation, sends get_started.payload to the app as a messaging_postbacks event and opens the standard messaging window. Meta notes the button is not supported when Messenger runs in the Facebook app's in-app browser, and a persistent menu needs it set first.
Does the greeting text still work?
Not on phones. Meta's reference is now titled [Deprecated] Greeting Text: the feature no longer works on Messenger for Android and iOS, and while the API may still accept the greeting property, customers will not see it, so Meta asks developers to avoid it. As documented, greeting holds one text per locale, with default required, of up to 160 characters, personalized with {{user_first_name}}, {{user_last_name}} or {{user_full_name}}, and setting it takes the Administrator role on the Page.
How do ice breakers work?
They list up to 4 questions a person can tap to open a conversation; the question is posted in the thread as if the person asked it, and its payload comes back as a postback event. Since April 2022 they are localized: each object in ice_breakers holds call_to_actions and a locale, a default locale is required, and a DELETE of ice_breakers removes all of them. Meta ranks the elements that compete for a new conversation:
- API ice breakers take precedence over the Get Started button when both are set.
- Both come before custom questions set in the Page inbox, whose editing is disabled while API ice breakers are set.
How is the persistent menu built?
As an array of menus, one per locale with a default required, each holding up to 20 call_to_actions of type web_url or postback. A title takes up to 30 characters and a postback payload up to 1,000, and composer_input_disabled set to true leaves the menu, buttons and webviews as the only way to interact. Meta's requirements before it appears:
- A Get Started button already set, and the
pages_messagingpermission. - A published Page, and the app set to public.
- The Administrator role on the Page for whoever sets it.
- Messenger v106 or later on iOS or Android, outside the Facebook app's in-app browser.
- Page-level changes can take up to 24 hours; a menu for one person, set through
custom_user_settingswith a PSID, updates in real time.
What are commands?
Keywords a person can invoke at any time, from a commands menu next to the composer, by typing a slash or an at sign, or from a popover when they type a matching word. Each locale holds 1 to 100 commands, with a name of 1 to 32 characters and no leading slash and a description of 1 to 64; when commands are set, they take priority over the persistent menu. Invoked commands reach the app inside the messages event, in message.commands.
What do whitelisted_domains and account_linking_url do?
Both serve experiences outside the conversation itself. whitelisted_domains lists up to 50 domains the Messenger webview may open for the Messenger Extensions SDK and the checkbox plugin, each served over HTTPS under a fully qualified name, never an IP address or localhost, and setting it takes the Administrator role on the Page. account_linking_url is the HTTPS callback that links a person's Messenger account to their account with the business.
How does easyCoexistence set a Page's Messenger profile?
It does not: no tool calls {page-id}/messenger_profile, and Page tokens are not handed out, so setting the profile is outside this connection. Commands people invoke arrive in the messages event that easyCoexistence forwards and automations read; taps that Meta reports as messaging_postbacks events, from Get Started, postback menu items and ice breakers, are not forwarded, since Pages are subscribed to feed, messages and mention.
Common mistakes
- Setting a persistent menu before Get Started. Meta's requirements include a Get Started button, so set get_started first.
- Leaving out the default locale. Ice breakers, menus and commands each need an object with locale set to default as the fallback.
- Calling the profile API in a loop. Meta allows 10 calls per 10 minutes per Page, so put several properties in one POST.
- Expecting a menu change at once. A Page-level menu update can take up to 24 hours to reach people.
Setting the Messenger profile is not among its tools. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Can a persistent menu differ per person?
Yes. custom_user_settings with the person's PSID overrides the Page's menu for that person, updates in real time and allows 10 calls per person in 10 minutes.
Which locales does the Messenger profile support?
Those on Meta's supported locales list, such as en_GB, pt_BR or ja_JP, plus default, the fallback used when no locale matches the person's.
Who can change a Page's Messenger profile?
An app with a Page token carrying pages_messaging. The persistent menu, the greeting and the domain list also need the Administrator role on the Page.
How much does easyCoexistence cost for a Facebook Page?
Each Page is one connection: US$ 9 to US$ 0.75 per connection per month, the price falling as your number of connections grows, and the first 3 days are free.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on