Source · Comeet

Comeet Jobs API.

Comeet (now Spark Hire Recruit) ships a Careers API designed for one customer's own site - not for aggregators. JobsPipe normalizes every public Comeet tenant into the same JSON shape as 30+ other sources.

All public Comeet career sites (600+ companies)
24h refresh
12 months retention

Why people are confused about the Comeet API

Comeet (rebranded to Spark Hire Recruit in 2023) has a well-documented developer portal at developers.comeet.com with two REST surfaces: a Careers API for syncing one customer's careers website with their Recruit account, and a Recruiting API for ATS-scope operations (candidates, applications, OAuth, webhooks, GraphQL). Both are scoped to one customer's UID + token pair - there's no aggregator-tier credential.

On the public side, every Comeet customer's career site is rendered at www.comeet.com/jobs/<company-uid>/ (with custom-domain options for paid tiers). The data behind those pages is fetched from Comeet's internal endpoints, but the shape varies across plan tiers and the per-tenant UID is required for every call. JobsPipe indexes every public Comeet career site and returns one flat record per posting in the same JSON schema as 30+ other sources.

Option 1
Get a UID + API token from each Comeet customer

Works for one customer at a time. Every Comeet tenant has its own UID and token, and there's no path to a cross-tenant developer key.

Option 2
Scrape www.comeet.com/jobs/<uid>

Possible. Custom-domain tenants, plan-tier rendering differences, and Comeet's bot detection make this more work than a uniform parser suggests.

Option 3
Use JobsPipe

Every public Comeet career site, one endpoint, flat JSON. Free tier covers 5,000 requests/month.

Comeet API documentation

Comeet's developer documentation lives at developers.comeet.com and is organized around two REST surfaces: the Careers API (intended to sync one customer's careers website with their Recruit account, with the most design flexibility of Comeet's embed options) and the Recruiting API (full ATS scope - candidates, applications, OAuth, webhooks, GraphQL, sandbox environment). Both are tenant-scoped: every call takes a customer UID and an authentication token minted inside that customer's Recruit admin. JobsPipe's normalized schema at /docs is the same shape across Comeet, Workday, Greenhouse, and 30+ other ATSs.

Comeet UID and token authentication

Comeet's APIs use a UID-plus-token model: the UID identifies the Recruit tenant and the token authenticates the caller. Tokens are minted inside the customer's Recruit admin and only see that customer's data. Comeet does not issue cross-tenant aggregator credentials. JobsPipe sidesteps the per-tenant model by reading public career-site data and exposing it under one JobsPipe key.

Comeet API integration

Single-tenant Comeet integration (post jobs from your CRM, sync candidates to a data warehouse, build a custom careers page) uses the Careers or Recruiting API with the customer's UID and token. Cross-tenant aggregation - what most teams arriving at this page want - is JobsPipe: every public Comeet (Spark Hire Recruit) career site under one endpoint, normalized into the same JSON schema as 30+ other ATSs, with no per-customer onboarding.

Sample request

curl "https://api.jobspipe.dev/v1/jobs?source=comeet" \
     -H "Authorization: Bearer $JOBSPIPE_KEY" \
     -H "Accept: application/json"

Sample response

{
  "id": "ct_NDk3MjE4MDQ0",
  "source": "comeet",
  "tenant": "fictiv",
  "title": "Backend Engineer, Pricing Platform",
  "company": "Fictiv",
  "location": {
    "city": "Tel Aviv",
    "region": "TA",
    "country": "IL",
    "remote": false
  },
  "salary": null,
  "employment_type": "full_time",
  "remote": "hybrid",
  "department": "Engineering",
  "posted_at": "2026-05-09T12:31:00Z",
  "expires_at": null,
  "apply_url": "https://www.comeet.com/jobs/fictiv/backend-engineer-pricing/95.A0E",
  "description": "Fictiv is hiring a Backend Engineer to own the pricing platform that quotes every order in real time ..."
}

Every Comeet job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.

Fields in every Comeet job record

idsourcetenanttitlecompanylocationsalaryemployment_typeremoteposted_atexpires_atapply_urldescription

FAQ

Do I need a Comeet UID or API token to use JobsPipe?+

No. JobsPipe reads only public career-site pages and doesn't use the authenticated Comeet APIs. You only need a JobsPipe key.

Is Comeet the same as Spark Hire Recruit?+

Yes. Comeet was acquired by Spark Hire in 2023 and the product is now branded Spark Hire Recruit. The developer portal still lives at developers.comeet.com and the UID-scoped careers URL pattern is unchanged - JobsPipe handles both names under the same source identifier.

How fresh is Comeet data on JobsPipe?+

Public Comeet career sites are re-crawled at least every 24 hours.

Does JobsPipe cover Comeet customers on custom domains?+

Yes. Customers using careers.<their-domain>.com instead of www.comeet.com/jobs/<uid> are indexed alongside the rest and exposed under the same source identifier.

Try Comeet data free - 5,000 requests/month, no credit card.

Get a free API key