Meta Facebook Technical Setup
From Standout Property Manager Wiki Help
Meta Facebook Technical Setup
This page is for ISSL / Standout technical administration. Normal estate-agency users should use Meta Facebook Property Catalogue.
Standout uses one centrally owned Meta application. Customers authorise that app to their own Business Portfolio/catalogue through Facebook Login for Business. Do not revert to the old model where every estate agent creates its own developer app and pastes access tokens into Standout.
Architecture
ISSL-owned Standout Meta app → customer Facebook Login for Business authorisation → customer Business Portfolio → customer Home Listings catalogue → Standout property synchronisation
Global values are held centrally in Tools → Meta API. Agency records store only their authorised business/catalogue connection and encrypted authorisation token.
Central values in Standout
Open:
Tools → Meta API
Configure:
- Meta App ID;
- Meta App Secret - stored encrypted; leave blank later to keep the current secret;
- Facebook Login for Business Configuration ID;
- Graph API version;
- Catalogue name prefix;
- the exact OAuth redirect URI shown by Standout must be registered in Meta.
Customers never see the App Secret.
Meta changes labels occasionally, but the current Standout app is administered from:
Meta for Developers → My Apps → Standout Property Manager
The left navigation used during setup/review includes:
- Dashboard;
- Use cases;
- Facebook Login for Business → Settings / Quickstart / Configurations / Templates;
- Review → Testing / Verification / App Review;
- Publish; and
- App settings.
When rebuilding or checking the app, use the page names shown in Meta rather than relying on old screenshots from the previous developer interface.
Meta application requirements
The application must be owned by the ISSL Meta Business account and configured for production use.
The Standout integration needs the permissions required to manage authorised business catalogues, principally:
- `catalog_management`;
- `business_management`; and
- `public_profile` as part of the Facebook Login flow.
Do not request unrelated Page or Ads permissions merely because a Meta use-case wizard happens to expose them. App Review should contain only permissions Standout genuinely uses.
Use cases and Facebook Login for Business
Meta changes its developer UI regularly. In the current application model, the app includes the Catalog API use case and Facebook Login for Business. A Marketing API use case may also appear because Meta's current use-case UI exposes `business_management` through that path; that does not mean Standout uses Ads Management.
The Facebook Login for Business configuration should be set up to let the customer choose the correct Business Portfolio/catalogue assets and grant the catalogue/business access required by Standout.
In Meta's current configuration wizard, `catalog_management` can appear in the configuration permission chooser while `business_management` may not. Do not assume that means `business_management` is unavailable: the app requests/reviews that permission through the relevant use case/App Review path. Keep the configuration limited to the assets/permissions the integration genuinely needs.
Copy the resulting Configuration ID into Tools → Meta API.
Business and Access Verification
Because Standout is a Tech Provider accessing authorised assets belonging to other businesses, complete Meta's verification flow for the ISSL business:
- Business verification;
- Access verification / Tech Provider verification;
- any other current Meta verification requirement shown for the app.
Published app status alone does not grant Advanced Access to client-business data.
App Review / Advanced Access
Request production/Advanced Access for the permissions Standout actually uses.
`catalog_management` description
Explain that Standout Property Manager is a SaaS platform for estate/letting agents; the customer explicitly connects its Meta Business Portfolio; Standout creates/reads/updates/removes the customer's property Home Listings; and property changes in Standout are synchronised to the authorised catalogue.
`business_management` description
Explain that Standout uses the permission to identify the Business Portfolio and business assets explicitly authorised by the customer, and to associate the correct catalogue with the correct estate-agency account. Standout does not use this permission to manage advertising accounts or obtain unrelated advertising analytics.
Screencast
Show the complete user experience:
- Standout Administration → Feeds/Portals → Outbound feeds;
- Connect Meta Account;
- Facebook Login for Business;
- select the test Business Portfolio/assets;
- return to Standout showing Connected;
- enable the required property groups;
- run Sync now;
- show the resulting Home Listing/catalogue in Meta.
Do not submit a video that ends in a permissions error.
Required API test calls
Meta can require recent successful Graph API calls before App Review can be submitted. Test results can take up to 24 hours to appear and may expire after the period shown by Meta.
Using Graph API Explorer with the Standout Property Manager app and a test user/business that the app is allowed to access, useful calls include:
GET /me/businesses?fields=id,name
This exercises `business_management` and should return the Business Portfolios visible to the test user.
Then identify a test Business Portfolio and run:
GET /BUSINESS_ID/owned_product_catalogs?fields=id,name,vertical
Choose a catalogue where `vertical` is `home_listings`, then run:
GET /CATALOG_ID?fields=id,name,vertical,owner_business{id,name}
GET /CATALOG_ID/home_listings?fields=id,home_listing_id&limit=1
An empty `data` array from `/home_listings` is a successful API call; it simply means the catalogue has no Home Listing items yet.
Never publish the access token from Graph API Explorer in documentation or tickets.
Reviewer instructions
Give Meta a dedicated Standout reviewer/test account that can reach:
Administration → Feeds/Portals → Outbound feeds → Meta / Facebook property catalogue
The reviewer instructions should explain that Facebook Login for Business is used to authorise the customer's Business Portfolio/catalogue and that `business_management`/`catalog_management` are used only for those authorised business assets.
Data handling / privacy
The Standout privacy policy used for App Review must accurately describe the optional Meta integration and any Platform Data received from Meta.
Do not claim that Standout never shares/processes data with third parties if the Meta integration sends property catalogue data to Meta at the customer's direction.
ISSL is the legal entity operating the Standout Meta application. List actual processors/service providers honestly in Meta's Data Handling questionnaire; do not select policies/processes that are not genuinely in place.
Error 10: Application does not have permission for this action
If Graph API Explorer can access the test business/catalogue with the correct permissions but the customer Facebook Login for Business connection returns:
`Meta API error 10: Application does not have permission for this action`
check the app's Access Verification and App Review/Advanced Access status before changing Standout code. The cross-business System User token can remain restricted until Meta has approved the required production access.
After approval, reconnect the customer so a fresh authorised token is issued.
Security
- App Secret is global and encrypted in Standout.
- Agency authorisation tokens are encrypted.
- Do not paste customer or Graph API Explorer tokens into wiki pages, email or public tickets.
- Use the exact OAuth redirect URI shown in Standout.
- If the Facebook Login for Business Configuration ID changes, update the shared Tools setting deliberately and retest a customer connection.