Pull real-time infrastructure signals into any Clay table in under 5 minutes using the HTTP API enrichment block.
In Clay, create a new table or open an existing one. You can start with a list of company domains you want to monitor — one domain per row in a "Domain" column.
Click + Add enrichment → HTTP API. Configure it as follows:
| Field | Value |
|---|---|
| Method | GET |
| URL | https://forelight.net/v1/signals |
| Header: Authorization | Bearer YOUR_API_KEY |
| Param: apex_domain | {{Domain}} (your domain column) |
| Param: type | new_apex_domain |
| Param: limit | 10 |
This returns the 10 most recent signals for each company in your list.
The API returns a JSON object. Map these paths to Clay columns:
| Clay column name | JSON path |
|---|---|
| Signal Type | data[0].signal_type |
| Score | data[0].score |
| Domain | data[0].domain |
| Detected At | data[0].detected_at |
| Company Name | data[0].company_name |
| Industry | data[0].company_industry |
| SaaS Vendor | data[0].saas_vendor |
| Hosting Provider | data[0].hosting_provider |
| Total Signals | total |
data[0].score as a Clay filter column. Score ≥ 70 = high-conviction signal (geographic expansion, wildcard cert, SaaS adoption). Route high-score rows to immediate sequences; lower scores to nurture.
Use the type query parameter to focus on a specific signal:
| type value | Score | Use case |
|---|---|---|
| domain_velocity | 90 | 3+ new domains in 7 days — acquisition, rebrand, or major launch |
| geographic_expansion | 85 | Company registered a country-code domain — entering a new market |
| wildcard_cert_issued | 70 | *.company.com — building out dynamic subdomain infrastructure |
| saas_adoption_detected | 65 | Company just adopted Shopify, HubSpot, Salesforce, Vercel, etc. |
| infrastructure_expansion | 50 | 5+ new subdomains in 24h — growth indicator |
| new_apex_domain | 40 | Company just registered a new top-level domain |
| new_subdomain | 20 | Company expanding infrastructure with a new subdomain |
One of the most powerful plays: trigger outreach when a company adopts a SaaS tool that's adjacent to yours.
Set up a Clay table with your target accounts. Add an HTTP API column with:
If data[0] is populated, this company just adopted that SaaS tool. Route them to your sequence.
All query parameters are optional and combinable:
| Parameter | Description |
|---|---|
| apex_domain | Filter to a specific company domain (e.g. acme.com) |
| domain | Exact subdomain match |
| type | Signal type (see above) |
| saas_vendor | SaaS platform name (Shopify, HubSpot, Salesforce, Vercel, etc.) |
| industry | Company industry (e.g. retail, technology, finance) |
| hosting_provider | AWS, Cloudflare, GCP, etc. |
| since | ISO 8601 timestamp — only signals after this time |
| limit | Number of results (default 100, max 1000) |
| cursor | Pagination cursor from previous response |
since to only pull signals from the last 7 days: since=2026-06-21T00:00:00Z. Combine with a Clay formula that generates a rolling date to keep your table current.
On Starter and Pro tiers, use POST /v1/signals/batch instead of per-row GET calls. This is dramatically faster for large Clay tables and uses the same quota (1 credit per domain).
Response groups signals by domain — map data.acme_com[0].score directly to a Clay column. Use in a Clay HTTP API enrichment block with method POST and JSON body.
Email clifton.n.harris@gmail.com or check the full API docs.