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

# Avionte BOLD Front Office API

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.

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

## Scope

Does not handle payroll tax filing or benefits administration - use it for recruiting, staffing, and placements only.

## Capabilities

- 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

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

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

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

Example prompt: Call GET `/v1/talent/{talentId}/all-tags`, then POST `/v1/talent-source` to record the source

## Key endpoints

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

## Key resources

- **Talent** — Candidate records, their tags, and sources
- **Jobs** — Open jobs and their required skills
- **Placements** — Records that place a candidate into a job
- **Timesheets** — Hours logged for placed workers
- **Companies** — Client companies and their contacts behind each placement

## AI readiness

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.

- **Score:** 53 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 44 / 100
  - Developer Experience & Jentic Compatibility: 80 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 43 / 100
  - Security: 63 / 100
  - AI Discoverability: 70 / 100
- **View full report:** https://jentic.com/apis/avionte.com/avionte/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

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

- **Lever** — Alternative applicant tracking API
- **Workable** — Alternative recruiting and hiring API
- **BambooHR** — Complementary HR information API

## FAQ

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