For Agents
Programmatically create a account, list all accounts. Covers 46 operations with bearer authentication.
Use for: I need to a account, I want to all accounts, Search for a specific account, Find all a account
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RecruitBPM 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 | shStep 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 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.
What an agent can do with RecruitBPM API.
Create a account
List all accounts
Get a specific account
Update a account
GET STARTED
Not supported: Does not handle payments, communications, or crm — use for hr and recruiting only.
RecruitBPM recruitment and applicant tracking system API for managing accounts, activities, appointments, assessments, campaigns, candidates, and more. The API exposes 46 endpoints secured with bearer authentication.
Partially update a account
Delete a account
Patterns agents use RecruitBPM API for, with concrete tasks.
★ HR and Recruiting Operations
Use the RecruitBPM API to perform hr recruiting operations programmatically. The API provides 46 endpoints covering core functionality including create a account, list all accounts, get a specific account.
Call POST /accounts to create a account
Automated Account Management
Automate account operations by combining multiple RecruitBPM API endpoints. Agents can list all accounts and then get a specific account in a single workflow.
Call GET /accounts to list all accounts, then verify the result
AI Agent Integration via Jentic
AI agents discover and call RecruitBPM API 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 'create a account', load the operation schema, and execute with Jentic-managed credentials
46 endpoints — recruitbpm recruitment and applicant tracking system api for managing accounts, activities, appointments, assessments, campaigns, candidates, and more.
METHOD
PATH
DESCRIPTION
/accounts
Create a account
/accounts
List all accounts
/accounts/{accounts_id}
Get a specific account
/accounts/{accounts_id}
Update a account
/accounts/{accounts_id}
Partially update a account
/accounts/{accounts_id}
Delete a account
/activities
Create a activitie
/activities
List all activities
/accounts
Create a account
/accounts
List all accounts
/accounts/{accounts_id}
Get a specific account
/accounts/{accounts_id}
Update a account
/accounts/{accounts_id}
Partially update a account
Three things that make agents converge on Jentic-routed access.
Credential isolation
RecruitBPM API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create a account') and Jentic returns the matching RecruitBPM API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct RecruitBPM API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using RecruitBPM API through Jentic.
What authentication does the RecruitBPM API use?
The RecruitBPM API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I create a account with the RecruitBPM API?
Yes. Use the POST /accounts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the RecruitBPM API?
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 create a account through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a account'. Jentic returns the matching RecruitBPM API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the RecruitBPM API have?
The RecruitBPM API exposes 46 endpoints covering account, activity, apollo operations.
/accounts/{accounts_id}
Delete a account
/activities
Create a activitie
/activities
List all activities