Yes, the API is built to carry a sale all the way through, not just the search. Your booking engine can pull live FD & Series Fares (Fixed Departures and Series Fares) listings, hold seats from a block, send the passenger name list, raise the ticketing request and read the PNR and ticket status back into your own system, so your staff do not have to open the panel to finish a booking.
The deadlines travel with the data. Each listing carries its name list deadline, release date, cut-off and ticketing time limit, so your engine can show the right date on screen and stop accepting bookings once a block closes. Spelling corrections and name swaps after that depend on the seller's contract and the airline's own rules, so some can be pushed through the API and some still need the seller to action them, and where the airline does not allow a change at all, no booking engine can work around it.
What the API will not do is take the commercial decisions for you. The net fare comes through exactly as the seller has loaded it, while your markup, the agent fare you display and the way you collect payment all stay on your side of the connection. Some blocks confirm straight away and others come back on request because the seller or the airline checks the names first, so build your engine to handle a pending status rather than treating every request as confirmed. Keep the reference the API returns in your own records, because that is what you will quote if a query or an ADM comes up later.
Register on eazyPNR to see live seats and the API details, then run a few test bookings end to end with your developer before you open the connection to your agents.