Búsqueda
Cerrar
  1. Página de inicio
  2. Foro
  3. API users
  4. Item delete error
Lista de foro Lista de mensajes

Item delete error

  • numisaisne-soissons
    numisaisne-soissons 99% (5239x)
    PRO advanced

    4 mensajes

    Francia

    Hi,
    We recently work with your api to add item and update our stock on Delcampe, everything works fine until a out of stock item, the delete request return this error :

    "Oops! An Error Occurred The server returned a "405 Method Not Allowed". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused."

    I try with and without optional parameter but same response.

    regards.
  • klaus_schneider
    klaus_schneider 100% (84983x)
    PRO advanced

    289 mensajes

    Alemania

    Hello,
    we have the same problem.
    Since December 13th From around 4 p.m. the deletion no longer works. Why doesn't Delcampe treat us to a happy and peaceful end to the year. Always these unnecessary problems. We also sell on eBay and HOOD and I can't remember any significant problems with the API here in the last 10 years.

    With Delcampe I could write a whole book about it.

    Something is fundamentally wrong with you!!! Kind regards
  • cartespostales_de
    cartespostales_de 100% (172010x)
    PRO premium

    69 mensajes

    Alemania


  • cartespostales_de
    cartespostales_de 100% (172010x)
    PRO premium

    69 mensajes

    Alemania



  • cartespostales_de
    cartespostales_de 100% (172010x)
    PRO premium

    69 mensajes

    Alemania

    this is not spam, my answers are always empty after submitting...
  • cartespostales_de
    cartespostales_de 100% (172010x)
    PRO premium

    69 mensajes

    Alemania

    next try, please html_entity_decode the message...

    Same here :help:

    and same at GetItem Call
    there is an empty Response-Body

    <?xml version="1.0" encoding="UTF-8"?>
    <Delcampe_Notification>
    <Notification_Token></Notification_Token>
    <Notification_Datetime>2023-12-14 08:01:03</Notification_Datetime>
    <Notification_Data>
    <Headers>
    <Ressource>item/12785783</Ressource>
    <Action>GET</Action>
    <Status>200</Status>
    </Headers>
    <body>
    </body>
    </Notification_Data>
    </Delcampe_Notification>
  • cartespostales_de
    cartespostales_de 100% (172010x)
    PRO premium

    69 mensajes

    Alemania

    next try, please html_entity_decode the message...

    Same here :help:

    and same at GetItem Call
    there is an empty Response-Body

    <?xml version="1.0" encoding="UTF-8"?>
    <Delcampe_Notification>
    <Notification_Token></Notification_Token>
    <Notification_Datetime>2023-12-14 08:01:03</Notification_Datetime>
    <Notification_Data>
    <Headers>
    <Ressource>item/12785783</Ressource>
    <Action>GET</Action>
    <Status>200</Status>
    </Headers>
    <body>
    </body>
    </Notification_Data>
    </Delcampe_Notification>
    Aha, htmlentities(message) will work
  • collectoravenue
    collectoravenue 100% (2012x)
    PRO free

    31 mensajes

    Italia

    Hi,
    I experience the same problem with all my customers.
    At least from 13-12-2023 12:04:48 (that's the timestamp of the first error our app logged)
  • @lco
    Cuenta cerrada

    94 mensajes

    Bélgica

    We have identified an issue that may be linked to the new behavior of returning multiple items for a single personal reference, a feature requested here: Vinculo (https)
    This have been deployed yesterday. We're currently working on a fix.

    Regards,

    Laurent.
  • numisaisne-soissons
    numisaisne-soissons 99% (5239x)
    PRO advanced

    4 mensajes

    Francia

    Ok thank you for your reply
  • klaus_schneider
    klaus_schneider 100% (84983x)
    PRO advanced

    289 mensajes

    Alemania

    Hello, the problem that it is possible to upload more than one article with the same personal reference is very, very old. This is due to the fact that the personal reference is not treated as a key field and, on the other hand, to the fact that there are always unclear situations when uploading articles (also a 10-year-old problem). This then leads to the same article being uploaded again because there is no clear feedback status from the previous attempt and therefore the article exists twice and with it the same personal reference. This in turn is due to the situation that there is no direct transfer with feedback of the assigned item number, but rather the request goes into a queue and the item number is only reported back later. In principle, a fundamentally flawed design with the resulting problems... Kind regards
  • klaus_schneider
    klaus_schneider 100% (84983x)
    PRO advanced

    289 mensajes

    Alemania

    Hello, until now there was no problem with deletion if there was more than one article with the same personal reference. All of them were reported back and subsequently all of them were deleted. Kind regards
  • @lco
    Cuenta cerrada

    94 mensajes

    Bélgica

    Hello, the problem that it is possible to upload more than one article with the same personal reference is very, very old. This is due to the fact that the personal reference is not treated as a key field and, on the other hand, to the fact that there are always unclear situations when uploading articles (also a 10-year-old problem). This then leads to the same article being uploaded again because there is no clear feedback status from the previous attempt and therefore the article exists twice and with it the same personal reference. This in turn is due to the situation that there is no direct transfer with feedback of the assigned item number, but rather the request goes into a queue and the item number is only reported back later. In principle, a fundamentally flawed design with the resulting problems... Kind regards
    Klaus,

    you'll find more information about the item adding process being asynchronous on this post reply: Vinculo (https)

    As long as you have no received the callback of the item creation, you should not try it again or you'll end with duplicates

    Laurent.
  • @lco
    Cuenta cerrada

    94 mensajes

    Bélgica

    Hello, until now there was no problem with deletion if there was more than one article with the same personal reference. All of them were reported back and subsequently all of them were deleted. Kind regards
    We have been requested last week to make the personal reference non unique because some of the API users use it to group and sort their collections. Please referrer to this post: Vinculo (https)

    We experienced a small change in the behavior of the API endpoint, because trying to get an item on an non-existing personal reference use to respond a 404. Now we are expecting a collection, so it will respond a 200... with an empty body.

    The fix to get the original behavior back will be deployed in a moment.

    Regards,
    Laurent.
  • @lco
    Cuenta cerrada

    94 mensajes

    Bélgica

    next try, please html_entity_decode the message...

    Same here :help:

    and same at GetItem Call
    there is an empty Response-Body

    <?xml version="1.0" encoding="UTF-8"?>
    <Delcampe_Notification>
    <Notification_Token></Notification_Token>
    <Notification_Datetime>2023-12-14 08:01:03</Notification_Datetime>
    <Notification_Data>
    <Headers>
    <Ressource>item/12785783</Ressource>
    <Action>GET</Action>
    <Status>200</Status>
    </Headers>
    <body>
    </body>
    </Notification_Data>
    </Delcampe_Notification>
    This problem has been fixed
  • klaus_schneider
    klaus_schneider 100% (84983x)
    PRO advanced

    289 mensajes

    Alemania

    Sorry, but I can't understand such decisions. A personal reference has nothing to do with sorting. Something is clearly being misused here due to a lack of options in the Delcampe article structure. The right way would be to introduce new fields. There is already a similar problem with the category numbers. Using different category numbers for different grades of the same item is simply insane. Just because other people do it that way doesn't mean it's right. What would be necessary for this is a field/fields in which the condition is stored, e.g. mint never hinged, used, new etc..., i.e. generally fields for product properties. Delcampe finally has to decide whether it wants to become a real marketplace in the future with a corresponding number of professional sellers or whether it wants to continue to be a playground for private sellers and pseudo-dealers.... and on this occasion we are still waiting for important things like the transmission of shipping information / Tracking data via API and please communicate to members that more or less automatic payment processing is now available. We answer this question dozens of times every week. After the purchase, the buyer still receives the information that the seller will contact him soon and all he has to do is click on “Pay”. How are we as sellers supposed to know when the customer has completed their purchase... these are the important things, finally functioning order processing. Kind regards
  • cartespostales_de
    cartespostales_de 100% (172010x)
    PRO premium

    69 mensajes

    Alemania

    This problem has been fixed
    Thanks a lot :cool2:

    Best regards and have some nice christmas days!
  • klaus_schneider
    klaus_schneider 100% (84983x)
    PRO advanced

    289 mensajes

    Alemania

    Hello, so far it doesn't work. The deletion calls are still acknowledged with an error message. Kind regards
  • klaus_schneider
    klaus_schneider 100% (84983x)
    PRO advanced

    289 mensajes

    Alemania

    Hello, the problem starts earlier because querying the article with the Personal Reference doesn't work. Nothing comes back and therefore no ItemID is available for deletion. Kind regards

Únese a la comunidad de coleccionistas

Inscripción Identificarse