Originally Posted by
gypsyjaney
As some of you have correctly observed, the real annoyance is that it will not let me do OLCI unless I keep on entering my details each time. So unless I do this it's no seat selection for me.
If your route requires API to be entered into the booking, it has always been the case that you're not allowed to OLCI until you have entered the API. This has not changed.
The thing that might have changed is if your API was previously being automatically populated from your BAEC profile, but your passport has expired. I don't know what happens when this occurs, but it may be that the auto-population stops so that you have to enter your API manually again.
It could also be that you're now flying different routes, because API requirements are different on different routes.
There are some routes that also
always require the API to be
re-entered after you've picked your seat and checked-in, if you want to print a boarding pass (or be able to see the seat map again and change your seat if you don't print a boarding pass). You can't get around this. You just have to do it.
Originally Posted by
gypsyjaney
I guess it's the Customer Service route for me if it persists.
Customer Service won't be able to do anything about it if you must enter API and you haven't done so.
Anyway, what is the big deal about putting in your API? Why is it so hard? I have to do it so often that I have memorised all my passport details and all those of my companion.