For SSL certs, this is a common practice and frequently needs to be coordinated between close integration partners so that nothing breaks.
For SSL certs, this is a common practice and frequently needs to be coordinated between close integration partners so that nothing breaks.
If you can provide clients with ample warning about any upcoming changes, and preferably provide them with a staging/dev instance they can test their code against, it might help avoid similar problems in future.
In my experience, clients get frustrated when their business-critical processes suddenly break with no warning and they have to engage in fire-fighting. From their perspective, they had something working one day, then you "made a change" and "all their stuff broke". That might not be a fair assessment, and it might well be due to shoddy practices on their end, but the end result is the same: the client is frustrated and has a bad experience of using your product.
What kind of communication channels have you guys seen or used for that kind of scenario? A separate Twitter feed? A blog? Sending an email to all customer every time the SSL certificate changes in any way?