# Breezy HR Jobs API

> Every public Breezy HR career site, one endpoint. No need to enumerate company slugs.

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

## Coverage

- **Sources covered:** Public Breezy HR customers
- **Freshness:** 24h refresh
- **History retention:** 12 months retention

## Why Breezy HR jobs data is confusing

Breezy HR offers a public Job Board JSON feed at app.breezy.hr/json/<company> - usable when you already know each company's Breezy slug. The catch: there's no list endpoint that enumerates Breezy customers, and not every customer enables the public feed. For cross-customer aggregation you either run continual slug discovery or use an aggregator.

Breezy customers host their careers pages at app.breezy.hr/<company> (and on customer-owned domains via embeds). JobsPipe indexes every public Breezy careers site we can identify and normalizes the data into the same schema as our other sources.

## Workarounds

### Hit app.breezy.hr/json/<company> directly

Works when you know the slug and the customer has the public feed enabled. There's no list endpoint to discover slugs from.

### Scrape app.breezy.hr subdomains

Possible but each company is its own config and subject to Breezy's rate limits.

### Use JobsPipe

Every public Breezy customer we've discovered, one endpoint, no slug enumeration needed.

## 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": "br_NzVmYmRiMjMtYTllZg",
  "source": "breezy",
  "tenant": "northbeam",
  "title": "Senior Frontend Engineer",
  "company": "Northbeam",
  "location": {
    "city": null,
    "region": null,
    "country": null,
    "remote": true
  },
  "salary": {
    "min": 140000,
    "max": 180000,
    "currency": "USD",
    "period": "year",
    "source": "explicit"
  },
  "employment_type": "full_time",
  "posted_at": "2026-05-10T14:55:00Z",
  "expires_at": null,
  "apply_url": "https://app.breezy.hr/p/northbeam/...",
  "description": "Northbeam is hiring a Senior Frontend Engineer to work on our attribution dashboards and customer-facing analytics surfaces ..."
}
```

## FAQ

### Why not just hit app.breezy.hr/json/<company> directly?

You can, when you already know the slug and the customer has the public feed turned on. JobsPipe is useful when you don't know the slugs in advance or want a normalized schema across Breezy plus 30+ other sources.

### How fresh is Breezy data?

Breezy careers pages are re-crawled at least every 24 hours.

### Are remote-only Breezy postings supported?

Yes. Many Breezy customers post remote roles; "remote": true in the JSON body of POST /v1/jobs/search filters to remote-only across Breezy and every other source.

### Does JobsPipe include Breezy ATS pipeline data?

No. JobsPipe is jobs-only. Candidate pipeline data is private to each Breezy customer's account.

## Breezy HR API documentation

Breezy HR developer documentation lives at developer.breezy.hr. The headline surfaces are the public Job Board JSON feed (app.breezy.hr/json/<company>) which returns published openings per customer, plus a private API for candidates, applicants, scorecards (account-scoped, OAuth or per-account key). The Job Board feed is the closest to a public endpoint, but you still need to know each customer's slug in advance to consume it. JobsPipe's documentation at /docs covers the unified JSON shape across Breezy plus 30+ other sources.

## Breezy HR API key

Breezy HR private API keys live inside the customer's Breezy admin under Settings > Integrations. The Job Board JSON feed itself doesn't require a key - it's public - but you still need to discover each customer's slug to fetch their feed. JobsPipe needs no Breezy credentials: we consume Job Board feeds for every Breezy customer we've discovered and authenticate with one JobsPipe key.

## Breezy HR API integration

Single-customer Breezy integration uses customer-minted credentials per company. Cross-customer aggregator integration is JobsPipe - every public Breezy customer, one endpoint, no slug-discovery loop required, same JSON schema as 30+ other ATSs.

## 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/breezy.