Yes, that is what the API is built for. When your booking engine sends a search to eazyPNR, FD & Series Fares (Fixed Departures and Series Fares) listings come back as structured results, so your developer can place them on the same results page as your published and low cost fares. You decide how it looks, either mixed in with everything else or under a separate group seats tab. Your customer just sees one set of options and picks one.
Each listing carries the details your engine needs to sell it properly, such as the flight and date, the cabin and the baggage as filed by the seller, the net fare, and the dates that matter, including the name list deadline, the release date, the cut-off and the ticketing time limit. Your engine adds your own markup on top of the net fare, so the customer only ever sees your agent fare and never the seller's net fare.
One thing to respect is that availability is live. Blocks get sold, extended or released through the day, so your engine should search fresh rather than quote from a copy it saved yesterday, and it should re-check before it confirms. Conditions on changes, name corrections, payment and refunds are set by the airline and by each seller's contract, so pass through the conditions attached to the listing instead of applying one blanket rule to every seller.
The sensible next step is to register on eazyPNR, look at the live seats in the portal first so you know what the data looks like, then hand your developer the API details and connect your engine.