List and relist item

I try to explain my system...

The item is published on delcampe by api. Then I got the notification: "Seller_Item_Add" with the id_item and the personal_reference, so I can connect my id to delcampe id.

When the item sell end, I got the notification: "Seller_Item_Close_Unsold", so I resend the item again and I should got another "Seller_Item_Add" with the new id_item, and so on...

But... doesn't work.

For the same item (with the same personal_reference that is unique), I got many notifications with different Datetime (timestamp). I've tried to use "notificationDelete" to delete the notifications already received, but "notificationDelete" require a notification id that isn't linked to the "Seller_Item_Close_Unsold" or "Seller_Item_Add". More, using "notificationDelete" is also changed the notification status on or off.

So, how I can delete the notification relative to the item added and process the next one?

In the documentation I read:

"To update a notification to the latest version, you have to disable the older one (by calling the resource NotificationDelete) and set the new one (by calling POST /notification/settings). Doing so, you will have the newest version set automatically."

But how I can do this correctly and how I can manage multiple items concurrently?

Thanks.

Die Informationen sind nicht mehr verfügbar, da das Konto dieses Benutzers gelöscht wird (DSGVO-Grundverordnung).

Ok, I've tried to get notifications settings:

GET /notification/settings
For example for the Curl_Default type I got:

[id_notification] => 133827
[id_user] => 64xxxx
[channel] => curl
[type] => Curl_Default
[destination] => Link (https)
[active] => 1

[id_notification] => 133889
[id_user] => 64xxxx
[channel] => curl
[type] => Curl_Default
[destination] => Link (https)
[active] => 1

[id_notification] => 133904
[id_user] => 64xxxx
[channel] => curl
[type] => Curl_Default
[destination] => Link (https)
[active] => 1

[id_notification] => 133919
[id_user] => 64xxxx
[channel] => curl
[type] => Curl_Default
[destination] => Link (https)
[active] => 1

[id_notification] => 133928
[id_user] => 64xxxx
[channel] => curl
[type] => Curl_Default
[destination] => Link (https)
[active] => 1

So, why for the same notification type I've 5 different notifications with different id? What id_notification refers to?

Thanks...

Dear vaccarisrl,

I think there is a misunderstanding of how notifications work. Notifications in our api are used to set a destination to send notifications. It is not a notification itself.

In this sense the notificationDelete will not delete notifications but will delete the notification's destination.

The notifications received are just http calls with xml in the POST data.

I can see that all your notification's type have 5 copies. Should I disable them ?

I hope to have been clear.

Don't hesitate to come back to us if you have any questions on the behavior of notification.

Best regards

Yes, you can disable duplicate notifications as they refer all to the same url. Probably I misunderstood how notifications work, but on the documentations it isn't really clear

So I don't need to activate and deactivate the notification every times server received one notification?

Or I need to delete/deactivate whenever the server receive one notification to disable the old one and receive the new notification?

Thanks.

Die Informationen sind nicht mehr verfügbar, da das Konto dieses Benutzers gelöscht wird (DSGVO-Grundverordnung).

Die Informationen sind nicht mehr verfügbar, da das Konto dieses Benutzers gelöscht wird (DSGVO-Grundverordnung).

Ok, now is a little more clear

Yes, please remove duplicated notification settings.

Then I've another question, why sometimes I got: "Max number of notification by type reach"?

What means this error?

Thanks...

Die Informationen sind nicht mehr verfügbar, da das Konto dieses Benutzers gelöscht wird (DSGVO-Grundverordnung).