Yes, the name list and PNR steps can be handled through the API, so in most cases your staff do not have to repeat the same work by hand in the dashboard. The API follows the same booking lifecycle an agent works through manually on FD & Series Fares (Fixed Departures and Series Fares), which is searching the blocks, holding the seats, sending the name list, getting the PNR, then moving to ticketing within the ticketing time limit. Your developer works through the same stages rather than a different process.
In practice your booking engine sends the passenger names against the block you are holding, before the name list deadline on that departure. Once the seller has processed it, the PNR comes back on the booking record and your engine can read it and show it to your own staff or your customer. The net fare stays the net fare in the data your engine receives, and whatever markup you add on top is yours to control, so your website or agent portal keeps quoting your own agent fare.
How far this runs without a human depends on the airline and on the seller's contract. Some sellers review name lists before confirming, or need passport details and other papers for certain departures, so the booking sits in a pending state until they act on it. Release date and cut-off still apply exactly as they do manually, because connecting by API does not extend any deadline. Name spellings matter just as much here, since a wrong name on a ticket can mean a correction charge or an ADM later, and that risk follows whoever submitted the data.
If you want your developer to see the real booking flow, register your agency on eazyPNR, get verified, and then look at the live seats and the API documentation together.