busybusy REST API
✓ Official Vendor SpecHR recruitingEmployee ManagementapiKey10 EndpointsREST
For Agents
Read and create time entries, projects, members, cost codes, and certifications for a construction company running on busybusy.
Use for: I need to pull last week's time entries for payroll, Create a time entry for a worker on a specific project, List active projects in busybusy, Create a new project in busybusy
Not supported: Does not handle payroll execution, equipment management, or financial accounting — use for busybusy time tracking, projects, members, and certification data only.
The busybusy REST API exposes time tracking, project management, and safety data for construction companies that run on busybusy. It covers time entries, projects, members, cost codes, certifications, and API keys, with read access on every resource and create access on time entries, projects, certifications, and API keys. It is used to sync busybusy data into payroll, ERP, and BI systems and to create time entries from external tools. Authentication is a Bearer API key sent in the Authorization header.
Install Jentic One Beta
Connect the busybusy REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the busybusy REST 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 busybusy REST API.
List time entries across the company via GET /time-entry
Create new time entries via POST /time-entry
List and create projects via /project
List members of the company via GET /member
Read the company's cost codes via GET /cost-code
List and rotate API keys via /api-key
List and create employee certifications via /certification
Use Cases
Patterns agents use busybusy REST API for, with concrete tasks.
★ Payroll-ready time entry sync
Pull all time entries for a pay period from /time-entry and route them to a payroll system. The endpoint returns the worker, project, cost code, start, and end timestamps needed to calculate wages and allocate labour cost across jobs. Suitable for construction firms that want busybusy as the system of record but pay through QuickBooks, ADP, or similar.
GET /time-entry filtered to the previous pay period, transform the records, and post them to the payroll system.
Project and cost code setup
Create new projects in busybusy when a new job is won and read the company's cost codes so external tools can present consistent options to the field. POST /project creates a project; GET /cost-code returns the available codes that can be tagged on time entries.
POST /project for the newly awarded job, then GET /cost-code so any downstream tool can present the right codes when workers clock in.
Workforce and safety records
Maintain the list of company members and their safety certifications. GET /member lists the workforce; /certification supports both reading existing certifications and posting new ones when training is completed. Useful for safety officers who track OSHA-style certifications across crews.
GET /member to list the workforce, then POST /certification for each worker who completed a recent safety course.
AI agent jobsite assistant via Jentic
An AI assistant can answer foreman questions like 'who is currently clocked in on the Smith project?' or 'how many hours has crew B logged this week?' by calling busybusy reads through Jentic. Jentic vaults the busybusy API key and issues scoped, short-lived access for each call.
Search Jentic for 'list busybusy time entries', load the GET /time-entry schema, execute it filtered to the current week and project, and summarise the results for the foreman.
Key Endpoints
10 endpoints — the busybusy rest api exposes time tracking, project management, and safety data for construction companies that run on busybusy.
METHOD
PATH
DESCRIPTION
GET
/time-entry
List time entries
POST
/time-entry
Create a time entry
GET
/project
List projects
POST
/project
Create a project
GET
/member
List members
GET
/cost-code
List cost codes
POST
/certification
Create a certification
GET
/api-key
List API keys
GET
/time-entry
List time entries
POST
/time-entry
Create a time entry
GET
/project
List projects
POST
/project
Create a project
GET
/member
List members
GET
/cost-code
List cost codes
POST
/certification
Create a certification
GET
/api-key
List API keys
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The busybusy Bearer API key is stored encrypted in the Jentic vault. Agents receive a scoped, short-lived token per operation — the raw key never enters the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'list busybusy time entries' or 'create a busybusy project') and Jentic returns the matching operation with its full request schema, so the agent calls the correct endpoint without reading busybusy docs.
Time to first call
Direct busybusy integration: a day or two for time-entry sync and project setup. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using busybusy REST API through Jentic.
What authentication does the busybusy REST API use?
Requests carry an Authorization header containing a Bearer API key issued from the busybusy account. Through Jentic, the key is encrypted in the vault and a scoped, short-lived token is issued per operation, so the raw key never enters the agent's context.
Can I create a busybusy time entry programmatically?
Yes — POST /time-entry with the worker, project, optional cost code, and start/end timestamps creates a time entry. This is the path used by external clock-in tools that mirror data into busybusy as the system of record.
How do I pull all time entries for a pay period?
GET /time-entry returns time entries for the company; filter the results to the pay period in your client and feed them to your payroll process. Pair with /member and /cost-code to label the records consistently.
Does the busybusy API expose safety certifications?
Yes. GET /certification lists certifications and POST /certification creates one. This is suitable for tracking OSHA-style safety training across crews and members.
What are the rate limits for the busybusy REST API?
The OpenAPI spec does not declare explicit limits. busybusy applies per-account quotas documented at https://api.busybusy.io/docs/apiv3.html — handle 429 responses with retry-with-backoff for bulk time-entry pulls.
How do I list busybusy time entries through Jentic?
Run `pip install jentic` and search for 'list busybusy time entries'. Jentic returns the GET /time-entry operation, you load its schema, and execute the call — credentials stay in the Jentic vault.
GET STARTED