Playbooks · Recipe
Search live LinkedIn job posts, roll them up to companies, pull the people who own the budget, then find and verify their emails. Four calls. The finder and verifier are waterfall endpoints, so a miss on those two costs zero; the searches bill per result returned.
Last updated September 22, 2026
Pattern: job search → company roll-up → employee search → email finder → email verifier
Credit math: Worked example at stated counts: 100 job results at 0.1 = 10 credits. Roll up to 40 companies, 5 people each = 200 employee results at 0.1 = 20 credits. 200 finder calls at 5 = up to 1,000 credits, less every miss, which bills zero. Verify the 120 hits at 2 = 240 credits. 0.1 credits per result on linkedin_job_search and linkedin_company_employees_search, 5 credits per email_finder call, 2 credits per email_verifier call
ROI math: Cost lands on verified contacts, not on rows attempted, because the two expensive steps are both waterfall. Multiply the credit total by your tier rate on /pricing — the rate varies by package and there is no single number.
Owned internally by: GTM engineer or RevOps, running it on a schedule they own
Best for: Anyone selling into teams while they staff up: recruiting tools, dev tools, sales enablement, agencies retained on headcount growth
curl -X POST https://api.richapi.ai/api/v1/linkedin_job_search \
-H "x-api-key: $RICHAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"keywords": "revenue operations", "location": "United States", "datePosted": "past-week"}'
Search LinkedIn jobs for "revenue operations" posted in the past week in the US.
Group the results by company. For the ten companies with the most open roles,
find the VP of Sales or Head of RevOps, get their work email, and verify it.
Show me which providers ran on each email.
A company posting four RevOps roles is telling you something real: a team is being built, a budget was approved, and somebody now owns a problem they did not own last quarter. That is worth acting on. It is not intent. Intent data means someone watched a demo of a product like yours, and we do not sell that — [we have no intent feed](/platform) and we are not going to imply one. What you get here is a public, timestamped, checkable fact about staffing. Half the value is that it is checkable: you can open the job post in the email you send. Treat it accordingly. A hiring post earns you a relevant first line, not an assumption that they are in a buying cycle. **[Get 25 free credits — no card](https://app.richapi.ai)**
Four calls, in order, each one narrowing the last. `linkedin_job_search` finds live posts by keyword, location and recency. It bills per result returned, so a wide query is a real cost decision — not a free browse. Roll the results up to companies. This step is yours, in code, and it is the step people skip. A company posting six roles arrives as six rows and must become one account before you spend another credit on it. `linkedin_company_employees_search` returns people at each surviving company. Also per-result. Search for the titles that sign, not the titles being hired — the person hiring three SDRs is a VP of Sales, and the SDR they hire in five weeks is not your buyer. `email_finder` then `email_verifier` turn names into addresses you can send to. Both are waterfall endpoints. Providers run cheapest-first, and a 2xx carrying `success: false` comes back with `billed: false` and costs zero. That is where the money in this recipe is protected, because that is where the misses happen.
Per-result endpoints have no meaningful cost without a result count, so here is one run with the counts written down. | Step | Count | Rate | Credits | |---|---|---|---| | `linkedin_job_search` | 100 results | 0.1 / result | 10 | | `linkedin_company_employees_search` | 40 companies × 5 = 200 results | 0.1 / result | 20 | | `email_finder` | 200 calls, 120 hits | 5 / call, misses free | 600 | | `email_verifier` | 120 calls | 2 / call | 240 | Rates used above: 0.1 credits per result on `linkedin_job_search` and `linkedin_company_employees_search`, 5 credits per `email_finder` call, 2 credits per `email_verifier` call. The 80 finder misses in that run cost zero. On a non-waterfall endpoint they would have cost 400 credits for nothing. Per-credit rates differ by package tier, so convert on [the pricing page](/pricing) rather than assuming one rate, or model the whole chain in [the waterfall cost calculator](/tools/waterfall-cost-calculator).
**Stale and evergreen posts.** Plenty of companies leave a req open for months, or run a permanent "always hiring engineers" listing. Filter hard on recency at the search step and re-check the post before it appears in a message, because "I saw you're hiring a Head of RevOps" reads badly when the role was filled in March. **Agency and staffing-firm posts.** A recruiting agency posts on behalf of a client. You enrich the agency, mail the agency, and learn nothing. Drop companies whose posting volume looks like a staffing business. **Titles from the post, not the org.** Searching for the title being hired gets you the future employee. Search for the person who approved the req. **The quiet one: query width.** `linkedin_job_search` bills per result. A vague keyword across three countries returns a large, expensive, mostly irrelevant page. Narrow the query before you widen it.
If your qualifier is what a company *runs* rather than who it is *hiring*, [tech stack qualification](/use-cases/tech-stack-intent-outbound) is the cheaper first filter — one flat call per domain instead of per-result search. If you already have the account list and only need contacts, skip straight to [list build and verify](/use-cases/list-build-and-verify). If you want an agent to run the whole thing conversationally, see [agent-driven account research](/use-cases/agent-driven-account-research) and the broader [signal-based prospecting](/use-cases/signal-based-prospecting) pattern. Everything else we have written up lives on [the use-case index](/use-cases).
**Does a hiring post mean they are ready to buy?** No. It means they are staffing. We do not sell intent data and this page is not an intent claim. The post gives you a true, dated, verifiable reason to reach out — use it as that. **What exactly is free when the chain misses?** Only `email_finder` and `email_verifier`, both waterfall. A waterfall 2xx with `success: false` carries `billed: false` and costs zero. The two search calls bill per result returned, and everything else in the catalog bills on any 2xx including an empty one. **How many people should I pull per company?** Three to five titles. Employee search bills per result, so pulling twenty people at a forty-person company is how you turn a 20-credit step into a 100-credit one with no extra meetings. **Can I run it on a schedule?** Yes, and the schedule is yours. We have no alerting product and no saved-search product. This is a cron job you own, hitting the same four endpoints weekly and diffing against what you already stored. **Do I need a credit card?** No. 25 free credits on signup.
Run the job search, look at what comes back, and decide if the signal is worth your outbound. **[Get 25 free credits](https://app.richapi.ai)**