---
title: "Breezy HR API"
description: "Breezy HR API: the keyless per-company JSON feed under the careers site, its slug and opt-in limits, and every public Breezy posting in one call."
canonical: https://jobspipe.dev/sources/breezy
date_published: 2026-06-16
date_modified: 2026-09-26
author: Dvir Atias
---

# Breezy HR API

Breezy HR exposes a keyless JSON feed of one company's published positions under that company's Breezy careers site when the customer enables it, but you must know each slug and there is no list endpoint across customers. JobsPipe collects public Breezy HR postings into one search endpoint, in the same record shape as the rest of its 30+ sources.

> Breezy HR's JSON feed is one company at a time, and there is no list of customers. JobsPipe collects public Breezy HR postings into one endpoint with the same record shape as the other collected boards.

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

## Coverage

- **Sources covered:** Public Breezy HR career sites
- **Freshness:** discovered_at, last_seen_at and verified_at on every record
- **History retention:** Closed postings kept, with closed_at and closed_reason

## Why Breezy HR jobs data is confusing

Breezy HR exposes a JSON feed of published positions for one company, on that company's Breezy careers site under a /json path, when the customer enables it. It is keyless, but you must know each company's Breezy slug, not every customer enables it, and there is no list endpoint that enumerates Breezy customers.

Breezy customers publish openings at app.breezy.hr/<company> or on a <company>.breezy.hr subdomain, and on their own domains through embeds. Breezy also syndicates to job boards on the customer's behalf, so the same role can appear on several boards. JobsPipe collects public Breezy HR postings and returns them with sources[0].provider set to breezy.

## Workarounds

### Read the per-company JSON feed

Works for customers who enable it and whose slug you know. Slug discovery and the disabled-feed case are on you.

### Scrape Breezy careers pages

Possible per employer you already know. Public HTML, no directory.

### Use JobsPipe

Public Breezy HR postings, one endpoint, the same schema as every other collected board. Free tier of 1,000 jobs to start.

## Fields available on every record

- `id`
- `job_title`
- `company`
- `company_domain`
- `url`
- `date_posted`
- `discovered_at`
- `last_seen_at`
- `verified_at`
- `status`
- `closed_at`
- `closed_reason`
- `ghost_score`
- `seniority`
- `cities`
- `state_code`
- `min_annual_salary_usd`
- `max_annual_salary_usd`
- `technology_slugs`
- `keyword_slugs`
- `esco_skills`
- `sources`

## Sample response

```json
{
  "id": "5c2e81a4d7f0",
  "job_title": "Customer Success Manager",
  "company": "Northwind Clinics",
  "company_domain": "northwindclinics.example",
  "url": "https://northwind-clinics.breezy.hr/p/5c2e81a4d7f0-customer-success-manager",
  "date_posted": "2026-09-04",
  "discovered_at": "2026-09-04T13:40:05+00:00",
  "last_seen_at": "2026-09-08 00:44:12",
  "verified_at": "2026-09-08 00:58:30",
  "status": "active",
  "closed_at": null,
  "closed_reason": null,
  "ghost_score": 9,
  "seniority": "mid",
  "cities": [
    "Denver"
  ],
  "state_code": "CO",
  "min_annual_salary_usd": 62000,
  "max_annual_salary_usd": 74000,
  "technology_slugs": [
    "hubspot",
    "zendesk"
  ],
  "keyword_slugs": [
    "customer-success",
    "healthcare"
  ],
  "sources": [
    {
      "provider": "breezy",
      "url": "https://northwind-clinics.breezy.hr/p/5c2e81a4d7f0-customer-success-manager"
    }
  ]
}
```

## FAQ

### How do I find a company's Breezy HR slug?

Read it from the company's careers site. Breezy customers publish openings at app.breezy.hr/<company> or on a <company>.breezy.hr subdomain, and the JSON feed sits under a /json path on that careers site. Companies that embed Breezy on their own domain hide the slug behind their own pages, and there is no list endpoint that enumerates Breezy customers.

### Is the Breezy HR JSON feed free to use?

Yes, where the customer has enabled it. The feed is keyless and returns that one company's published positions, but not every customer turns it on, and there is no cross-customer feed. When a company's feed is disabled, the fallback is its public careers page, which is plain HTML you parse per employer.

### Is there a list of companies that use Breezy HR?

Not from Breezy. It has no list endpoint and no customer directory, so building a Breezy customer list yourself is a crawl of careers pages rather than an API call. A JobsPipe search with "source_or": ["breezy"] returns the employers behind public Breezy HR postings in the company field of each record.

### How do I search Breezy HR jobs across employers?

Send "source_or": ["breezy"] in the JSON body of POST /v1/jobs/search and narrow with job_title_or, job_location_or or company_name_partial_match_or. Breezy syndicates postings to job boards on the customer's behalf, so drop source_or to see the same employer's roles on every collected board; sources[0].provider on each record names the board it came from.

## Does Breezy HR have an API?

Breezy HR exposes a JSON feed of published positions for one company, on that company's Breezy careers site under a /json path, when the customer enables it. It is keyless, but you must know each company's Breezy slug, not every customer enables it, and there is no list endpoint that enumerates Breezy customers. Breezy customers publish openings at app.breezy.hr/<company> or on a <company>.breezy.hr subdomain, and on their own domains through embeds. Breezy also syndicates to job boards on the customer's behalf.

## What JobsPipe returns for Breezy HR

A POST /v1/jobs/search with "source_or": ["breezy"] returns public Breezy HR postings as JobsPipe records: id, job_title, company, company_domain when it resolves, url on the company's Breezy careers site, date_posted, discovered_at, last_seen_at, verified_at, status with closed_at and closed_reason once a posting closes, ghost_score, seniority, min_annual_salary_usd and max_annual_salary_usd when the posting states a range, technology_slugs and keyword_slugs parsed from the description, and sources[0].provider set to breezy. Drop source_or to search every collected board at once.

## Related

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

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

---
Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup:

```bash
curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search
```

Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin