Originally Posted by
golfmad
It's virtually unfathomable. My API data usually doesn't but sometimes does populate automatically. The most annoying thing is the part at the end where it helpfully asks whether I'd like to save my API to avoid having to enter it in future. I say 'yes'. Fast forward to the next time, rinse and repeat.
I'll second that and add Mrs Clam seat pref = aisle, mine = window and irrelevant of who is lead pax or whose CC is used ( as I know BA like to default lead pax to the CC payer listed on initial transaction) our bookings hold a pretty consistent 90% seating pref transposed irrelevant of cabin, LH/ SH or any other factor you can think of. I've always let BA off with the API thing not carrying over as I have multiple active passports issued by different nation states and whilst you can only register one with BA i've just assumed that somewhere in the background some overarching DB highlights that fact and causes a conflict but maybe it's just an inexplicable part of BA IT that means your API carries over if the day has an S or T in it, the weather is projected to be clement that day or Sandra the tea ladt at Waterside happened to be wearing a mauve blouse on the the day you made the booking?!?!?!
On the basis any API conflict can be resolved at check-in if need be i'd just ignore it despite the confusion and annoyance it causes from time to time