Zoekopdracht
Afsluiten
  1. Startpagina
  2. Forum
  3. API users
  4. Street and number (continued) missing in notifications
Forumslijst Berichten lijst

Street and number (continued) missing in notifications

  • fnwbr
    Rekening afgesloten

    34 berichten

    Duitsland

    For `Seller_Item_Close_Sold` notifications we're not receiving data that a Delcampe user might have typed into the "Street and number (continued)" inputs.

    When calling the `item/1234/buyer` API endpoint to double-check the data we can see that it's being concatenated to the `buyer_address` field, however, this does not happen with the payload of `Seller_Item_Close_Sold` notifications.

    Can you please fix this and send the whole address (including the data from the "(continued)" input) with the notification payload in first place?
  • Rekening verwijderd
    Beheerder
    Rekening verwijderd

    0 berichten

    België

    De informatie is niet meer beschikbaar omdat de rekening van deze gebruiker is verwijderd (AVG)
  • fnwbr
    Rekening afgesloten

    34 berichten

    Duitsland

    Example buyer ID: 1295112
    Example item ID that was sold: 576275055

    The `buyer_address` field did only contain the first half of the address because the user split up their address between the "Street and number" and the "Street and number (continued)" inputs.

    Again, this information is only missing on the notification payload, but not when manually calling `item/576275055/buyer` on the REST API.
  • Rekening verwijderd
    Beheerder
    Rekening verwijderd

    0 berichten

    België

    De informatie is niet meer beschikbaar omdat de rekening van deze gebruiker is verwijderd (AVG)
  • fnwbr
    Rekening afgesloten

    34 berichten

    Duitsland

    Sorry, just to clarify: You're saying you are aware that this is a bug but you're not fixing it because I'm the only one who pointed it out?

    We are an agency in Germany, taking care of about 10 Delcampe users, and at least 3 of those have pointed this out in the past. It took me a while to figure out what the actual issue was.

    Or asked in a different way: Why do you want to keep this inconsistent behavior of your API when comparing the notification payload vs. the response data when calling the `item/1234/buyer` API endpoint?

    Can you at least put this on a todo list for future bug fixes or so?
  • sammlerkalle
    Rekening afgesloten
    PRO free

    881 berichten

    Duitsland

    The street number is not sent, when there is a linebreak between the streetname and the number. The normal mail will sent the complete data and the notification cuts the line after the streetname. I had the same problem a short time ago. item #508618016 - This is an bug by Delcampe and should be solved.
  • Rekening verwijderd
    Beheerder
    Rekening verwijderd

    0 berichten

    België

    De informatie is niet meer beschikbaar omdat de rekening van deze gebruiker is verwijderd (AVG)
  • fnwbr
    Rekening afgesloten

    34 berichten

    Duitsland

    :veryhappy:

    Thanks a ton!
  • Rekening verwijderd
    Beheerder
    Rekening verwijderd

    0 berichten

    België

    De informatie is niet meer beschikbaar omdat de rekening van deze gebruiker is verwijderd (AVG)

Word lid van de verzamelaars-community!

Registreren Aanmelden