Ready to post? 
First try sear
Subject: GET /api/v2/connections/{id} not returning options object for Facebook social connection
Environment
Tenant dev-f5l7vb5vs5q2vfh1.us.auth0.com
Region US
Plan Development
Connection ID con_nUJeUmyp39QKKtEl
Strategy facebook
Issue
The GET /api/v2/connections/{id} endpoint returns an empty options.scope for a Facebook social connection, despite permissions being visibly configured in the Auth0 Dashboard (Age Range, Events, Gender checked).
Endpoint Called
GET https://dev-f5l7vb5vs5q2vfh1.us.auth0.com/api/v2/connections/con_nUJeUmyp39QKKtEl
Also tried:
GET /api/v2/connections/:id?fields=id,name,strategy,options&include_fields=true
Token Scopes (confirmed present)
read:connections
update:connections
read:connections_options
read:connection_profiles
read:connections_keys
Grant type: client_credentials (M2M)
Audience: https://dev-f5l7vb5vs5q2vfh1.us.auth0.com/api/v2/
Actual Response
json{
“id”: “con_nUJeUmyp39QKKtEl”,
“options”: {
“scope”: “”
},
“strategy”: “facebook”,
“name”: “facebook”,
“is_domain_connection”: false,
“authentication”: { “active”: true },
“connected_accounts”: { “active”: false },
“enabled_clients”: [
“FKcJaCDTDCgkL9yukmvDxcqoxkFTSffz”,
“3eQ75QMDvaLRSpukXFDss8qMvPu6xlmJ”
],
“realms”: [“facebook”]
}
Expected Response
options should contain the Facebook permissions configured in the dashboard:
json{
“options”: {
“scope”: “public_profile,user_age_range,user_events,user_gender”,
“public_profile”: true,
“user_age_range”: true,
“user_events”: true,
“user_gender”: true
}
}
Dashboard Configuration (confirmed saved)
PermissionScope KeyStatusPublic Profilepublic_profile​
EnabledAge Rangeuser_age_range​ EnabledEventsuser_events​ EnabledGenderuser_gender​ Enabled
Questions for Auth0 Support
Is the options object intentionally excluded from the API response for Facebook social connections?
Is there a specific endpoint or parameter required to retrieve Facebook permission scopes via the Management API?
Does the read:connections_options scope unlock any additional endpoint or response fields not documented publicly?
Is this a known bug or a documentation gap?
ching for your answer.