Recruitis.io
✓ Official Vendor SpecHR recruitingPayrollbearer62 EndpointsREST
For Agents
Programmatically log in, log out. Covers 62 operations with bearer authentication.
Use for: I need to log in, I want to log out, Search for my information, Find all new job
Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.
API Documentation for the Recruitis.io System The documentation is based on authorization using a token, which is generated either by the system itself or by the user within Recruitis. Over time, additional functionalities will be added. If the functionality of any API call is disrupted, a new branch (v2, etc.) will be created, or you will be informed of the change well in advance. API URL To call. The API exposes 62 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Recruitis.io to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Recruitis.io, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frecruitis.io%2Frecruitis" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frecruitis.io%2Frecruitis" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Recruitis.io API.
Log in
Get my information
Create new job
Show list of channels
Monitor Recruitis.io operational status and events
Use Cases
Patterns agents use Recruitis.io API for, with concrete tasks.
★ HR and Recruiting Operations
Use the Recruitis.io to perform hr recruiting operations programmatically. The API provides 62 endpoints covering core functionality including log in, log out, get my information.
Call PUT /login to log in
Automated Authentication Management
Automate authentication operations by combining multiple Recruitis.io endpoints. Agents can log out and then get my information in a single workflow.
Call PUT /logout to log out, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Recruitis.io endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'log in', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
62 endpoints — api documentation for the recruitis.
METHOD
PATH
DESCRIPTION
PUT
/login
Log in
PUT
/logout
Log out
GET
/me
Get my information
POST
/jobs
Create new job
GET
/jobs
Get all jobs
GET
/jobs/{id}
Get job detail
GET
/jobs/{id}/channels
Show list of channels
PUT
/jobs/{id}/channel/{channel_id}
Publish job
PUT
/login
Log in
PUT
/logout
Log out
GET
/me
Get my information
POST
/jobs
Create new job
GET
/jobs
Get all jobs
GET
/jobs/{id}
Get job detail
GET
/jobs/{id}/channels
Show list of channels
PUT
/jobs/{id}/channel/{channel_id}
Publish job
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Recruitis.io by hand means handling its bearer token auth, pointing at the app.recruitis.io/api2 host, and managing login yourself. Through Jentic you install once, import Recruitis.io from the API Directory, store the token once, and your agent calls it.
Permission scoping
Recruitis.io puts the job id in the URL path (/jobs/{id}), so a rule can pin your agent to specific jobs and their channels. You choose the operations it may call, so writes like assigning a job to a channel are only included if you add them.
Credential isolation
Your Recruitis.io token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a job' or 'list a job's channels', and Jentic returns the matching Recruitis.io operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Recruitis.io API through Jentic.
What authentication does the Recruitis.io use?
The Recruitis.io uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I log in with the Recruitis.io?
Yes. Use the PUT /login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Recruitis.io?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I log in through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'log in'. Jentic returns the matching Recruitis.io operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Recruitis.io have?
The Recruitis.io exposes 62 endpoints covering authentication, me, jobs operations.
Can I limit what my agent is allowed to do with the Recruitis.io API?
Yes. Because you run Jentic One yourself, your own rules decide which Recruitis.io operations the agent may call and which stored token it uses. Recruitis.io puts the job id in the URL path, such as /jobs/{id} and /jobs/{id}/channels, so you can pin the agent to specific jobs and their channels rather than the whole account. You choose the operations it may run, so write actions like creating a job or publishing a job to a channel are available only if you add them.
GET STARTED