<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Noble Ronin</title>
    <description>The latest articles on DEV Community by Noble Ronin (@ronin13).</description>
    <link>https://dev.to/ronin13</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4027486%2F6ad6877d-ae73-4dab-8cfd-d6f408944c56.png</url>
      <title>DEV Community: Noble Ronin</title>
      <link>https://dev.to/ronin13</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ronin13"/>
    <language>en</language>
    <item>
      <title>Skip LinkedIn/Indeed: most companies' job boards have a public JSON API</title>
      <dc:creator>Noble Ronin</dc:creator>
      <pubDate>Mon, 13 Jul 2026 15:33:36 +0000</pubDate>
      <link>https://dev.to/ronin13/skip-linkedinindeed-most-companies-job-boards-have-a-public-json-api-48b</link>
      <guid>https://dev.to/ronin13/skip-linkedinindeed-most-companies-job-boards-have-a-public-json-api-48b</guid>
      <description>&lt;p&gt;If you've ever tried to pull job listings by scraping LinkedIn or Indeed, you know the pain: anti-bot systems, CAPTCHAs, rotating proxies, and scripts that silently break every few weeks.&lt;/p&gt;

&lt;p&gt;Here's the thing — you usually don't need any of that.&lt;/p&gt;

&lt;p&gt;Companies don't post jobs on LinkedIn first. They post them in their &lt;strong&gt;ATS&lt;/strong&gt; (Applicant Tracking System) — Greenhouse, Lever, Ashby, Workday, etc. — and most ATS platforms expose the company's board as a &lt;strong&gt;public JSON endpoint&lt;/strong&gt;. No key, no login, no browser. It's the company's own source of truth, so it's cleaner and fresher than any aggregator.&lt;/p&gt;

&lt;h2&gt;
  
  
  The endpoints
&lt;/h2&gt;

&lt;p&gt;A few that work with a plain GET (&lt;code&gt;{company}&lt;/code&gt; = the company's slug):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Greenhouse&lt;/strong&gt; — &lt;code&gt;https://boards-api.greenhouse.io/v1/boards/{company}/jobs?content=true&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lever&lt;/strong&gt; — &lt;code&gt;https://api.lever.co/v0/postings/{company}?mode=json&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recruitee&lt;/strong&gt; — &lt;code&gt;https://{company}.recruitee.com/api/offers/&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Breezy HR&lt;/strong&gt; — &lt;code&gt;https://{company}.breezy.hr/json&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;SmartRecruiters, Ashby, BambooHR and Personio have their own equivalents. Workday is the one annoying exception — it's a POST and needs the full board URL (tenant + datacenter + site), so you can't guess it from a bare company name.&lt;/p&gt;

&lt;h2&gt;
  
  
  Example: pulling Stripe's open roles (Python)
&lt;/h2&gt;

&lt;p&gt;Stripe uses Greenhouse:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;requests&lt;/span&gt;

&lt;span class="n"&gt;company&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;stripe&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
&lt;span class="n"&gt;url&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;https://boards-api.greenhouse.io/v1/boards/&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;company&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;/jobs?content=true&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
&lt;span class="n"&gt;jobs&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;requests&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;()[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;jobs&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;j&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;jobs&lt;/span&gt;&lt;span class="p"&gt;[:&lt;/span&gt;&lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;]:&lt;/span&gt;
    &lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;j&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;title&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;—&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;j&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;location&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;][&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;name&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;])&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's it. No Selenium, no proxy, no CAPTCHA solver. Runs in ~200ms and won't break next Tuesday because Cloudflare changed something.&lt;/p&gt;

&lt;h2&gt;
  
  
  Auto-detecting the ATS
&lt;/h2&gt;

&lt;p&gt;If you don't know which ATS a company uses, just try them in order and take the first one that returns jobs. A bare &lt;code&gt;404&lt;/code&gt; means "not this ATS, try the next." Greenhouse → Lever → Ashby → SmartRecruiters → Recruitee → Breezy covers a huge chunk of tech companies.&lt;/p&gt;

&lt;h2&gt;
  
  
  Gotchas
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Rate limits&lt;/strong&gt; are lenient but real — be polite, set a &lt;code&gt;User-Agent&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Descriptions&lt;/strong&gt;: Greenhouse/Lever include full HTML descriptions in the list; Breezy's list endpoint doesn't (you'd fetch each posting for that).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Workday&lt;/strong&gt;: POST-only, needs the full board URL — worth special-casing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  If you don't want to build/maintain 9 of these
&lt;/h2&gt;

&lt;p&gt;I got tired of keeping a fetcher per ATS in sync, so I bundled 9 of them (Greenhouse, Lever, Ashby, SmartRecruiters, Workday, BambooHR, Personio, Recruitee, Breezy) into one thing that auto-detects the ATS from a bare company name or board URL and returns normalized jobs: &lt;strong&gt;&lt;a href="https://apify.com/ponderable_hydrometer/multi-ats-jobs" rel="noopener noreferrer"&gt;https://apify.com/ponderable_hydrometer/multi-ats-jobs&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;But honestly, the endpoints above are the real value — build your own if you'd rather.&lt;/p&gt;

&lt;p&gt;Which ATS should I add next? Considering Workable, Teamtailor and JazzHR.&lt;/p&gt;

</description>
      <category>webscraping</category>
      <category>python</category>
      <category>api</category>
      <category>jobs</category>
    </item>
  </channel>
</rss>
