Need help and/or support getting News Headline data returned from the Lookup port please.

I am able to successfully get the News Config data from: NCG,[XML/Text],[RequestID]
Which returns data like this:
[...]
'MINOR', 'DT7', 'Quote List Changes', '1D', '10'
'MINOR', 'RTI', 'Calendars and Reports', '2Ab', '10'
'MAJOR', 'CPR', 'PR Newswire', '1X', '5'
'MAJOR', 'CBW', 'Business Wire', '1X', '2'
'MAJOR', 'RTT', 'Real-Time Trader', '2Ab', '10'
'MINOR', 'RTB', 'Breaking News Headlines', '2Ab', '10'
'MINOR', 'RTC', 'Big Stories', '2Ab', '10'
'MINOR', 'RTD', 'Analyst Updates', '2Ab', '10'
'MINOR', 'RTE', 'Analyst Comments', '2Ab', '10'
'MINOR', 'RTF', 'Stocks on the Move', '2Ab', '10'
'MINOR', 'RTG', 'Corporate Actions', '2Ab', '10'
'MINOR', 'RTH', 'Market Overview', '2Ab', '10'
'MINOR', 'RTK', 'Economic News', '2Ab', '10'
[...]


Ok that's a great start, but can't seem to get any further -- when ever I try to send an NHL request to get headlines it just doesn't seem to work.

I followed the API guidelines here:
http://www.iqfeed.net/dev/api/docs/NewsLookupviaTCPIP.cfm

Following the guidelines:
NHL,[Sources],[Symbols],[XML/Text],[Limit],[Date],[RequestID]
Here's an couple examples I tried:

NHL,,,,,,
NHL,,TSLA,x,,,
NHL,AP:DTN:MW,TSLA,x,,,

I've tried passing in News Sources (or not), TICKER symbols (or not), passing in 't' for text or 'x' for XML... and also tried not passing in anything hoping it would return all the news, but, to my dismay, no matter what I try, it seems I get the same result... an empty array ['] or an empty XML shell:

<?xml version='1.0'?> <news_headlines> </news_headlines>

Getting News Headlines to come back from the servers seems to be an elusive mystery.

I'm sure I must be missing a step or doing something wrong? Please help! Thanks in advance.

-e


Edited by etron on Aug 31, 2016 at 08:44 PM

Hey guys, Thanks for your help and prompt response via the developer support channel. For posterity here is what support told me:



After seeing this reply that it works on that end, and inspecting my code closer, to my embarrassment, there was an extra ascii character getting inserted into every request after the comma which was causing requests to get sent wrong. Somehow I completely missed this as I was printing the command for debugging before this character was getting inserted!

Thanks for your quick response and help via developer support.

-e

Edited by etron on Sep 1, 2016 at 05:29 PM