
Personal accounts
Facebook Messenger API Personal Account Access: What Meta Allows and How to Connect One
Looking for a Facebook Messenger API personal account option? Meta's Messenger Platform only serves Facebook Pages. Here is why, and how your users can connect their own account to your app.
Tom Reyes
Anna Lee, personal account
Hi Anna, can we move our call to Thursday?09:12
Webhook: message.new
Sure, Thursday 10am works. I'll send the invite.09:14 · Seen
POST
api.unipile.com/v2/{ACCOUNT_ID}/chats/{CHAT_ID}/messages/send
200 OK
Table of Contents
Short answer
The official Facebook Messenger API does not support personal accounts. Meta's Messenger Platform lets a Facebook Page or an Instagram professional account reply to people, never a personal profile. To work with a personal Facebook account, the account owner connects it to your app through a third party API such as Unipile.
Open source projects that drive messenger.com from a browser are unofficial, mostly unmaintained and break whenever the interface changes. A connected account goes through a maintained API with webhooks.
For the wider picture of Meta's APIs, see how the Facebook APIs fit together.
With Unipile
Messages from a personal Facebook account in three steps
- 1
Connect. Your user links their own Facebook account through Hosted Auth. No Meta app, no App Review.
- 2
Send. Call the V2 API with your
X-API-KEYheader:POST/v2/{ACCOUNT_ID}/ chats/ {CHAT_ID}/ messages/ send - 3
Receive. Incoming messages reach your webhook as
message.newevents.
Details in the connection flow and code samples below, or the Facebook quickstart.
Start your 7-day free trial
The answer
Does the Facebook Messenger API Work with a Personal Account?
Not the official one. Meta built the Messenger Platform for businesses: it lets a Facebook Page or an Instagram professional account answer the people who write to it. A personal Facebook account can only reach your app when its owner connects it, through a third party API that acts on their behalf.
Meta's Messenger Platform
Facebook Page
- Your Meta app acts for a Page with a Page access token.
- The Page answers people who message it first.
- Standard messaging window of 24 hours after the person's last message.
- App Review before serving Pages you do not own.
Connected account with Unipile
Personal Facebook account
- Each user links their own account through hosted authentication.
- Your app reads and sends messages from that account.
- One REST API and one webhook format for every channel.
- The user stays bound by Meta's Terms.
Source: Meta's Messenger Platform overview. Last verified: November 2026.
Official model
Why Meta's Messenger Platform Stops at Facebook Pages
The Messenger Platform is designed around a Page, not a person. Every call acts on behalf of a Facebook Page, with a Page access token and the pages_messaging permission, so there is no token that represents a personal inbox.
1
Meta app
You register an app on Meta for Developers with the Messenger use case.
2
Facebook Login for Business
A Page admin grants permissions such as pages_messaging.
3
Page access token
Your app calls the Send API on behalf of that Page only.
4
Webhook and 24 hour window
The Page receives messages and replies within the standard messaging window.
Permissions are requested through Facebook Login for Business, and business_management is a dependency of pages_messaging. App Review is not required if you only send and receive messages for your own Page; serving other businesses' Pages needs it. Most replies must be sent within 24 hours of the person's last message; the HUMAN_AGENT message tag extends manual replies to 7 days, after App Review. None of these Graph API steps can target a personal profile, which is why tools built on the official API connect Pages only. What this setup costs is detailed in our guide to Facebook Messenger API pricing.
Sources: Meta's Messenger Platform overview and Send API reference. Last verified: November 2026.
What Happened to the Facebook Chat API?
Meta shut down the old Facebook Chat API (XMPP, chat.facebook.com) in 2015, with the end of Graph API v1.0 and the xmpp_login permission. There is no official API for a personal Facebook inbox: the Messenger Platform that replaced it for business messaging only acts for Pages. The unofficial libraries published on npm since then sign in to messenger.com with the user's own session. They are not supported by Meta, and the original open source project says it is in maintenance mode.
- No release schedule. They stop working when Facebook changes its interface.
- Credentials in your app. Your app stores and reuses the user's session or password.
- Account risk. Facebook can restrict an account whose use breaks its Terms, and that risk falls on the end user.
To message from a Page you manage, use the Messenger Platform and send a Messenger message via API. For the user's own account, use a maintained API: the user connects through Hosted Auth, so your app never handles their password, and you get an account_id, webhooks and a support team (see how a personal account connects). Meta's Terms still apply to that account.
Connection
How a Personal Facebook Account Connects to Your App
The account owner connects it themselves. Your app opens a Unipile Hosted Auth page (or your own screen with Custom Auth), the user signs in to Facebook and validates two factor authentication, and your app receives an account_id to call the API with.
1Your app
Open Hosted Auth
The user clicks "Connect Facebook" and lands on Hosted Auth.
2The user
Sign in and confirm
Username, email or phone with password, browser cookies or the UniLogin extension, then 2FA by SMS, authenticator app, WhatsApp, in-app approval or one time code.
3Unipile
Get an account_id
The connected account appears in your dashboard and every call uses its account_id.
There is no Meta OAuth screen and no QR code in this flow, and you do not create a Meta app or go through App Review on your side. Methods per provider are listed in the provider features table, and the product overview lives on the Facebook Messenger API page.
Compliance
Each user connects their own account
Unipile is not a Meta product. It is not a Meta Partner and is not endorsed by Meta. Each user connects their own account, Unipile acts on behalf of that authenticated user, and the user remains bound by Meta's Terms.
Scope
Facebook Personal Account API: What a Connected Account Can Do
In practice, a Facebook Messenger API personal account integration exposes the user's own Messenger inbox through the Unipile API: chats, messages, attachments, reactions and receipts, plus real time webhooks, compared below with the official Page model.
| Topic | Page via Messenger Platform | Personal account via Unipile |
|---|---|---|
| Account | A Facebook Page or Instagram professional account | The user's own personal Facebook account |
| Who connects | A Page admin, through Facebook Login for Business | The account owner, through Hosted Auth or Custom Auth |
| What your app holds | A Page access token | Your Unipile API key and the user's account_id |
| Meta app and App Review | A Meta app, plus App Review to serve Pages you do not own | No Meta app and no App Review on your side |
| Who writes first | The person messages the Page | The user can reply or start a new conversation |
| Real time events | Messenger webhooks on your Meta app | New, edited and deleted messages, read and delivery receipts, reactions, chat updates |
Account
PageA Facebook Page or Instagram professional account
Personal accountThe user's own personal Facebook account
Who connects
PageA Page admin, through Facebook Login for Business
Personal accountThe account owner, through Hosted Auth or Custom Auth
What your app holds
PageA Page access token
Personal accountYour Unipile API key and the user's
account_idMeta app and App Review
PageA Meta app, plus App Review to serve Pages you do not own
Personal accountNo Meta app and no App Review on your side
Who writes first
PageThe person messages the Page
Personal accountThe user can reply or start a new conversation
Real time events
PageMessenger webhooks on your Meta app
Personal accountNew, edited and deleted messages, read and delivery receipts, reactions, chat updates
Messaging endpoints
- List chats and messages, including group conversations
- Start a conversation, send messages and attachments
- Edit, delete and forward messages
- Add and remove reactions, mark as read, read receipts
- Mute and archive chats
Not supported
- Pinning a message
- Stories
The same connected account also exposes its posts, comments and reactions. Those endpoints are summarized in the Facebook API guide.
Code
Read Chats and Send a Message from a Personal Account
Two calls cover the basic loop: list the chats of the connected account, then send a message in one of them. Requests go to https://api.unipile.com with your API key in the X-API-KEY header.
# 1. List the chats of the connected personal account
curl --request GET \
--url "https://api.unipile.com/v2/{ACCOUNT_ID}/chats" \
--header "X-API-KEY: {YOUR_API_KEY}"
# 2. Send a message in one of those chats
curl --request POST \
--url "https://api.unipile.com/v2/{ACCOUNT_ID}/chats/{CHAT_ID}/messages/send" \
--header "X-API-KEY: {YOUR_API_KEY}" \
--header "content-type: application/json" \
--data '{ "text": "Thursday 10am works for me." }'
const base = "https://api.unipile.com/v2/{ACCOUNT_ID}";
const headers = { "X-API-KEY": process.env.UNIPILE_API_KEY };
// 1. List the chats of the connected personal account
const chats = await (await fetch(`${base}/chats`, { headers })).json();
// 2. Send a message in one of those chats
await fetch(`${base}/chats/{CHAT_ID}/messages/send`, {
method: "POST",
headers: { ...headers, "content-type": "application/json" },
body: JSON.stringify({ text: "Thursday 10am works for me." }),
});
import os, requests
base = "https://api.unipile.com/v2/{ACCOUNT_ID}"
headers = {"X-API-KEY": os.environ["UNIPILE_API_KEY"]}
# 1. List the chats of the connected personal account
chats = requests.get(f"{base}/chats", headers=headers).json()
# 2. Send a message in one of those chats
requests.post(
f"{base}/chats/{{CHAT_ID}}/messages/send",
headers=headers,
json={"text": "Thursday 10am works for me."},
)
200 OK · message sent from the user's own account
Incoming messages arrive on your webhook as message.new events, so you do not need to poll. The Node.js SDK wraps the same calls as getChatsList and sendMessage. Full setup in the Facebook quickstart. More languages, attachments and Page replies in Facebook Messenger API send message.
What the Two Calls Look Like in Your App
1List the chatsGET/chats
Tom ReyesHi Anna, can we move our call to Thursday?
Maya ChenSee you at the market on Saturday
Sam PatelThanks for the photos
Selected chat
- chat_id
- {CHAT_ID}
- name
- Tom Reyes
- last message
- Hi Anna, can we move…
- timestamp
- 09:12
2Send the replyPOST/messages/send
Tom Reyes
Anna Lee, personal account
Hi Anna, can we move our call to Thursday?09:12
Thursday 10am works for me.09:14 · Seen
Request
- chat_id
- {CHAT_ID}
- text
- Thursday 10am works…
- response
- 200 OK
Use cases
Legitimate Use Cases, and Meta's Rules Your Users Still Follow
A connected personal account fits products where a professional talks with their own contacts from their own account: CRMs, helpdesks, AI assistants that draft replies the user approves, and advisor tools. It is not built for cold outreach or fully automated bots.
CRM
A salesperson finds their Messenger conversations on the right contact record, next to emails and calls. See the CRM integration.
Helpdesk and multichannel inbox
Messenger sits in the same inbox as LinkedIn, WhatsApp, Instagram and Telegram, with one data model.
AI assistant
An agent drafts a reply from the conversation history, and the user reviews it before it is sent.
Advisor follow up
A consultant or agent keeps track of the clients they already talk to on Messenger.
Meta's Terms still apply
A connected account remains bound by Meta's Terms of Service. Build for conversations the user would have anyway: unsolicited messages and unauthorized automation can lead Meta to restrict the account.
Building a single inbox across networks? See how a unified messaging API works.
Graph API
Facebook API for Personal Accounts: What the Graph API Still Allows
A Facebook API personal account integration through Meta's Graph API is narrow. It can identify the person and read a few profile fields, but it cannot open their Messenger inbox or publish on their behalf.
Identity still works. With Facebook Login, the person grants your app a user access token. The public_profile permission reads the default public profile fields and email reads their primary email address. Other user permissions, such as user_posts for the posts a user made on their timeline, are limited by Meta to a short list of approved uses. No user permission gives access to the person's Messenger conversations. How these tokens are issued is covered in our guide to the Facebook API access token.
Publishing to a profile ended in 2018. Meta removed the publish_actions permission on April 24, 2018, and apps already approved for it could keep using it until August 1, 2018. Since then, apps built on the Graph API publish to Pages only, which is why scheduling tools stopped offering personal profiles.
A connected account covers both sides. When the owner connects their personal account through Unipile, your app reads and sends its Messenger messages, and creates, edits and deletes its posts, comments and reactions. The publishing side is detailed in our Facebook post API guide.
| Action | Graph API with a user access token | Personal account connected via Unipile |
|---|---|---|
| Read the user's Messenger messages | No, no user permission covers the inbox | Yes, chats, messages and attachments |
| Publish on the user's profile | No, publish_actions was removed in 2018 | Yes, create, edit and delete posts |
| Reply to messages | No, the Messenger Platform serves Pages | Yes, reply or start a conversation |
Read the user's Messenger messages
Graph APINo, no user permission covers the inbox
Connected accountYes, chats, messages and attachments
Publish on the user's profile
Graph APINo,
publish_actions was removed in 2018Connected accountYes, create, edit and delete posts
Reply to messages
Graph APINo, the Messenger Platform serves Pages
Connected accountYes, reply or start a conversation
Sources: Meta's Permissions reference and Graph API changelog of April 24, 2018. Last verified: November 17, 2026.
Connect personal Facebook accounts to your product
Meta's Messenger Platform remains the right tool for a business answering people on its own Page. When your product needs a Facebook Messenger API, personal account included, let your users connect their own Facebook account and use one API for Facebook and your other channels.
EU Regulated
Digital Markets Act (DMA)
Each user connects their own account, with no profile storage. Unipile is not a Meta Partner. Read our Digital Markets Act page
Endpoint reference
All Facebook API endpoints in one place
Messages are one part of the picture. Browse every Facebook endpoint available with Unipile, from chats to posts, or read the complete Facebook API guide to compare Meta's official APIs with connected accounts.
Personal Facebook Account API FAQ
Quick answers on profiles, message history, first messages, reactions, Pages, chatbots, the Graph API and unofficial libraries.
Meta's Messenger Platform does not: it serves Facebook Pages and Instagram professional accounts. A personal profile can be used when its owner connects it to your app through Unipile's hosted authentication, and the owner stays bound by Meta's Terms.
Yes, once the account is connected. The API lists the chats and messages of the connected personal account, including group conversations and attachments, and webhooks push new, edited and deleted messages to your app.
Yes. A connected personal account can start a new conversation as well as reply. Keep it to people the user knows or works with: unsolicited messages go against Meta's Terms and can get the account restricted.
Yes. You can list, add and remove reactions on messages, and new reactions reach your app through the message.reaction.new webhook event.
Yes, for Pages the connected user manages. Your app can read and reply to the Page's messages and publish as the Page. A Page cannot start a conversation or delete its messages, so Page threads always begin with the person writing first.
Meta's Messenger Platform, and the chatbot builders that rely on it, work with Pages only. With a connected personal account, keep a person in the loop: an AI drafts a reply and the user approves it. Fully automated or unsolicited messaging can get the account restricted.
Partly. Meta's Graph API still accepts a personal profile for Facebook Login and a few read permissions, but it cannot open the person's Messenger inbox, and it has not published to profiles since publish_actions was removed in 2018. For a Facebook API personal account setup that covers messages and posts, the owner connects the account through Unipile and your app works with one REST API.
Yes. Open source libraries that sign in to messenger.com with the user's own session exist, but they are unofficial and not supported by Meta. They can stop working when Facebook changes its interface, and the account that uses them can be restricted under Meta's Terms. For a production app, use the Messenger Platform for Pages you manage, or a maintained API where the user connects their own account and stays bound by Meta's Terms.
Not through their Facebook Messenger integrations: those rely on Meta's Messenger Platform, which serves Pages only. With a personal account connected through Unipile, the message is sent from your own workflow, for example an HTTP step that calls the send message endpoint for that account.
No. Unipile is an independent company: it is not a Meta Partner and is not endorsed, sponsored or approved by Meta. Connecting a personal Messenger account through Unipile is not an official Messenger Platform integration. Facebook and Messenger are trademarks of Meta Platforms, Inc.
No. The account owner signs in through Unipile's hosted authentication, so you do not register a Meta app, request pages_messaging or go through App Review on your side. The same goes for the Pages that user manages.
Unipile is designed in the spirit of the Digital Markets Act. Each person connects their own Facebook account, messages are read and sent on their behalf, and Unipile does not store user profiles. Details on our Digital Markets Act page.
Yes. A connected personal account is still a Facebook account under Meta's Terms. Keep to legitimate uses such as answering customers, syncing conversations into a CRM or helping a user manage their own inbox; bulk or unsolicited messaging can get the account restricted.
Still have questions? Our team is here to help.
Talk to an expert
