Documentation
Reference material for integrating Homa Meta Platform with Meta’s Instagram, Messenger and WhatsApp Business APIs — authorization, permissions, tokens, webhooks and data deletion.
How the integration is structured
Homa Meta Platform sits between Meta’s Graph APIs and Homa CRM. It performs one job: it obtains explicit authorization from a business owner, stores the resulting credentials securely on the server, and uses them to synchronise only the messages and business assets that the owner selected.
Every authorization begins on Meta’s own consent screen and every credential exchange happens server-side. No access token, app secret or authorization code is ever exposed to a browser, written to client storage or included in a URL that a user can see.
These pages describe the integration as it is designed and deployed. Where a behaviour depends on Meta’s current API version or approval state, that dependency is called out explicitly rather than assumed.
Who these pages are for
- Reviewers assessing the integration
- Each page states what data is requested, why it is needed and how it is protected, so the permission model can be evaluated without reading source code.
- Engineers implementing or maintaining the flow
- The OAuth, webhook and token pages document the exact sequence, the required verification steps and the failure modes that must be handled.
- Business owners connecting an account
- The permissions and data deletion pages explain, in plain language, what access is granted and how to withdraw it.
Browse the documentation
Introduction
Authorization
Events and data