api design: how do you deal with eventual consistency

Hey everyone, I've been struggling a bit with designing APIs for systems that are, well, eventually consistent. Like, when a user changes their profile info, how do you let other services or the UI know without making them wait? Should we just send out events, maybe add a 'status' field that people have to keep checking, or is there a better, more standard way to do this with APIs? I'd love to hear what you all prefer and what to watch out for.