Bilflo API
★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting Atsbearer24 EndpointsREST
For Agents
Manage staffing-agency clients, contract jobs, contacts, addresses, and agreements in Bilflo, and read company-settings reference data and dashboards.
Use for: I need to create a new staffing client in Bilflo, Update the address on file for client 8821, Post a new contract job for a placed candidate, Terminate an active contract job in Bilflo
Not supported: Does not handle candidate sourcing, applicant tracking pipelines, or payroll disbursement — use for Bilflo agency client, contract job, and back-office configuration only.
Jentic publishes the only available OpenAPI specification for Bilflo API, keeping it validated and agent-ready. Bilflo is a back-office platform for staffing and recruitment agencies, exposing endpoints for client records, contract jobs, client contacts, addresses, agreements, and configurable company settings such as workers' comp codes, payment terms, and pay-bill items. The API also covers dashboards and custom fields used to extend the underlying client and job model. Authentication is by bearer token, scoped to the agency's Bilflo tenant.
Install Jentic One Beta
Connect the Bilflo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bilflo 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Bilflo API.
List, create, and update agency clients via /v1/Clients
Add client contacts, addresses, and agreements through dedicated POST endpoints
Create and update contract jobs and terminate them with /v1/ContractJobs/terminate
Read configured workers' comp codes, payment terms, and states from /v1/CompanySettings
Enumerate pay-bill items used to price contract roles
List custom field definitions and their available items via /v1/CustomFields
Create and read agency dashboards through /dash/v1/Dashboards
Use Cases
Patterns agents use Bilflo API for, with concrete tasks.
★ Onboard a New Staffing Client
Staffing agencies onboard a new client by creating the company record, adding the primary billing and worksite addresses, capturing the day-one contact, and recording the signed agreement. Bilflo exposes POST /v1/Clients, /v1/Clients/contact, /v1/Clients/address, and /v1/Clients/agreements as the four-step pipeline. Running this through the API removes manual rekeying when the agency captures clients via a CRM or a sales-form intake.
Call POST /v1/Clients, then POST /v1/Clients/contact, /v1/Clients/address, and /v1/Clients/agreements with the matching clientId
Place and Terminate Contract Workers
Recruiters track placements as contract jobs in Bilflo — opening a job when a candidate starts, updating it for rate or extension changes, and terminating it when the contract ends. POST /v1/ContractJobs creates the job, PUT /v1/ContractJobs/{jobId} updates rates or end dates, and POST /v1/ContractJobs/terminate closes it cleanly so downstream pay-bill runs are accurate.
Call POST /v1/ContractJobs with clientId, candidate details and bill rate, then later POST /v1/ContractJobs/terminate with the jobId and termination date
Reference Data for Onboarding Forms
Internal tools that build staffing onboarding forms need the agency's configured reference lists — workers' comp codes, payment terms, pay-bill items, and US states. Bilflo's /v1/CompanySettings endpoints expose each list so the form keeps in sync with the back-office configuration without hard-coding values. /v1/CustomFields and /v1/CustomFields/items pull custom-field definitions for any extended attributes.
Call GET /v1/CompanySettings/workersCompCodes, /v1/CompanySettings/paymentTerms, /v1/CompanySettings/payBillItems and merge into the onboarding form dropdowns
Agent-Driven Staffing Operations via Jentic
An AI back-office agent connected through Jentic answers 'add Acme Corp as a new client and link John Smith as the primary contact' by chaining the Bilflo client and contact create operations. The bearer token sits in the Jentic vault scoped to the agency tenant, so the agent never sees the raw secret and can repeat the workflow for every new client without bespoke glue code. Use cases extend to placement creation and termination flows.
Search Jentic for 'create a staffing client', load Bilflo POST /v1/Clients, execute, then load /v1/Clients/contact and execute with the returned clientId
Key Endpoints
24 endpoints — jentic publishes the only available openapi specification for bilflo api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/v1/Clients
List staffing clients
POST
/v1/Clients
Create a new client record
POST
/v1/Clients/contact
Add a contact to a client
POST
/v1/Clients/agreements
Add a client agreement
POST
/v1/ContractJobs
Create a contract job placement
POST
/v1/ContractJobs/terminate
Terminate an existing contract job
GET
/v1/CompanySettings/workersCompCodes
List workers' comp codes
GET
/v1/CompanySettings/payBillItems
List pay-bill items
GET
/v1/Clients
List staffing clients
POST
/v1/Clients
Create a new client record
POST
/v1/Clients/contact
Add a contact to a client
POST
/v1/Clients/agreements
Add a client agreement
POST
/v1/ContractJobs
Create a contract job placement
POST
/v1/ContractJobs/terminate
Terminate an existing contract job
GET
/v1/CompanySettings/workersCompCodes
List workers' comp codes
GET
/v1/CompanySettings/payBillItems
List pay-bill items
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Bilflo bearer tokens are stored encrypted in the Jentic vault scoped per agency tenant. Agents call operations by name and Jentic attaches the Authorization header at execution time so the raw secret never enters the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'create a staffing client', 'terminate a contract job') and Jentic returns the matching Bilflo operation with parameters typed, so the agent fills only the business values it needs to send.
Time to first call
Direct Bilflo integration: 1-2 days mapping the client, contact, address, agreement, and contract-job pipeline. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Bilflo API through Jentic.
Why is there no official OpenAPI spec for Bilflo API?
Bilflo exposes its API surface via Swagger UI at api.bilflo.com/swagger but does not publish the underlying OpenAPI document for distribution. Jentic generates and maintains a structured OpenAPI specification so AI agents and developers can call Bilflo API via tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Bilflo API use?
Bilflo uses HTTP bearer authentication. The token is issued from the Bilflo platform and scoped to the agency tenant. Through Jentic, the token is held encrypted in the vault and attached to outbound calls so the raw secret never enters the agent's context.
Can I create a contract job placement through the API?
Yes. POST /v1/ContractJobs accepts the client ID, role, candidate details, and bill/pay rates, returning the job ID. Update later with PUT /v1/ContractJobs/{jobId}, and close out with POST /v1/ContractJobs/terminate when the contract ends.
What are the rate limits for the Bilflo API?
Bilflo does not publish rate limits in this OpenAPI spec — limits are enforced per agency plan. For high-volume reference-data syncs, cache the /v1/CompanySettings results, since workers' comp codes and pay-bill items change infrequently.
How do I add a new client through Jentic?
Run `pip install jentic`, then `await client.search('create a staffing client')`, `await client.load(...)` for Bilflo POST /v1/Clients, and `await client.execute(...)` with the client name and details. Chain into /v1/Clients/contact and /v1/Clients/address for contacts and addresses.
Are custom fields supported on clients and contract jobs?
Yes. GET /v1/CustomFields returns the agency's custom field definitions and GET /v1/CustomFields/items returns the selectable values for picklist-style fields. Use these to render dynamic forms or validate values before posting client and contract-job records.
GET STARTED