POST data empty in notifications

  • stamps_auction

    6 messages

    Royaume-Uni

    Hello,
    I set up notifications, but the notifications send empty POST data, only the GET data (the token) is sent. Any clues what the problem is?
    Thanks

    PS: On this page, at the bottom is a "send us an email" link: Lien (https)
    ( support_api@delcampe.com ), but this email bounced back.
  • @lco
    Compte fermé

    94 messages

    Belgique

    Hello,
    I set up notifications, but the notifications send empty POST data, only the GET data (the token) is sent. Any clues what the problem is?
    Thanks

    PS: On this page, at the bottom is a "send us an email" link: Lien (https)
    ( support_api@delcampe.com ), but this email bounced back.
    • Posté le 9 juil. 2025 à 08:01
    • #1919599
    Hello stamps_auction,

    You're right for this support_api@delcampe.com : it was missing after a system migration; thank you for reporting.

    I can see on our side that your server replies with 500 status / "Internal server error".
    We have a new endpoint (still undocumented) that allows you to investigate how we see your response to our callbacks, from Delcampe servers point of view.

    Call this API endpoint with your session token (i removed the host part to avoid the automatic rewriting of the link):

    /notification/logs?token=your_token

    You can also filter on date and errors using the query string parameters as in this example:

    /notification/logs?from=2025-07-09&to=2025-07-10&errorsOnly=1&token=your_token

    You'll get an XML representation of our callback logs, I hope this will help you debugging this issue.

    Laurent.
  • stamps_auction

    6 messages

    Royaume-Uni

    OK hope the broken email is now working.

    As for the 500 status / "Internal server error", that was already fixed a few days ago, but still no POST data. Is there also a log where I can see the xml sent to my endpoint?
  • @fred
    Administrateur

    144 messages

    Belgique

    OK hope the broken email is now working.

    As for the 500 status / "Internal server error", that was already fixed a few days ago, but still no POST data. Is there also a log where I can see the xml sent to my endpoint?
    • Posté le 10 juil. 2025 à 08:16
    • #1919839
    Hi stamps_auction,

    It looks like you have a configuration error on your webserver. When we investigate our logs, we see that our initial callback is a POST but your webserver served us a 301 response and rewrote it as a GET

    08:48:51 POST Lien (http) 301
    08:48:52 GET Lien (https) 200

    We will change our code to handle the redirects more strictly (if the original request was a POST, the following redirects will be POST as well) but you have to change your nginx/apache vhost to prevent this 301 redirection

    Fred
  • stamps_auction

    6 messages

    Royaume-Uni

    Thanks. That fixed the problem. Sorry my mistake. Maybe before the system accepts a new notification URL it can check if there's a redirect or not. If yes refuse to add the notification and tell us why. Would have saved me a few hours of finding the problem. Just an idea, not sure how easy it is to implement.

Rejoignez la communauté des collectionneurs !

S'inscrire Se connecter