Which design pattern is best suited to write a wrapper to multiple APIs?

I want to create a wrapper class or an API simple enough for a few open source libraries that can individually talk to different hardware devices or sensors and get some data which essentially is a set of data points and most of these libraries may provide some data in common but slightly different data structure.

For instance, Library A provides a vector of RGB frames from hardware A and Library B provides a vector of thermal image frames from sensor B and Library C provides machine learning algorithms that can be applied on these data streams.

So,

1. Which design pattern should I follow to achieve the above mentioned wrapper class or API?
2. Can anyone provide a tutorial resource or a relatively simpler open source API or wrapper class that I can refer to for it?