RecruitBPM API

Name: RecruitBPM API
Brand: RecruitBPM API
Availability: InStock

✓ Official Vendor SpecHR recruitingRecruiting Atsbearer46 EndpointsREST

For Agents

Programmatically create a account, list all accounts. Covers 46 operations with bearer authentication.

Install Jentic One Beta

Connect the RecruitBPM API to your agent

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Frecruitbpm.com%2Frecruitbpm" | sh

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%2Frecruitbpm.com%2Frecruitbpm" | 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 RecruitBPM API.

Create a account

List all accounts

Get a specific account

Update a account

GET STARTED

Start building with RecruitBPM API

Explore with Jentic

View OpenAPI Document

Use Cases

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

Key Endpoints

46 endpoints — recruitbpm recruitment and applicant tracking system api for managing accounts, activities, appointments, assessments, campaigns, candidates, and more.

METHOD

PATH

DESCRIPTION

POST

/accounts

Create a account

GET

/accounts

List all accounts

GET

/accounts/{accounts_id}

Get a specific account

PUT

/accounts/{accounts_id}

Update a account

PATCH

/accounts/{accounts_id}

Partially update a account

DELETE

/accounts/{accounts_id}

Delete a account

POST

/activities

Create a activitie

GET

/activities

List all activities

POST

/accounts

Create a account

GET

/accounts

List all accounts

GET

/accounts/{accounts_id}

Get a specific account

PUT

/accounts/{accounts_id}

Update a account

PATCH

/accounts/{accounts_id}

Partially update a account

DELETE

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the RecruitBPM API by hand means handling its bearer token auth, pointing at the api.recruitbpm.com host, and managing requests yourself. Through Jentic you install once, import the RecruitBPM API from the API Directory, store the token once, and your agent calls it.

Permission scoping

RecruitBPM puts the account id in the URL path (/accounts/{accounts_id}), so a rule can pin your agent to specific accounts. You choose the operations it may call, so writes like updating or deleting an account are only included if you add them.

Credential isolation

Your RecruitBPM 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 an account' or 'list activities', and Jentic returns the matching RecruitBPM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

RecruitBPM API

Connect the RecruitBPM API to your agent

Capabilities

Start building with RecruitBPM API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs