RecruitBPM API

Name: RecruitBPM API 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.

Use for: I need to a account, I want to all accounts, Search for a specific account, Find all a account

Quickstart

Get started with RecruitBPM API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a account"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with RecruitBPM API API.

Create a account

List all accounts

Get a specific account

Update a account

Partially update a account

GET STARTED

Start building with RecruitBPM API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use RecruitBPM API 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 though Jentic?

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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Greenhouse

Alternative hr recruiting API

Choose Greenhouse when you need a different approach to hr recruiting operations

Alternative

Lever

Alternative hr recruiting API

Choose Lever when you need a different approach to hr recruiting operations

Complementary

Workday

Complementary hr recruiting API

Choose Workday when you need a complementary approach to hr recruiting operations

FAQs

Specific to using RecruitBPM API 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.