Avionte BOLD Front Office API
53
AI ReadinessFoundational (C)53/100
Community OpenAPI document · agent-readyHR recruitingRecruiting AtsapiKey, bearer205 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Run recruiting and staffing with the Avionte BOLD Front Office API: talent, jobs, placements, timesheets, and contacts. Secured with an API key and a bearer token.
Use for: Find talent for a job opening, Add a placement in Avionte, Create a timesheet for a worker, List the tags on a talent record
Not supported: Does not handle payroll tax filing or benefits administration - use it for recruiting, staffing, and placements only.
The BOLD Front Office API is the recruiting and staffing core of Avionte's platform. An agent can work with talent records and their tags, search jobs and attach required skills, add talent sources, create placements, and log timesheets. Companies, contacts, branches, and departments organise the staffing data behind every placement, so a recruiting workflow can run end to end.
Install Jentic One Beta
Connect the BOLD Front Office API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BOLD Front Office 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.
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%2Favionte.com%2Favionte" | 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%2Favionte.com%2Favionte" | 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 BOLD Front Office API.
Look up talent records and their tags
Search jobs and attach required skills
Add talent sources
Create placements
Log timesheets for placed workers
Use Cases
Patterns agents use BOLD Front Office API for, with concrete tasks.
★ Fill an open job
Move a candidate from sourcing to placed. The agent pulls talent ids, confirms the job's required skills, and records the placement once a match is agreed.
Call GET /v1/talents/ids/{page}/{pageSize}, then POST /v1/placement to record the hire
Log billable time
Capture hours for placed workers. The agent creates timesheets so staffing hours flow into billing and payroll downstream.
Call POST /v1/timesheets with the worker's hours
Enrich candidate records
Keep talent data clean and searchable. The agent reads the tags on a talent record and registers where the candidate came from.
Call GET /v1/talent/{talentId}/all-tags, then POST /v1/talent-source to record the source
Key Endpoints
205 endpoints — the bold front office api is the recruiting and staffing core of avionte's platform.
METHOD
PATH
DESCRIPTION
GET
/v1/talent/{talentId}/all-tags
Get all tags on a talent record
GET
/v1/talents/ids/{page}/{pageSize}
Get a page of talent ids
POST
/v1/job/{jobId}/skills/add
Add required skills to a job
POST
/v1/talent-source
Add a talent source
POST
/v1/timesheets
Create a timesheet
POST
/v1/placement
Add a placement
GET
/v1/contact/activity-types
Get all contact activity types
GET
/v1/work-comp
Get workers comp codes
GET
/v1/talent/{talentId}/all-tags
Get all tags on a talent record
GET
/v1/talents/ids/{page}/{pageSize}
Get a page of talent ids
POST
/v1/job/{jobId}/skills/add
Add required skills to a job
POST
/v1/talent-source
Add a talent source
POST
/v1/timesheets
Create a timesheet
POST
/v1/placement
Add a placement
GET
/v1/contact/activity-types
Get all contact activity types
GET
/v1/work-comp
Get workers comp codes
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
B
BOLD Front Office API
- Foundational (C)53/100
44
Foundational Compliance80
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience43
Agent Usability63
Security70
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
44
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
76%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
80
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
44%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
76%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
71%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
54%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
70
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
70%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the BOLD Front Office API by hand means obtaining an API key and a bearer token, pointing at the api.avionte.com host, and shaping talent, job, and placement requests yourself. Through Jentic you install once, import Avionte from the Jentic API Directory, store the credentials once, and your agent calls it.
Permission scoping
Avionte puts the talent and job ids in the URL path (/v1/talent/{talentId}/all-tags), so a rule can pin your agent to one talent record or job and nothing else. You choose which operations it may call, so state-changing ones like adding a placement or creating a timesheet are not included unless you add them.
Credential isolation
Your Avionte API key and bearer token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add a placement' or 'find talent for a job', and Jentic returns the matching Avionte operation with its input schema so the agent calls the right endpoint without browsing the reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using BOLD Front Office API through Jentic.
What authentication does the BOLD Front Office API use?
The BOLD Front Office API uses an API key in the x-api-key header along with a bearer token in the Authorization header. Through Jentic both credentials are stored encrypted in your Jentic One instance and injected at execution time, so the raw secrets never enter the agent context.
What can an agent do with the BOLD Front Office API?
It can look up talent records and their tags, search jobs and attach required skills, add talent sources, create placements, and log timesheets. Companies and contacts organise the staffing data. Responses are structured so an agent can act on them directly.
Can I create placements through the BOLD Front Office API?
Yes. The API lets an agent add a placement once a candidate and job are matched, and log the timesheets that follow for the placed worker.
What are the rate limits for the BOLD Front Office API?
Rate limits are not specified in the OpenAPI spec. Check the Avionte documentation for current limits. Through Jentic, retries are handled in the execution layer.
How many endpoints does the BOLD Front Office API have?
The BOLD Front Office API exposes 205 endpoints covering talent, jobs, placements, timesheets, companies, and contacts.
Can I limit what my agent is allowed to do with the BOLD Front Office API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Avionte operations your agent may call. Because Avionte puts the talent and job ids in the URL path, such as /v1/talent/{talentId}/all-tags, a rule can pin the agent to a single talent record and nothing else. You also choose which operations it may call, so state-changing ones like POST /v1/placement to add a placement are excluded unless you add them.
GET STARTED