Managing IDs

Avoid Hard-Coding IDs: Product and Rate IDs are more consistent but are subject to change. RatePrice IDs will change frequently as the operators change things in their system. Instead of hard coding, use real-time data or configurable mappings.

RatePrice IDs: Especially prone to frequent updates.

• Use dynamic mapping by fetching RatePrice IDs in real-time from the API whenever needed. This ensures that the IDs are always up-to-date, reducing the risk of errors in your integration. For example, retrieve RatePrice IDs from the GET /Price Schedule endpoint when displaying pricing options to users, or as part of your nightly caching routine.
• Or configurable mappings by implement a mapping layer in your system that allows IDs to be updated from the API periodically and mapped to internal configurations. Example: Maintain a database of RatePrice IDs for each product and supplier, refreshing the data frequently.