Request for public API to retrieve verified_entities for regional_regulation_identities used in AdSet creation

[voidbean]

Summary

The Java SDK supports setting regional_regulation_identities when creating or updating an Ad Set (e.g., setRegionalRegulationIdentities).
The corresponding model RegionalRegulationIdentities includes fields such as singapore_universal_beneficiary and singapore_universal_payer.
There is no public SDK/Graph API edge to list the available regulations and their verified entities for an Ad Account.
The Ads Manager UI obtains this data using an internal GraphQL operation: useAdAccountCAAPRegulationVerifiedEntitiesLiveQuery (doc_id-based, cookie-authenticated), returning structures like:

{
  "regulations": [
    {
      "regulation_type": "SINGAPORE_UNIVERSAL",
      "verified_entities": [
        {
          "verification_entity_id": "1",
          "full_descriptive_name": "1",
          "status": "FAILED"
        },
        {
          "verification_entity_id": "2",
          "full_descriptive_name": "2",
          "status": "VERIFIED"
        }
      ]
    }
  ]
}

Actual Result

• No public Marketing API or SDK edge to retrieve verified_entities.
• Only an internal, cookie-based GraphQL call in Ads Manager returns the required IDs, which is unsuitable for server-side automation and not part of the supported public API.

Request

• Please expose a public, access-token-based Marketing API endpoint (and document it) to fetch regulations and verified_entities for an Ad Account.
  • Listing regulations relevant to an Ad Account.
  • Listing verified_entities for each regulation_type, including verification_entity_id, full_descriptive_name, and status.

This would enable programmatic discovery and population of regional_regulation_identities when creating/updating Ad Sets.

Additional Information

• Example internal call observed in Ads Manager UI (redacted and provided only as reference; not usable with app tokens):

POST https://adsmanager.facebook.com/api/graphql/
x-fb-friendly-name: useAdAccountCAAPRegulationVerifiedEntitiesLiveQuery
variables: { "adAccountID": "act_<AD_ACCOUNT_ID>", "regulationTypes": ["SINGAPORE_UNIVERSAL"], "skipExperienceAPI": false }
doc_id: <internal_doc_id>

• SDK references (Java):
  • AdSet.setRegionalRegulationIdentities(...)
  • RegionalRegulationIdentities model (fields include singapore_universal_beneficiary, singapore_universal_payer, etc.)

Thank you for considering this request. Providing a public, documented endpoint would significantly improve developer experience and enable compliant, automated ad operations in regulated markets.

[rafaelargentametadata]

Still waiting for that one.