Manatal API

Name: Manatal API
Brand: Manatal API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting Atsbearer14 EndpointsREST

For Agents

Create and update jobs, candidates, clients, and pipeline activity in the Manatal applicant tracking system through a bearer-token REST API.

Install Jentic One Beta

Connect the Manatal API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Manatal API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Manatal API.

Post a new job opening into a Manatal workspace and update its details over time

Create candidate records and attach them to a specific job pipeline

Read a candidate's activity history to reconstruct touchpoints in the funnel

GET STARTED

Start building with Manatal API

Explore with Jentic

View OpenAPI Document

Manatal is an AI-assisted recruitment platform used by in-house talent teams and agencies, and its API exposes the core ATS objects — jobs, candidates, clients, pipelines, and activities — through a REST surface under /open/v3. The endpoints support the recruiter day-to-day: posting and updating jobs, creating and editing candidate records, attaching activity history, and reading pipeline configuration. Authentication is bearer token via the Authorization header, generated per workspace from the Manatal admin UI. The API is suited to ATS sync work, candidate sourcing pipelines, and reporting on hiring funnels.

Use Cases

Patterns agents use Manatal API for, with concrete tasks.

★ Sync sourced candidates from a sourcing tool

Recruiting agencies sourcing candidates in LinkedIn or Hunter.io need those records to land in Manatal without manual rekeying. Calling POST /open/v3/candidates with the parsed profile creates the record, and a follow-up call attaches the candidate to the right job pipeline. This keeps the ATS as the system of record while sourcing happens elsewhere.

Create a Manatal candidate from a parsed LinkedIn profile and attach them to job id 4421 in the Sourced stage.

Publish a job opening from an internal hiring tool

Talent teams running an internal requisition workflow need approved roles to flow into Manatal as published jobs. POST /open/v3/jobs creates the job with title, description, and client, and PUT /open/v3/jobs/{jobId} keeps the record in sync as the requisition is edited. The result is one canonical job record in the ATS rather than parallel listings drifting out of sync.

Create a Manatal job titled 'Senior Backend Engineer' for client id 88 and update its description after approval.

Hiring funnel reporting

Heads of talent need weekly visibility into stage-by-stage conversion across roles. Reading GET /open/v3/jobs alongside candidate activity per job builds a funnel report — applications, screens, interviews, offers — without exporting CSVs from the Manatal UI. The activities endpoint provides the timestamped events the report depends on.

Pull all jobs and their candidate activities for the last 7 days and produce a stage-conversion summary per job.

Agent-driven recruiter assistant

An AI assistant inside a recruiter's workflow needs to act on the ATS — file a candidate, log a call, move someone forward — without the recruiter switching tabs. Through Jentic, the agent searches for the right Manatal operation by intent, loads the schema, and executes with a scoped credential. The recruiter speaks the action and the agent calls the API, with the bearer token never exposed in the conversation.

Given a recruiter instruction 'add Jane Doe as a candidate to the Marketing Lead role', call Manatal via Jentic to create the candidate and attach to the job.

Key Endpoints

14 endpoints — manatal is an ai-assisted recruitment platform used by in-house talent teams and agencies, and its api exposes the core ats objects — jobs, candidates, clients, pipelines, and activities — through a rest surface under /open/v3.

METHOD

PATH

DESCRIPTION

GET

/open/v3/jobs

List jobs

POST

/open/v3/jobs

Create a job

PUT

/open/v3/jobs/{jobId}

Update a job

GET

/open/v3/candidates

List candidates

POST

/open/v3/candidates

Create a candidate

PUT

/open/v3/candidates/{candidateId}

Update a candidate

GET

/open/v3/candidates/{candidateId}/activities

List candidate activities

GET

/open/v3/pipelines

List pipelines

GET

/open/v3/jobs

List jobs

POST

/open/v3/jobs

Create a job

PUT

/open/v3/jobs/{jobId}

Update a job

GET

/open/v3/candidates

List candidates

POST

/open/v3/candidates

Create a candidate

PUT

/open/v3/candidates/{candidateId}

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Manatal bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped access session — the raw Authorization header value never enters the agent's prompt context, so a leaked transcript cannot leak the workspace token.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a candidate in manatal') and Jentic returns the matching POST /open/v3/candidates operation with its input schema, so the agent can call it without browsing the Manatal docs.

Time to first call

Direct Manatal integration: 1-2 days for auth, pagination, and pipeline mapping. Through Jentic: under an hour — search, load schema, execute.

FAQs

Specific to using Manatal API through Jentic.

What authentication does the Manatal API use?

Manatal uses bearer token authentication, with the token passed in the Authorization header. Tokens are generated per workspace from the Manatal admin UI. Through Jentic, the token is stored encrypted in the vault and scoped to the calling agent — the raw bearer value never sits in the agent's prompt context.

Can I create candidates and attach them to a job through the Manatal API?

Yes. POST /open/v3/candidates creates a candidate record, and the candidate can be associated with a job through the candidate payload's job reference fields. Use PUT /open/v3/candidates/{candidateId} afterwards to update stage or attach activities.

What are the rate limits for the Manatal API?

The published spec does not list explicit rate limits. Manatal's public docs note that excessive request rates may be throttled at the workspace level. For bulk imports, batch and back off on 429 responses rather than hammering the candidate or job endpoints.

How do I post a new job to Manatal through Jentic?

Run pip install jentic, then search Jentic for 'create a job in manatal'. Jentic returns the POST /open/v3/jobs operation, you load its input schema, and execute with the title, description, and client_id fields populated to create the job.

Does the Manatal API expose pipeline stages?

Yes. GET /open/v3/pipelines returns the pipelines configured in the workspace, including the ordered stages. This is how external tools can map their internal candidate statuses onto the correct Manatal stage when syncing records.

Can I retrieve the activity history of a candidate?

Yes. GET /open/v3/candidates/{candidateId}/activities returns the timestamped activity events for a single candidate, which is what funnel reports and recruiter dashboards consume to reconstruct touchpoints.

Manatal API

Connect the Manatal API to your agent

Capabilities

Start building with Manatal API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs