canonical: https://jentic.com/apis/recruitbpm.com/recruitbpm

# RecruitBPM API

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.

## For AI agents

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

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Create a account
- List all accounts
- Get a specific account
- Update a account
- Partially update a account
- Delete a account

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create a account', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Account** — Operations related to Account
- **Activity** — Operations related to Activity
- **Apollo** — Operations related to Apollo
- **Appointment** — Operations related to Appointment
- **Approver** — Operations related to Approver

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the RecruitBPM API?

Yes. Because you run Jentic One yourself, your own rules decide which RecruitBPM operations and credentials the agent may use. Since RecruitBPM puts the account id in the URL path (`/accounts/{accounts_id}`), you can pin the agent to specific accounts, and you choose which operations it may call. That means read calls like GET /accounts can be allowed while writes such as PUT, PATCH, or DELETE on an account are included only if you add them.