Guides
Tracking product updates
When you store product relations in your own application, you might want to know when a product is changed so you can validate your configurations.
When you store product relations or configurations in your application, you might need to know which products are outdated. In the /products
endpoint, there is a property per product with the updated date.
Example
{
"meta": {
...
},
"data": [
{
"code": "deco-fabric",
"article_group_name": "Material",
"unit_code": 1,
"translations": {
"en": {
"title": "Deko fabric",
"description": "Deko fabric"
},
"de": {
"title": "Dekostoff",
"description": "Dekostoff"
},
"nl": {
"title": "Dekostof",
"description": null
}
},
"created_at": "2018-01-08T15:59:59+0000",
"updated_at": "2022-07-19T07:16:37+0000"
},
{
...
},
]
}
To only retrieve updates after a certain date you can supply updated_at_from
& updated_at_to
parameters in the call. You'll only get the product updates between this date.
Managing your catalog
It might happen that a Probo product is discontinued, and sometimes, it is also replaced with a new product. Via the API, it is possible to automatically update your own catalog.
First, you should set up a scheduled job that checks for product updates after a given timestamp. You should store the "last checked date", to only get the recent product updates.
Secondly, fetch every product that has been updated and check for any of the given parameters
Parameter | Explanation | |
---|---|---|
active |
If the current product is still active. | When false you should no longer use this product |
active_to |
The date until the product is active | This is an indicator of when the product is discontinued. |
replaced_by_product |
Indicates an replacing product. | Some products might have a successor, this is the API code for this product |
Example Forex
{
"active": true,
"active_to": "2999-12-30T23:00:00+0000",
"replaced_by_product": "2024-forex",
"code": "forex",
...
}