[Bug Report: Documentation Errors] Subaccount / Location APIs - Missing a LOT of Fields

[i-am-rad]

🐛 Describe the Bug

There are a lot of data objects that can be set by the API that are missing from public docs. Example are all the A2P fields.

There are also things in search locations and get location by Id that are missing lots of data in the results. If you compare private API to public api there is so much useful information that is lost that holds value for agencies that can use the APIs to retrieve it.

📍 API Endpoint

/locations

✅ Expected Behavior

Compare private API to public API for all location APIs. Unless there is a justified reason to not give us this data, then please release it to us if it holds useful value to agencies. If there is concern about data payload sizes give us booleans for additional data objects so we can opt in to those.

💻 Screenshots or Code Samples

No response

Product Area

saas

🧠 Additional Context

No response

[github-actions]

✅ Issue processed successfully!

Your issue has been reviewed and assigned to the appropriate team.

[lisacatto]

This is so essential to have all of the fields available for us to be able to effectively manage multiple locations.

[singhdaljeet007]

@i-am-rad we've updated the OAUTH responses for location APIs - locations GET, search, PUT, CREATE.
Please note that there are few fields which are for internal use only and few are deprecated thus can't be added to the response