Notifications API Architecture: How Do You Handle Destination IDs?

[belalali0626]

I'm implementing notifications with Amazon's Selling Partner API (SP-API) and would like community feedback on best practices for handling notification destination IDs.
Specifically, I'm wondering:

1. Do you store SP-API destination IDs in your database or hardcode them in your application code, considering they rarely change?
2. For multi-regional sellers/marketplaces, what's your approach to managing these destination IDs?
3. If you hardcode them, how do you handle configuration updates when Amazon requires changes?

I'm interested in hearing from others who have built systems using SP-API notifications, particularly for solutions that operate across multiple Amazon marketplaces. Any insights on scaling SP-API notification handling would be appreciated.