# Recruiterflow Jobs API

> Public job postings from agencies that use Recruiterflow, one endpoint - same schema as 30+ other sources.

**Canonical URL:** https://jobspipe.dev/sources/recruiterflow

## Coverage

- **Sources covered:** Public Recruiterflow-hosted job boards
- **Freshness:** 24h refresh
- **History retention:** 12 months retention

## Why Recruiterflow jobs data is confusing

"Recruiterflow API" points at Recruiterflow's API-key-authenticated recruiting-CRM API, scoped to a single agency's jobs, candidates, and deals. It automates one agency's workflow, not postings across every Recruiterflow customer.

Recruiterflow agencies publish open roles to public job boards, but there is no public endpoint that enumerates Recruiterflow accounts or their postings. JobsPipe indexes the public Recruiterflow-hosted postings it can identify and normalizes them into the same JSON shape as every other source.

## Workarounds

### Use the Recruiterflow API

Right for automating one agency's jobs, candidates, and deals with that agency's API key. It is not a cross-account job feed.

### Scrape individual Recruiterflow boards

Possible for a board whose URL you already know. Subject to rate limits, HTML drift, and no way to discover other accounts.

### Use JobsPipe

Public job postings from Recruiterflow-powered boards under one endpoint, normalized - no per-account API key, no board discovery.

## Fields available on every record

- `id`
- `source`
- `tenant`
- `title`
- `company`
- `location`
- `salary`
- `employment_type`
- `remote`
- `posted_at`
- `expires_at`
- `apply_url`
- `description`

## Sample response

```json
{
  "id": "rf_ODIyN2ExZmMtM2Rl",
  "source": "recruiterflow",
  "tenant": "storm2",
  "title": "Backend Engineer (Fintech)",
  "company": "Storm2",
  "location": {
    "city": "New York",
    "region": "NY",
    "country": "US",
    "remote": true
  },
  "salary": {
    "min": 150000,
    "max": 190000,
    "currency": "USD",
    "period": "year",
    "source": "explicit"
  },
  "employment_type": "full_time",
  "posted_at": "2026-05-14T13:45:00Z",
  "expires_at": null,
  "apply_url": "https://jobs.recruiterflow.com/storm2/...",
  "description": "Storm2 is recruiting a Backend Engineer for a high-growth fintech client ..."
}
```

## FAQ

### Is there a Recruiterflow API for job postings?

Recruiterflow has an API-key-authenticated API scoped to one agency's data - not a public feed across every Recruiterflow customer. For public Recruiterflow-hosted postings across many agencies, JobsPipe is the aggregation layer.

### How do I get a Recruiterflow API key?

A Recruiterflow API key is generated inside the agency's account settings and only sees that account's data. JobsPipe needs no Recruiterflow key: it consumes only public board postings and authenticates with one JobsPipe key.

### Can I get jobs from one agency that uses Recruiterflow?

Yes. "company_name_partial_match_or": ["storm2"] in the JSON body of POST /v1/jobs/search filters to that agency's postings (substitute any name).

### Does JobsPipe expose Recruiterflow candidate data?

No. JobsPipe reads only public job postings - never candidate or deal data.

## Recruiterflow API documentation

Recruiterflow's developer documentation covers an API-key-authenticated API scoped to a single agency account, exposing that account's jobs, candidates, and deals. It is not a public, cross-account job feed: there is no unauthenticated postings endpoint and no list endpoint to enumerate Recruiterflow customers. JobsPipe's normalized JSON schema is documented at /docs and uses the same shape across Recruiterflow, Workday, Greenhouse, and 30+ other sources.

## Related

- **Product:** https://jobspipe.dev/jobs-api
- **All sources:** https://jobspipe.dev/sources
- **Docs:** https://jobspipe.dev/docs
- **Sign up (free tier):** https://jobspipe.dev/signup

---
Generated from structured data. View the rendered page at https://jobspipe.dev/sources/recruiterflow.