The apigetjobs endpoint always returns a blank results table. I ensured the URL parameters were formatted correctly, in accordance with the IndeedClient implementation. On top of that, I tried both xml and json output formats, and even multiple publisher tokens. Given how recently this repo was last 'updated' I'd assume apigetjobs isn't officially deprecated.
Examples (using cURL)
$ curl "http://api.indeed.com/ads/apigetjobs?publisher=7863709885041358&v=2&format=json&jobkeys=5898e9d8f5c0593f,c2c41f024581e
ae5"
{"version":2,"results":[]}
$ curl "http://api.indeed.com/ads/apigetjobs?publisher=1637952116847595&jobkeys=5e50b56a7e69073c&v=2&format=json"
{"version":2,"results":[]}
$ curl "https://api.indeed.com/ads/apigetjobs?publisher=1637952116847595&jobkeys=5e50b56a7e69073c&v=2"
<?xml version='1.0' encoding='UTF-8'?><response version="2"><results/></response>
The
apigetjobsendpoint always returns a blankresultstable. I ensured the URL parameters were formatted correctly, in accordance with theIndeedClientimplementation. On top of that, I tried bothxmlandjsonoutput formats, and even multiplepublishertokens. Given how recently this repo was last 'updated' I'd assumeapigetjobsisn't officially deprecated.Examples (using cURL)