Clay Hiring Intent Signals: Enrich Open ATS Jobs by Domain
Clay's HTTP API column is configured field-by-field—not by importing JSON. Customize your Clay column tokens below, copy each exact field in 1 click, and enrich target domains across 434 ATS portals from $0.20/1K ($0.0002~$0.00076/call) with 0 Credits charged when an account has 0 matching jobs.
Interactive Clay HTTP API Column Builder
Configure your Clay variables & copy each field in 1 click
Method
GETEndpoint URL
https://api.jobpostingsapi.com/v1/jobs/search?company={{domain}}&limit=5Headers
Authorization: Bearer YOUR_API_KEYRun Condition ('Only run if')
Boolean({{domain}}) && !{{hiring_signal_checked}}Clay Output Column Extraction Paths (Click to Copy JSON Path)
Clay Enrichment Cost Savings Calculator
Clay Native Credits vs. JobPostings API (From $0.20/1K)
1 Credit = 1 returned job · 0 Credits on 0-match domains
Save 99.6% vs. native waterfall credits (6,500 empty lookups billed at $0.00).
Claim 1,500 Free Credits ($1.50) — Test in Clay Now →Engineering Highlights & Credit Safeguards
- →Zero Clay markup credits: Clay's native 'HTTP API' action calls https://api.jobpostingsapi.com directly using your own API key at 0 Clay credits.
- →Transparent volume unit economics: 1 Credit per returned job record—from $0.20/1K on Business Scale ($199/mo, $0.199/1K = $0.000199/job) to $0.76/1K on Starter ($19/mo) or $0.83/1K on non-expiring $25 PAYG.
- →Zero waste on non-hiring ICP accounts: whenever a target domain has 0 matching open roles, GET /v1/jobs/search and GET /v1/companies/{slug}/job-count charge strictly 0 Credits.
- →Every matched record returns department (team), source.name (ATS vendor), salary.annual_usd_max, extracted skills[], company.is_staffing_agency, and direct apply_url.
1. Clay Native Job Waterfall vs. JobPostings API HTTP Column
GTM engineers enriching 10,000+ target accounts per month in Clay often spend $300–$1,200/month on native job-lookup credits alone. Routing hiring-intent checks through a direct HTTP API column cuts per-account enrichment cost by over 95%:
| Evaluation Dimension | JobPostings API (Clay HTTP Column) | Clay Native Find Jobs Action | Legacy Intent Platforms |
|---|---|---|---|
| Effective Unit Rate | From $0.20/1K ($0.0002~$0.00076/job · $0.83/1K on $25 PAYG) | 2–4 Clay credits/row (~$0.14–$0.28/row on standard plans) | $500–$1,500+/mo annual seat contract |
| Cost When 0 Jobs Match | $0.00 (strictly 0 Credits deducted) | Varies by provider waterfall step | Fixed sunk monthly contract |
| Headcount-Only Summary Option | 1 Credit flat via GET /v1/companies/{slug}/job-count (<15 ms) | Requires fetching full job list rows | Separate company-enrichment SKU |
| Direct Employer ATS Coverage | 434 ATS & career portals (Greenhouse, Lever, Ashby, Workday, iCIMS) | Primarily social/aggregator snapshots | 150–250 sources (daily/weekly batch) |
| Pre-Parsed Skills & USD Salary | Included in data[0].skills & data[0].salary.annual_usd_max | Requires extra Claygent / LLM tokens to parse JD | Paid technographic add-on |
2. Live Response Payload & Clay Dot-Path Output Mapping
Once your Clay HTTP API column runs against a target domain such as stripe.com, click any cell response in Clay and click 'Add as column' on these exact JSON paths:
Captured Production 200 OK Payload (GET /v1/jobs/search?company=stripe.com&limit=2)
{
"code": 0,
"provider": "https://jobpostingsapi.com",
"status": "ok",
"msg": "success",
"data": [
{
"id": "j_gh_stripe_5601881",
"data_tier": "premium",
"status": "active",
"title": "Data Analyst",
"company": {
"id": "c_stripe",
"name": "Stripe",
"slug": "stripe",
"domain": "stripe.com",
"is_staffing_agency": false,
"industry": null
},
"department": "7112 Data Science",
"location": {
"raw": "US",
"city": null,
"region": null,
"country": "US"
},
"work_arrangement": "onsite",
"employment_type": "full_time",
"skills": ["sql", "python", "experimentation"],
"salary": null,
"apply_url": "https://stripe.com/jobs/search?gh_jid=5601881",
"link_type": "direct",
"source": {
"name": "greenhouse",
"display_name": "Greenhouse",
"type": "ats",
"board": "stripe",
"job_id": "5601881"
},
"posted_at": "2026-11-13T22:08:50.000Z"
}
],
"meta": {
"request_id": "fed62adc-7aca-4fe5-9abf-d50455df881f",
"count": 1,
"total": 1130,
"total_relation": "eq",
"has_more": true,
"took_ms": 14
}
}- Gate Sequence Enrollment on Direct Employer Roles: Add a Clay formula filter checking data[0].company.is_staffing_agency === false so your SDR sequence never triggers on third-party recruiting agency listings.
- Use /job-count First for Ultra-Large TAM Lists (50K+ Domains): Enriching 50,000 domains? Run GET /v1/companies/{{domain}}/job-count first (1 Credit = $0.0002 on Scale when open_jobs > 0, and 0 Credits when open_jobs = 0) to get open_jobs, open_jobs_growth.posted_last_30d, and open_jobs_by_department before fetching full job descriptions.
- Need Scheduled Cron Alerts Instead of Static Tables?: Pair Clay account enrichment with our hourly n8n ATS job feed workflow (/integrations/n8n-ats-job-feed-automation) to push newly opened requisitions straight into Clay webhooks or Slack.
Frequently Asked Questions
- Does Clay charge Clay credits when I use the HTTP API column with JobPostings API?
- No. Clay's HTTP API integration uses your own external API key at 0 Clay credits. You only consume JobPostings API credits—1 Credit per returned job ($0.199/1K on Scale $199/mo, $0.76/1K on Starter $19/mo, or $0.83/1K on $25 PAYG), and 0 Credits when 0 jobs match.
- Should I pass Authorization: Bearer or x-api-key in Clay's Headers field?
- Both are natively supported by our gateway. In Clay's HTTP API Headers section, either Authorization: Bearer jp_live_your_key or x-api-key: jp_live_your_key authenticates identically.
- How do I avoid re-running the Clay HTTP column on already-enriched rows?
- Paste Boolean({{domain}}) && !{{hiring_signal_checked}} into Clay's Run Settings -> 'Only run if' formula box, and toggle off auto-update when editing downstream prompt columns.
Related Endpoints & Workflow Connectors
Other Connector · n8n Workflow JSON
n8n ATS Job Feed Workflow: Greenhouse & Workday to Slack
1 Credit / new event ($0.20–$0.76/1K) · 0 Credits when idle →
Other Connector · LangChain & CrewAI
LangChain & CrewAI Job Search Tool for Real-Time ATS Data
1 Credit / job ($0.20–$0.76/1K) · 0 Credits on 0 matches →
Instant API Key · Zero Credit Card Required
Test this Clay HTTP API connector free with 1,500 Credits ($1.50).
Includes 60 RPM / 5 RPS throughput, +2,000 Sandbox Streak bonus credits ($3.50 total free testing), and automatic 0-credit protection whenever a search returns 0 jobs.