ad: UR5CDX-1

Querying API for /P callsigns broken

Discussion in 'QRZ XML Logbook Data' started by DF2ET, Jan 6, 2024.

ad: L-HROutlet
ad: l-rl
ad: Left-3
ad: abrind-2
ad: L-MFJ
ad: Left-2
ad: Radclub22-2
  1. DF2ET

    DF2ET XML Subscriber QRZ Page

    Dear qrz.com team,

    the XML API obviously has an issue with queries for compound callsings like DF2ET/P. Using the query: http://xmldata.qrz.com/xml/current/?s=SESSIONKEY;callsign=DF2ET/P results in an answer:

    <QRZDatabase version="1.36">
    <Session>
    <Error>Not found: P</Error>
    <Key>SESSIONKEY</Key>
    <Count>27132</Count>
    <SubExp>Sat Apr 27 16:29:45 2024</SubExp>
    <GMTime>Sat Jan 6 06:43:35 2024</GMTime>
    <Remark>cpu: 0.024s</Remark>
    </Session>
    </QRZDatabase>

    Also using _ or %2F for the forward slash does not work. Could you please fix this issue?

    vy73 de Florian DF2ET
     
  2. K8VHL

    K8VHL Platinum Subscriber Volunteer Moderator Platinum Subscriber QRZ Page

    I am unable to find a QRZ callsign account for DF2ET/P. Have you established one such as you did for SM/DF2ET?
     
  3. DF2ET

    DF2ET XML Subscriber QRZ Page

    This was just ment to be an example. It seems to affect callsign which contain a forward slash. See the error message:

    <Error>Not found: P</Error>

    It seems to search for P indtead of DF2ET/P regardless of if there is an account for it or not.
     

Share This Page

ad: ProAudio-1