Oauth permissions for listing views

Hello, @nigelmorford 

Why It's Unclear from Dev Docs
If the API documentation states this functionality isn't possible, it could be due to one of these reasons:

Scope Limitations: OAuth scopes may not explicitly include permissions to list views.
Undocumented API Endpoints: Some APIs expose endpoints that aren't documented but are accessible to partners like Make.com or Zapier.
Custom Implementations: Make.com and Zapier often leverage special partner access to APIs, which may include elevated privileges or dedicated endpoints.
How Make.com and Zapier Do It
Predefined Connections: These platforms often have pre-built integrations with APIs that might use service accounts or access tokens that bypass standard OAuth restrictions.
Scoped Partnerships: They may negotiate special API scopes or use internal APIs not available to general developers.
Workarounds: They could be parsing metadata or leveraging other endpoints to derive a list of views indirectly.
Is It Possible for You?
Check OAuth Scopes: Look into the OAuth scope configurations of the API. Some APIs may require higher-level scopes for accessing view data.

For example, in Salesforce, to list views, you may need access to specific objects or metadata-related scopes.
For Google services, ensuring you have sufficient read or admin privileges might be necessary.
Enterprise Access: If you’ve done this using enterprise access tokens, see if OAuth tokens can be issued for similar scopes. Some APIs allow scope elevation via administrator consent.

Query Other Metadata Endpoints: Some APIs allow indirect retrieval of views through related metadata endpoints. For example:

In Salesforce, querying the ListView metadata object.
In other CRMs or tools, querying custom object or view settings.
Contact API Provider: Reach out to the API provider to clarify whether this functionality is supported with OAuth. They might clarify undocumented capabilities.

Best Regards