Having one pattern across the whole experience is usually a great idea. But don't force it. You may have to rely on a pagination model where there is a technical limitation in a few cases; it would be a loss to limit the whole interface to suit a minority of instances.
The key to either model is making it obvious to users that there is more to look at (and letting them see how). Some paginated models make it hard to see and can lead to users making decisions on the top-n records not knowing about n+1 (particularly bad if the are accustomed to having less than a pageful and don't notice the second page become available).
scroll your paged data - infinite scroll
If you have paginated data in the API you can still scroll it by loading the next page(s) below/above before they are needed. Tiled web map/Slippy map interfaces use this for 2 dimensional scrolling across paged/tiles data. (You'll need to handle the loading case for fast scrollers of course.)