C# Design Pattern - Best Way to Design For Many Datasources

I currently have an ASP.Net MVC 5 app that uses 3 external datasources (calls are made to external APIs, responses are deserialized, and mapped to business POCOs).

The app currently uses SimpleInjector to inject concrete repositories for each datasource into a business logic layer for consumption.

The problem is, as more datasources are added (potentially 20-30), the constructor will be huge and injecting all these repositories seems cumbersome.

Is there a better pattern/approach to consuming all the datasources rather than using different repositories?

Would a facade or some other pattern be more appropriate?