Aller au contenu
Toutes les missions
Veille marché · Dev-to Nouvelle Publiée il y a 6 heures

SmartRecruiters' Posting API has a pay field after all: a correction, and four more things from 903 boards

In October we wrote up the basics of SmartRecruiters' public Posting API: the two calls, the page size, the location fields. One sentence in it was wrong. We wrote that the API has no pay fi...

Mode October we wrote up

Résumé

In October we wrote up the basics of SmartRecruiters' public Posting API: the two calls, the page size, the location fields. One sentence in it was wrong. We wrote that the API has no pay field. It has one. We missed it because it is not in the list call and most job records do not carry it. This post corrects that, and adds four things we learned since from building a search across companies. Everything up to the last section was measured on 12 November 2026: on the job lists of Sixt (552 postings), ServiceNow (788) and Wise (442) read live, on 25 job records from each, on the newest job of 129 boards, and on our daily index of 199,259 SmartRecruiters jobs on 903 boards. SmartRecruiters documents the Posting API as access to job postings a company has made public, and it answers without a key. We read it at one request a second for this post. Where the pay is https://api.smartrecruiters.com/v1/companies/<board>/postings/<id> The list call (/postings?limit=100&offset=0) returns no pay and no job text. Both are on the job's own record, above, so pay costs one request per job. 1. There is a compensation object, and most employers leave it out When an employer fills in the pay on a posting, the job record carries this: { "min": 80000, "max": 110000, "currency": "USD", "period": "YEARLY" } It is there on a minority of jobs. We took every seventh board of the 903 and read its newest job: 24 of the 129 records carry compensation. Whether it is filled depends on the employer far more than on the job: of 25 jobs read from each of three large boards, 23 of Wise's carry it and none of ServiceNow's or Sixt's do. ServiceNow states pay in a sentence of the job text instead. The object is not always the four keys above. Of the 24: 13 have all four keys. 8 have no min key at all, 2 have no max, and 1 has no period. 3 hold a 0 at the only end they give, which means the field was left empty, not that the job is unpaid. period was YEARLY on 10, MONTHLY on 7 and HOURLY on 6. We also met DAILY on other boards. The currencies were US dollars (9), euros (9), Canadian dollars (3), pounds (2) and dirhams (1). So treat a missing key and a 0 as "not stated", accept a range with one end, and always read the period: 13 of these 24 are monthly or hourly figures. Check the size against the period too. One record gave 3.8 euros a month, and in our runs a full-time job in France came back as 10,000 to 12,000 euros a year. The field does not say whether a figure is base pay or total pay. Reading the field as well as the text matters. On those 129 records, a careful reading of the job text alone found a pay range on 12; with the field it was 28. In a search for data jobs across all boards, the first 100 results went from 3 with a pay range to 18, and of the 500 newest jobs in the index, from 63 to 148. 2. releasedDate moves, and the list is sorted by it The list comes back newest first by releasedDate, and it is the only date on a posting. It is not the date the job first appeared. Of Sixt's 552 postings, 490 were dated within the last seven days, 243 of them on 6 November and 140 on 5 November. Sixt did not open 383 jobs in two days: our index holds 385 Sixt jobs dated 5 or 6 November, and it had already listed 357 of them before 5 November, 330 of them since 29 October. The date moved after we first saw the posting. It is common. Across the index, 23,077 of the 199,259 jobs, on 444 of the 903 boards, carry a releasedDate later than the day we first listed them, 15,429 of them by more than a week. A filter such as "posted in the last 7 days" built on releasedDate therefore returns re-released postings as new. If you need "new", keep your own record of when you first saw each posting id. 3. One job can be several postings A posting is not a job opening. Each has a refNumber, the employer's requisition number, and one requisition can be published several times. Sixt's 552 postings carry 453 different refNumber values, ServiceNow's 788 carry 705 and Wise's 442 carry 418. The usual cause is location: one posting per city. All 52 of ServiceNow's requisitions with more than one posting span more than one city, and so do 33 of Sixt's 55. In our search for data jobs, four consecutive results were one requisition at one pharmaceutical company, the same title and the same pay range, published separately for four US cities. Language is a rarer cause: Sixt publishes under seven language codes (268 postings in German, 177 in English, 58 in Spanish), but only 2 of its 55 repeated requisitions come in more than one language. The flag defaultJobAd helps. No requisition on the three boards has more than one posting with it set, so keeping only those gives one posting per requisition: for all 705 of ServiceNow's, for 450 of Sixt's 453 and for 398 of Wise's 418 (the other 20 have none set). Counting postings overstates openings, then. Group by company and refNumber when you count. 4. The job text is four sections, and the list is mostly the employer's own fields The job text is in jobAd.sections: companyDescription, jobDescription, qualifications and additionalInformation. Employers use them differently. On 25 ServiceNow jobs the text averaged about 6,400 characters, split 12%, 33%, 27% and 28% across the four. On 25 Sixt jobs it averaged about 3,800 characters with 78% in jobDescription, and qualifications was empty on all 25. Across the 129 newest jobs, jobDescription was filled on every one, qualifications on 115 and additionalInformation on 116. Read only jobDescription and you lose two thirds of a ServiceNow job, pay included: the 11 of those 25 jobs that mention a currency do so in qualifications, none in jobDescription. Join all four. The list has the opposite problem. Each list item carries customField, an array of the employer's own fields: labels such as "Cost Center", "Legal Entity", "Recruiting Team" and "Worker Sub Type". It is 34% of the bytes of Sixt's list, 55% of ServiceNow's and 69% of Wise's, where an average list item is 3,042 bytes. Nothing in it is standard from one board to the next, so skip it unless you know the board. 5. There is no directory of boards, and a few boards hold most of the jobs The API answers for a board you name and does not say which boards exist; a name that does not exist returns an empty list, not an error. To search across companies you need the list of boards first. We built ours from public web data, the Common Crawl URL index, and confirmed each candidate by reading its board. The boards are very uneven. Half of our 903 list 27 jobs or fewer. Four boards hold 48,842 of the 199,259 jobs, and 35 boards with more than 1,000 jobs each hold 116,690. One pizza chain alone lists 24,969 jobs and accounts for 13,635 of the 34,949 jobs dated in the seven days before our refresh. A search across SmartRecruiters without a cap per company is mostly a search of those few boards. The tool SmartRecruiters Jobs API on Apify Store does the above for every board at once: a daily index of 198,086 open jobs on 901 SmartRecruiters boards (18 November 2026), searched by title, place, workplace type, employment type, pay and date, with a cap per company, and the full text and the pay read live from each job's own record at search time. The search it opens with (data analyst, data scientist, data engineer) returned, on 18 November, 100 of 1,059 matching jobs, newest first with at most 5 per company, from 54 companies in 26 seconds on Apify, 20 of them with a pay range. $2.50 per 1,000 jobs. For one company's board read live from its URL, our SmartRecruiters Jobs Scraper returns the same 30 fields, so both drop into one table with the other systems Dodo Data reads. It reads pay from the job text only for now; the pay field is next.