Yes, the API is built for the work that comes after the search, not just the search itself. Looking at live availability, holding seats, sending the name list, asking for a change and cancelling can all be driven from your own booking engine, so your staff stay in one screen instead of jumping between systems. Your eazyPNR login stays there as well, for your own checks and for anything your developer has not wired up yet.
The part to get right is deadlines. Every block carries its own name list deadline, release date and ticketing time limit, set by the seller's contract with the airline, and those dates do not move just because a request came through an API rather than from a person. Your engine should read those dates back with each listing and put them in front of whoever is making the booking, because a name list that lands after the cut-off can mean the seats go back and have to be asked for again.
After ticketing the same logic applies. Once the names are in and the seats are ticketed, the PNR sits with the airline, so a name correction, a date change or a refund follows that airline's rules on that fare, and careless changes are what invite an ADM later. Keep the net fare you pay and the agent fare you quote apart in your own records, since your customer only ever sees the net fare plus your markup.
The sensible next step is to register on eazyPNR to see live seats, then let your developer work against the API documentation in your account while your team keeps booking as usual.