Source · ManatalManatal Jobs API.
Every public Manatal-hosted careers site, one endpoint. Recruiting agencies and in-house teams both covered.
Why people are confused about the Manatal API
Manatal is positioned as a recruiting CRM as much as an ATS - many of its customers are agencies placing candidates across multiple clients. Manatal's REST API is available to subscribers but is scoped per-customer, with no public cross-customer endpoint exposing jobs across the Manatal universe.
Manatal customers host their careers pages at careers.manatal.com/<company> or on their own domains via embeds. JobsPipe indexes every public Manatal careers page and normalizes the data into the same schema as Workday, Indeed, and our other sources.
Possible for a single named partner. Not a viable path for cross-customer coverage.
Technically possible. Each customer is its own scraper config, subject to Manatal's rate limits.
Every public Manatal customer, one endpoint, same JSON schema as the rest of JobsPipe.
Manatal API documentation
Manatal developer documentation lives at developers.manatal.com. The REST API covers candidates, jobs, clients (Manatal supports recruiting agencies, so 'client' is a first-class concept distinct from the agency's own user accounts), and webhooks. All endpoints are customer-scoped - there's no cross-customer aggregator surface. JobsPipe's documentation at /docs covers the unified JSON schema we return for every public Manatal careers page, normalized to the same shape as our other ATS sources.
Manatal API key
Manatal mints API keys inside the customer's Manatal admin under Settings > API. Each key is account-scoped. For recruiting agencies on Manatal, the key sees the agency's own data plus the data for every end-client the agency manages - but only within that agency's account. JobsPipe doesn't need Manatal credentials - we consume only public Manatal careers pages and authenticate with one JobsPipe key.
Manatal API integration
Single-customer Manatal integration uses Manatal-issued credentials per agency or in-house team. Cross-customer integration - where you want jobs across many Manatal-using companies and agencies in one feed - is JobsPipe: every public Manatal customer, one endpoint, normalized JSON.
Sample request
curl "https://api.jobspipe.dev/v1/jobs?source=manatal" \
-H "Authorization: Bearer $JOBSPIPE_KEY" \
-H "Accept: application/json"Sample response
{
"id": "mn_N2I4MzAwYWMtYjFkOA",
"source": "manatal",
"tenant": "fitch-bennett",
"title": "Senior Recruitment Consultant",
"company": "Fitch Bennett Partners",
"location": {
"city": "Singapore",
"region": null,
"country": "SG",
"remote": false
},
"salary": null,
"employment_type": "full_time",
"posted_at": "2026-05-12T07:30:00Z",
"expires_at": null,
"apply_url": "https://careers.manatal.com/fitch-bennett/...",
"description": "Fitch Bennett is hiring a Senior Recruitment Consultant to lead our financial-services placement practice in APAC ..."
}Every Manatal 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 Manatal job record
FAQ
Does JobsPipe need Manatal API credentials per customer?+
No. JobsPipe consumes only public-facing Manatal careers data.
Are agency-placed roles included?+
Yes, if the agency makes the role public on their Manatal careers page. JobsPipe doesn't distinguish between in-house and agency postings - both flow through the same schema.
How fresh is Manatal data?+
Every Manatal customer's public careers page is re-crawled at least every 24 hours.
Can I filter by region or country?+
Yes. Use ?country=SG for Singapore-only postings (or any ISO country code), ?country=US for US postings, etc.
Try Manatal data free - 5,000 requests/month, no credit card.
Get a free API key