No, you do not need a separate connection for each consolidator. One API link to eazyPNR gives your booking engine access to the FD & Series Fares (Fixed Departures and Series Fares) listings of every seller you are cleared to see, so your development team builds and tests once instead of once per supplier. You do not have to chase each wholesaler for their own technical setup, and when a new seller starts listing, their seats simply appear in the same search response your engine is already reading.
What comes back for each listing is the information your staff would otherwise read off a WhatsApp message or a spreadsheet, which is origin and destination, the departure date and timing, baggage, the net fare that is yours to buy at, and the dates that govern the block. That means the name list deadline, the release date and the ticketing time limit travel with the listing rather than being one rule for the whole platform, because those terms depend on the airline and on the seller's own contract for that series. Your engine should display them to whoever is selling, since missing a cut-off on one listing does not excuse it just because another seller is more relaxed.
On the booking side your engine sends the block request, passes the passenger names, and receives the PNR and the status updates back through the same connection. Your markup sits in your own engine, so the customer sees only the agent fare you decide to show while the net fare stays on your side of the wall. Because every seller is reached the same way, you can compare listings for the same route and date in one response and block from whichever one suits the group.
The next step is to register on eazyPNR, look at the live seats in the panel so you know what the data looks like, then have your team connect your booking engine to the API from your own account.