Yes, they come back automatically. Anything your staff would see against a booking on eazyPNR is available to your booking engine through the same API, so nobody has to retype a PNR or a ticket number from one screen into another.
When your engine sends a booking request, the reply carries the booking reference, the airline PNR once the seller has created it, the status of the seats you are holding, and the dates that matter to you, which are the name list deadline, the release date and the ticketing time limit. Your engine can come back and read the same booking again later, so when names are accepted or the status moves on, your own system updates without anyone logging in separately.
Ticket numbers work the same way, with one point of timing to plan for. Some sellers issue tickets as soon as the names are in, while others wait until the cut-off has passed, and that depends on the airline and on the seller's own contract. So the ticket number may sit empty for a while after the seats are confirmed. Tell your developer to read the booking status rather than assume a ticket number exists the moment a booking is accepted.
On fares, your engine receives the agent fare with your markup already applied for whoever is buying, and your net fare stays on your side of the wall. Keeping names in one record instead of copying them between systems also cuts down spelling mismatches, which are a common root of an ADM later. The next step is to register on eazyPNR, see the live seats in your account, and let your developer test the API against real listings.