Suche
Schließen
  1. Startseite
  2. Forum
  3. API users
  4. error on item Info by reference
Übersicht der Foren Alle Einträge

error on item Info by reference

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

    4 Beiträge

    Frankreich

    Hi,
    Since this morning i got error when i try to get item info by personal reference (success at 7h43, first error for me at 8h43) :


    Link (https)
    An error occurred
    401
    Unauthorized


    Something change for that call ?
    regards.
  • klaus_schneider
    klaus_schneider 100% (84918x)
    PRO advanced

    289 Beiträge

    Deutschland

    Hello, this function is very important, what are they tinkering with now? When will it work again? The whole order processing can't work properly again. When will this Delcampe API drama finally be over!!! Kind regards
  • @kevin
    Administrator
    @kevin

    102 Beiträge

    Belgien

    Hi numisaisne-soissons,

    Do you still get the error after retrieving a new token?

    If the problem persists, can you send us the personal reference you are having a problem with?

    Best regards,
    --
    Kevin
    Delcampe Team
  • numisaisne-soissons
    numisaisne-soissons 99% (5226x)
    PRO advanced

    4 Beiträge

    Frankreich

    it works now, thank you

    Yes this morning i try with a new token, may be an temporary overload on your api.
  • klaus_schneider
    klaus_schneider 100% (84918x)
    PRO advanced

    289 Beiträge

    Deutschland

    Currently not working again, since about 18h 19.06.2024
  • Servitel
    Servitel
    free

    448 Beiträge

    Schweiz

    Currently not working again, since about 18h 19.06.2024
    • Erstellt am 19.06.2024 um 16:52
    • #1761953
    Hi Klaus
    at my end the search by reference works fine.
  • klaus_schneider
    klaus_schneider 100% (84918x)
    PRO advanced

    289 Beiträge

    Deutschland

    Hello, yes it basically works. The problem lies in a chain of events. If an error message or e.g. Error 400 etc. is returned for a request or the subsequent action, but the operation was still carried out, e.g. the article was deleted but no success was returned. In this case, the job on the requester's side remains open, of course. So the operation is repeatedly attempted to be carried out again... It's a vale of tears...
  • Servitel
    Servitel
    free

    448 Beiträge

    Schweiz

    Hello, yes it basically works. The problem lies in a chain of events. If an error message or e.g. Error 400 etc. is returned for a request or the subsequent action, but the operation was still carried out, e.g. the article was deleted but no success was returned. In this case, the job on the requester's side remains open, of course. So the operation is repeatedly attempted to be carried out again... It's a vale of tears...
    • Erstellt am 21.06.2024 um 06:20
    • #1762559
    you are right
    I have implemented a check system that download the full list of items on D* and compare the result with the true list.
    Eventually the system delete again items not deleted

    Sometimes D* says "operation completed" but is not true. This happens sometimes when listing lots of items
  • klaus_schneider
    klaus_schneider 100% (84918x)
    PRO advanced

    289 Beiträge

    Deutschland

    at the moment it doesnt work, or response of delete is not true....
  • @lco
    Account geschlossen

    94 Beiträge

    Belgien

    at the moment it doesnt work, or response of delete is not true....
    • Erstellt am 25.06.2024 um 14:45
    • #1764018
    Hello,

    in order to investigate, can you provide me example of call that did not behave as expected?
    The object ID should be sufficient.

    Laurent.
  • klaus_schneider
    klaus_schneider 100% (84918x)
    PRO advanced

    289 Beiträge

    Deutschland

    Hello, I can't give you an ItemID. Delcampe quickly set up the emails for it. This email was the only link between our personal reference and the Delcampe ItemID! Such changes should be announced a few weeks in advance, as is usual elsewhere. Then there will be a response. How would Delcampe know how things that have been around for years are used in the field!!! On June 25, 2024 at 8:18 p.m., for example, the following personal reference "B190039CBF5-S3E80AER" was supposed to be deleted. The delete/close ended with an error message. In this case, that might mean a 400xx or whatever, so in any case not the defined XML response from CloseItem. To see exactly that, the log level would have to be increased first. The article was deleted anyway, which means that the process remains open here. As a result, this of course means that GetItemByReference no longer works because the article has been deleted in the meantime. The problem lies with CloseItem, or rather the general problem that with various functions it keeps happening that the expected XML container is not returned as a response, but rather some nonsense. Best regards
  • @lco
    Account geschlossen

    94 Beiträge

    Belgien

    We had to do a quick move on banning the start/close emails, because the imact was huge for a lot of users. Check this french thread for example: Link (https)

    Now we're planning to set those notification back, but it will be a daily digest of the new, renewed and closed sales.

    This is the API forum, go the API way to manage a big business. Our API calls have reliability mechanisms (Dead letter queue: Link (https)

    Laurent.
  • klaus_schneider
    klaus_schneider 100% (84918x)
    PRO advanced

    289 Beiträge

    Deutschland

    Hello, we have been working at Delcampe for over 15 years and have been using the API from the start. So we know what we're talking about. The problem is not that something changes, it's the method. Quick Move is a good example of this. I miss the plan at Delcampe and informing those involved at the right time. There are always three parties: Delcampe, the buyers and the sellers, and we always need a win-win-win situation. In the last few months it has unfortunately been a lose-lose-lose situation, or at least a frustrate, frustrate, frustrate situation. We have now switched this to callbacks, so from our point of view there is currently no need for action. Now to the actual topic of this thread. The problem with ItemClose has disappeared since today, yesterday it didn't work. From this I can only conclude that the correct XML response is now being returned again. We had just increased the log level and will leave it like this for a few days. But I have more examples on the topic of plans. If I find the time, I'll post it in the forum at the weekend. Regards
  • richnoddystamps
    Account geschlossen
    PRO free

    232 Beiträge

    Vereinigtes Königreich

    Am I right thinking that something has changed on "To Be Shipped"? It is now much more time consuming to pick and pack sale items as the "Personal Reference" no longer appears on the To be shipped list. This is incredibly frustrating and means that each item link has to be opened to find the personal reference number.

    Is it possible to default this list to show Personal reference numbers on the list?

    Also, is anyone else experiencing really sloppy and slow service on the API forum. One of the calls on my API system is not working so is not reporting sales back to my own website, again causing significant extra work. I am expecting to be charged €20 for this service so I would image I will be getting a €0.66 discount for every day the service is not working.

    I also messages Miranda about a week ago and had received no reply.

Werden Sie Mitglied der Sammler-Community!

Anmelden Einloggen