Yes, on most blocks the seat is confirmed the moment your engine sends the booking through, but whether it is instant or on request depends on the seller and on how that particular block has been set up.
Where a seller is holding the inventory already and has chosen instant confirmation, your booking engine calls the API, the seat comes out of availability right away, and you get a booking reference back along with the PNR if the seller has already created one. Where the seller has marked a block as on request, the API accepts your booking and returns it as pending, and the seller confirms or declines in their own time. The important thing for your engine is to show your customer as confirmed only once the API has sent back a confirmed status, not when the request is first accepted, otherwise you are promising a seat that is still being looked at.
Confirmation also does not mean the booking can then be left alone. The name list deadline, the ticketing time limit and the block cut-off still apply exactly as they would if you had booked by hand, and if names or ticketing are not completed in time the seller can release the seat back. Your engine should read those dates from the API and chase them, rather than you keeping a separate diary. The net fare stays what you agreed with the seller, you add your own markup, and your customer only ever sees the agent fare you choose to show them.
To see how this behaves on live blocks before you build around it, register on eazyPNR, look at what sellers are loading, and connect your engine from there.