Changes
The content of
idfield ofSupOfferwill change from a simple number into a string.The change will take effect on
Context
Previously, a seller's offer for a part (SupOffer) was identified by a numerical identifier (id) presented as a String (ID!) field. Due to an upcoming system improvement, these identifiers are now changing into hashed values represented as strings.
Offer IDs | Examples | |
|---|---|---|
Current ID | Number in String Format |
|
Upcoming ID | String Value in String Format |
|
Impact on API Clients
Under normal circumstance, developed applications should not be impacted by this change. If you are not storing our old encoded offer identifiers, you will not be affect by these changes.
However, if you happen to be storing these values, you will need to refresh manually any remembered identifiers. (As a reminder, it is against our T&Cs to store Nexar data for more than 24 hours.)
Developers who are casting the value into an number, such as via: offer_id = int(offer.id)will need to update their application to avoid making this assumption because values of SupOffer.id.
If you have any questions, please don’t hesitate to open a support ticket https://support.nexar.com/ or email support@nexar.com
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article