Clay Hiring Signals: New-on-Board Signals via HTTP API Column
Clay hiring signals work best when they tell you a company is hiring for the team you sell to, not just that it has open jobs. RoleDawn gives you that as JSON: one HTTP API column returns the companies whose SDR, AE, RevOps or other role-family jobs are new on their own careers page since we started tracking it, each linked to the post. Setup takes six steps and a free key.
By the RoleDawn team · Published · Updated
Add an HTTP API column in Clay with Method GET and the endpoint https://roledawn.com/api/v1/signals?family=sdr&since=7d, and add your free RoleDawn key as the header X-RoleDawn-Key (email only, shown right away at roledawn.com/api/key). RoleDawn returns the companies with roles in that team new on their job board, each with the public job post, in a "signals" list; set the field path to signals, or use HTTP API as a source with signals as the results path to get one row per company.
- Free key, no account. Enter an email, copy the key, paste it into one header. No password, no card.
- A reason to reach out on every row. Each company comes with the job post that shows it is hiring for the team you sell to, and whether the company's own post calls the role "founding" or "our first".
- Already filtered. Staffing agencies, large established companies and intern or contract roles are left out; one row per company.
- Ranked. Posts where the company says "founding" or "our first" first, then signals observed on a board already tracked, then the newest.
What does the request look like?
Companies with SDR or BDR roles new on their job board in the last 7 days:
curl "https://roledawn.com/api/v1/signals?family=sdr&since=7d&limit=2"
Real response, captured 2026-10-11 (47 matching companies that day; limit=2 keeps the example short):
{
"family": "sdr",
"since": "7d",
"type": "first_hire",
"include_closed": false,
"window_start": "2026-10-04T16:16:47.784Z",
"generated_at": "2026-10-11T16:16:47.784Z",
"total": 47,
"count": 2,
"limit": 2,
"offset": 0,
"next_offset": 2,
"free_rows": 20,
"truncated": true,
"semantics": "Each record is a change RoleDawn observed on the company's public ATS job board between two reads (basis=observed), or inferred on our first read of that board (basis=inferred). It is not proof that the company never had this role before. Only founding_evidence (the company's own words in the job title or post) is a first-hire claim.",
"signals": [
{
"company": "Forum Ventures",
"company_key": "forum-ventures",
"company_url": "https://roledawn.com/companies/forum-ventures",
"title": "Market Development Representative",
"family": "sdr",
"type": "first_hire",
"signal": "SDR/BDR role new on their board",
"evidence": "New on their board",
"founding": true,
"location": "Toronto; New York",
"job_url": "https://jobs.ashbyhq.com/forum-ventures/1f0b3f36-7540-48ec-b4b9-bc8db8e14cd1",
"posted": "2026-10-07T04:20:23.872Z",
"detected": "2026-10-07T11:45:51.015Z",
"roles_last_30d": null,
"roles_prior_30d": null,
"signal_id": 7236,
"dedupe_key": "first_hire:561:sdr",
"ats": "ashby",
"job_posted_at": "2026-10-07T04:20:23.872Z",
"job_posted_at_source": "ashby:publishedAt",
"first_seen_at": "2026-10-07T11:45:51.015Z",
"detected_at": "2026-10-07T11:45:51.015Z",
"basis": "observed",
"basis_reason": "First SDR / BDR role seen on this ashby board since we started reading it on 2026-10-05: at least 1 earlier successful read, none with a SDR / BDR role (last empty read 2026-10-05T08:01:41.536Z).",
"founding_mention": true,
"founding_evidence": {
"source": "job_description",
"text": "as our first Market Development Representative"
},
"still_open": true,
"last_verified_open_at": "2026-10-10T23:45:10.105Z",
"closed_at": null,
"prior_observation": {
"source": "derived",
"company_first_crawled_at": "2026-10-05T08:01:41.536Z",
"crawls_before_detection": 1,
"crawls_before_detection_exact": false,
"last_empty_crawl_at": "2026-10-05T08:01:41.536Z"
}
},
{
"company": "SwiftConnect",
"company_key": "swiftconnect",
"company_url": "https://roledawn.com/companies/swiftconnect",
"title": "Sales Development Representative",
"family": "sdr",
"type": "first_hire",
"signal": "SDR/BDR role new on their board",
"evidence": "New on their board",
"founding": true,
"location": "United States",
"job_url": "https://jobs.lever.co/swiftconnect/3305b93a-6112-4334-a4f5-cb0a36f5eeed",
"posted": "2026-10-06T18:58:48.406Z",
"detected": "2026-10-07T06:30:17.442Z",
"roles_last_30d": null,
"roles_prior_30d": null,
"signal_id": 6006,
"dedupe_key": "first_hire:4213:sdr",
"ats": "lever",
"job_posted_at": "2026-10-06T18:58:48.406Z",
"job_posted_at_source": "lever:createdAt",
"first_seen_at": "2026-10-07T06:30:17.442Z",
"detected_at": "2026-10-07T06:30:17.442Z",
"basis": "observed",
"basis_reason": "First SDR / BDR role seen on this lever board since we started reading it on 2026-10-06: at least 1 earlier successful read, none with a SDR / BDR role (last empty read 2026-10-06T02:30:45.351Z).",
"founding_mention": true,
"founding_evidence": {
"source": "job_description",
"text": "founding SDR"
},
"still_open": true,
"last_verified_open_at": "2026-10-10T18:45:10.176Z",
"closed_at": null,
"prior_observation": {
"source": "derived",
"company_first_crawled_at": "2026-10-06T02:30:45.351Z",
"crawls_before_detection": 1,
"crawls_before_detection_exact": false,
"last_empty_crawl_at": "2026-10-06T02:30:45.351Z"
}
}
]
}
The same request with your free key, as Clay sends it:
curl -H "X-RoleDawn-Key: rd_your_key" -H "X-Client: clay-http-column" "https://roledawn.com/api/v1/signals?family=sdr&since=7d"
Same request for RevOps over 30 days:
curl "https://roledawn.com/api/v1/signals?family=revops&since=30d&limit=2"
Real response, captured 2026-10-11 (34 matching companies that day; limit=2 keeps the example short):
{
"family": "revops",
"since": "30d",
"type": "first_hire",
"include_closed": false,
"window_start": "2026-09-11T16:16:49.509Z",
"generated_at": "2026-10-11T16:16:49.509Z",
"total": 34,
"count": 2,
"limit": 2,
"offset": 0,
"next_offset": 2,
"free_rows": 20,
"truncated": true,
"semantics": "Each record is a change RoleDawn observed on the company's public ATS job board between two reads (basis=observed), or inferred on our first read of that board (basis=inferred). It is not proof that the company never had this role before. Only founding_evidence (the company's own words in the job title or post) is a first-hire claim.",
"signals": [
{
"company": "Keycard Labs",
"company_key": "keycard-labs",
"company_url": "https://roledawn.com/companies/keycard-labs",
"title": "Founding Revenue Operations Lead",
"family": "revops",
"type": "first_hire",
"signal": "RevOps role new on their board",
"evidence": "Job title says \"Founding\"",
"founding": true,
"location": "US - Remote",
"job_url": "https://jobs.ashbyhq.com/keycard-labs/834c4b93-bf46-48bd-adbe-819429bf513c",
"posted": "2026-10-08T19:15:28.250Z",
"detected": "2026-10-08T21:00:18.865Z",
"roles_last_30d": null,
"roles_prior_30d": null,
"signal_id": 9802,
"dedupe_key": "first_hire:1405:revops",
"ats": "ashby",
"job_posted_at": "2026-10-08T19:15:28.250Z",
"job_posted_at_source": "ashby:publishedAt",
"first_seen_at": "2026-10-08T21:00:18.865Z",
"detected_at": "2026-10-08T21:00:18.865Z",
"basis": "observed",
"basis_reason": "First RevOps role seen on this ashby board since we started reading it on 2026-10-05: at least 1 earlier successful read, none with a RevOps role (last empty read 2026-10-05T13:16:09.016Z).",
"founding_mention": true,
"founding_evidence": {
"source": "title",
"text": "Founding Revenue Operations Lead"
},
"still_open": true,
"last_verified_open_at": "2026-10-11T05:15:10.190Z",
"closed_at": null,
"prior_observation": {
"source": "derived",
"company_first_crawled_at": "2026-10-05T13:16:09.016Z",
"crawls_before_detection": 1,
"crawls_before_detection_exact": false,
"last_empty_crawl_at": "2026-10-05T13:16:09.016Z"
}
},
{
"company": "Replo",
"company_key": "replo",
"company_url": "https://roledawn.com/companies/replo",
"title": "Founding GTM",
"family": "revops",
"type": "first_hire",
"signal": "RevOps role new on their board",
"evidence": "Job title says \"Founding\"",
"founding": true,
"location": "San Francisco",
"job_url": "https://jobs.ashbyhq.com/replo/d2597358-ccfb-46a8-900d-cb66fa973263",
"posted": "2026-10-02T01:02:48.547Z",
"detected": "2026-10-06T02:39:34.835Z",
"roles_last_30d": null,
"roles_prior_30d": null,
"signal_id": 3570,
"dedupe_key": "first_hire:2039:revops",
"ats": "ashby",
"job_posted_at": "2026-10-02T01:02:48.547Z",
"job_posted_at_source": "ashby:publishedAt",
"first_seen_at": "2026-10-05T16:01:38.415Z",
"detected_at": "2026-10-06T02:39:34.835Z",
"basis": "inferred",
"basis_reason": "Found on our first read of this board, so there is no earlier observation. Inferred from the board: older roles in other functions and only 1 recent RevOps role; the job title says Founding.",
"founding_mention": true,
"founding_evidence": {
"source": "title",
"text": "Founding GTM"
},
"still_open": true,
"last_verified_open_at": "2026-10-11T09:15:10.126Z",
"closed_at": null,
"prior_observation": {
"source": "derived",
"company_first_crawled_at": "2026-10-05T16:01:38.415Z",
"crawls_before_detection": 0,
"crawls_before_detection_exact": false,
"last_empty_crawl_at": null
}
}
]
}
How do I set up the HTTP API column in Clay?
- Add the HTTP API column. In your Clay table, add a column, pick the HTTP API enrichment and set Method to GET.
- Paste the endpoint. Endpoint: https://roledawn.com/api/v1/signals. Under Query String Parameters add family = sdr (or a column such as /Family) and since = 7d.
- Add your free key as a header. Get a free personal key at roledawn.com/api/key (email only, shown right away). Under Header Fields add X-RoleDawn-Key = your key, or save it once as an HTTP API (Headers) account. Optionally add X-Client = clay-http-column. Clay calls from shared IPs, so the key keeps your 50 daily requests your own.
- Choose the fields to return. Under Field Paths to Return keep total and signals, or a single value such as signals.0.company.
- Set a polite rate limit. For example 1 request per 1000 ms. The API allows 60 requests per minute and 50 per day per key.
- Run it and spread the list into rows. Run the column, then use Write to Other Table on the signals list to get one row per company, or start a new table with HTTP API as a source and results path signals.
A simple setup: one small table with a row per role family you sell to (sdr, sales, revops), the HTTP API column calling RoleDawn with family = that row's value, and Write to Other Table sending each company into your prospecting table. From there your usual Clay enrichments find the domain and the people to contact.
Which fields can I map to columns?
| Field | Type | Meaning |
|---|---|---|
company | string | Company name. Source: ATS. |
company_key | string | RoleDawn company id. Source: RoleDawn. |
company_url | string | RoleDawn company page with all open roles. Source: RoleDawn. |
title | string | Title of the job post behind the signal. Source: ATS. |
family | string | Role family id (sdr, sales, revops, ...). Source: RoleDawn rule. |
type | string | first_hire (public name "New on their board": first role of the family we have seen on this board since we started tracking it, not proof of a first hire) or surge (clearly more roles than the 30 days before). Source: RoleDawn rule. |
signal | string | Readable label, e.g. "SDR/BDR role new on their board". Source: RoleDawn rule. |
evidence | string | "New on their board" (basis observed), "New on their board · inferred on first read" (basis inferred), or role counts for a surge. Source: RoleDawn rule. |
founding | boolean | Same as founding_mention (kept for existing callers). Source: ATS. |
location | string | null | Location text of the job post. Null when the post has no location. Source: ATS. |
job_url | string | The company's own public job post (original posting link). Source: ATS. |
posted | ISO 8601 | null | Deprecated: same as job_posted_at (until 2026-10-11 it fell back to first_seen_at). Null when as job_posted_at. Source: ATS. |
detected | ISO 8601 | Deprecated alias of detected_at. Source: RoleDawn observation. |
roles_last_30d | integer | null | Surges: roles of the family posted in the last 30 days. Null when type is first_hire. Source: RoleDawn observation. |
roles_prior_30d | integer | null | Surges: roles of the family posted in the 30 days before. Null when type is first_hire. Source: RoleDawn observation. |
signal_id | integer | RoleDawn signal id. Source: RoleDawn. |
dedupe_key | string | first_hire:<company id>:<family> (one ever per company and family; reposts never create a second) or surge:<company id>:<family>:<YYYY-MM>. Source: RoleDawn. |
ats | string | Applicant tracking system hosting the board. Source: RoleDawn. |
job_posted_at | ISO 8601 | null | Newest posting date the ATS shows; never filled with our first_seen_at. Null when the ATS gives no posting date. Source: ATS. |
job_first_posted_at | ISO 8601 | null | ATS posting date when we first saw the post; surge counts use it, so reposts do not count as new roles. Null when the ATS gave no posting date. Source: ATS. |
reposted | boolean | The ATS date moved forward or the title changed after we first saw the post (Workday dates are not compared). Source: RoleDawn. |
reposted_at | ISO 8601 | null | When we noticed the latest repost or rename. Null when never reposted or renamed. Source: RoleDawn. |
original_title | string | null | Title when we first saw the post, if renamed since; title is the current one. Null when never renamed. Source: ATS. |
job_posted_at_source | string | ATS field job_posted_at comes from, e.g. lever:createdAt; Greenhouse falls back to updated_at, Workday dates are day precision. Source: RoleDawn. |
first_seen_at | ISO 8601 | When RoleDawn first saw this job post on the board. Source: RoleDawn observation. |
detected_at | ISO 8601 | When RoleDawn created the signal. Source: RoleDawn observation. |
basis | string | observed = changed between two of our reads of the board; inferred = estimated on our first read, with no earlier observation. Source: RoleDawn rule. |
basis_reason | string | One sentence with the numbers behind basis. Source: RoleDawn rule. |
founding_mention | boolean | The company itself calls a role of this family founding / first / #1. The only first-hire claim in a record, and it is the company's words, not verified by RoleDawn; title evidence is the strong kind. Source: ATS. |
founding_evidence | object | null | {source: title | job_description, text}: the title, or the matched phrase in the job post. Null when founding_mention is false. Source: ATS. |
still_open | boolean | The post was still listed at our last successful read. Closed posts are left out unless include_closed=true. Source: RoleDawn observation. |
last_verified_open_at | ISO 8601 | null | Our last successful read of the board, at which the post was still listed. Null when the post is closed, or the last read failed before 2026-10-11. Source: RoleDawn observation. |
closed_at | ISO 8601 | null | First read at which the post was no longer listed. Null when the post is open. Source: RoleDawn observation. |
prior_observation.source | string | recorded = snapshot written when the signal was created (from 2026-10-11); derived = rebuilt from job timestamps (older signals). Source: RoleDawn. |
prior_observation.company_first_crawled_at | ISO 8601 | null | Our first successful read of this board (for boards tracked before 2026-10-11: earliest first_seen_at of any job there). Null when the board never had a job post before 2026-10-11. Source: RoleDawn observation. |
prior_observation.crawls_before_detection | integer | Successful reads of the board before the read that produced the signal (a minimum when derived). Source: RoleDawn observation. |
prior_observation.crawls_before_detection_exact | boolean | true when recorded; false when derived (true count is at least the number given). Source: RoleDawn. |
prior_observation.last_empty_crawl_at | ISO 8601 | null | Latest read before detection at which the board had 0 roles of this family (when derived: the latest such read we can prove). Null when basis is inferred, or type is surge. Source: RoleDawn observation. |
Field paths are relative to each item in signals once the list is spread into rows (for example company, job_url, founding). On the parent row, total tells you how many companies matched and truncated whether there were more than 20.
Which parameters can I change?
| Parameter | Required | Use |
|---|---|---|
family | required | Role family id, e.g. sdr, sales, revops; up to 5 comma-separated |
since | optional | 7d, 14d, 30d (default 7d): when the signal was detected |
type | optional | first_hire (default), surge or all |
limit | optional | Companies per page, 1–20 (default 20) |
offset | optional | Skip this many companies within the top 20; use next_offset |
include_closed | optional | true = also return signals whose job post has since closed (still_open=false). Default false: closed posts are left out |
Role family ids: revops, sales-enablement, marketing-ops, sales, sdr, sales-engineering, partnerships, customer-success, account-management, support, professional-services, marketing, product-marketing, growth-marketing, content, devrel, community, software-engineering, frontend, mobile, platform-sre, security, compliance, qa, engineering-management, hardware, it, data-engineering, data-analytics, ml-ai, product-management, design, ux-research, technical-writing, finance, legal, people, recruiting, bizops, workplace, executive, clinical, supply-chain. Unknown values come back as a JSON error with the parameter name:
Real response for since=90d (HTTP 400), captured 2026-10-11:
{
"error": {
"code": "invalid_parameter",
"message": "since must be one of 7d, 14d, 30d.",
"param": "since",
"docs": "https://roledawn.com/api#errors"
}
}
What should I write to these companies?
The job post is the reason to reach out: mention the specific detail it shows (an SDR hire, a RevOps role) and how you help teams at that stage. Read the post before you send. The Weekly List sample shows this week's top companies and a few suggested opening lines.
FAQ
What are hiring signals in Clay?
Hiring signals in a Clay table are columns that tell you a company is building a team right now, so the row is worth working this week. RoleDawn adds a specific one through a single HTTP API column: the companies that posted a role in a role family new on their own careers page since we started tracking it (an SDR, AE or RevOps role, for example), or whose hiring in one team clearly jumped, each with the public job post.
How is this different from a job-openings signal I already use in Clay?
RoleDawn's signal is narrower on purpose: it fires when a role family appears on a company's board for the first time since we started tracking it (2026-10-05), not every time a role is open, and every row comes with the job post and a "founding" flag (the company's own wording) you can map to a column. It is a list of new accounts to work rather than an alert on accounts you already have, so it sits next to any other signal in your table.
Do I need an API key to call RoleDawn from Clay?
Not to try it, but add one. Clay sends HTTP API requests from its own servers, so many Clay users share the same IP address and the keyless allowance (50 requests per IP per day) can run out because of other people's tables. A free personal key from roledawn.com/api/key (email only, shown right away) gives you 50 requests per day of your own: add it under Header Fields as X-RoleDawn-Key. Either way you get up to 20 companies per query and 60 requests per minute.
What happens if I hit the daily limit?
RoleDawn answers HTTP 429 with code rate_limited and a Retry-After header (seconds until 00:00 UTC, when the count resets). Without a key, the message links the free key page. Cached repeats of the same query do not count against the keyless limit.
Which role families can I ask for?
Any of the 43 RoleDawn role families. For outbound teams the useful ones are revops, sales-enablement, marketing-ops, sales, sdr, sales-engineering and the other GTM families. Ask for up to 5 at once with commas: family=sdr,sales,revops.
What does type=first_hire mean here?
"New on their board": the company posted a role in a family RoleDawn had not seen on its public job board since it started tracking it (2026-10-05). It is a change we observed, not proof that the company never had the role: only founding_evidence (the company's own words — a "Founding" job title is the strong kind, "our first …" in the description the weaker one) is a first-hire claim, and RoleDawn does not verify it. basis=observed ("New on their board") means the role appeared between two of our reads, with prior_observation saying how many earlier reads had none; basis=inferred ("New on their board · inferred on first read") is an estimate from our first read of the board. Every row links to the job post so you can check it.
Does the API give me contacts or email addresses?
No. It returns companies and their public job posts only. Use the Clay enrichments you already have to find the domain and the right people at each company.
How often should the Clay table refresh?
Career pages are re-read about once a day, so once a day with since=7d is enough. Repeated calls within 15 minutes are served from the cache.
What if more than 20 companies match?
total shows how many match and truncated is true. Narrow the query (one family, since=7d), or get the Weekly List: the top 20 sales-team companies every Monday by email and CSV with a suggested opening line for each, $349/month after a free 2-week trial.
Related: Hiring Signals API reference · OpenAPI spec · This week's Weekly List sample · New SDR/BDR posts · All roles new on company boards. RoleDawn is not affiliated with Clay.