canonical: https://jentic.com/apis/busybusy.io/busybusy # BusyBusy REST API The BusyBusy REST API reads and writes workforce records for construction and field teams, covering equipment, employee certifications, project cost codes, and budget costs. It also exposes authoritative signature records and API key management for account integrations. Agents can keep an external system in sync with busybusy's time-tracking and job-costing data without operating the mobile app. ## For AI agents Read and write equipment, certifications, cost codes, and budget costs in busybusy, and retrieve authoritative signatures. Returns workforce and job-costing records for an agent to reconcile. ## Scope Does not handle payroll processing, GPS time clock capture, or scheduling. Use for reading and writing equipment, certification, and job-costing records only. ## Capabilities - Create, read, and update equipment records - Track employee certifications and record new ones - List and create project cost codes - Read and create budget cost entries for jobs - Retrieve authoritative signature records tied to time entries - List and create API keys for account integration access ## Use cases ### Agent-Driven Workforce Data Sync An AI agent keeps a project management or payroll system in step with busybusy by reading equipment, cost codes, and budget costs and creating records when jobs are set up. It reconciles what each system holds and files the differences, so field data captured in busybusy flows into back-office tools without manual re-entry. This suits recurring end-of-day or end-of-week reconciliation runs. Example prompt: Read the equipment and cost codes for a project, compare them with the payroll system, and create any missing records in busybusy ### Equipment and Cost Code Setup When a new job starts, teams create its equipment list and project cost codes in one pass rather than tapping through the app. The API accepts new equipment and cost code records and lets an integration read them back to confirm. Budget cost entries can be attached so job costing is ready before work begins. Example prompt: Create the equipment records and project cost codes for a new job, then add the matching budget cost entries ### Certification Compliance Tracking An agent reads employee certifications and flags which crew members are missing a required qualification for a job. It lists certifications on file and records new ones as workers complete training. This turns compliance checks into an automated report rather than a manual roster review. Example prompt: List the certifications on file for a crew, identify workers missing a required qualification, and record new certifications as they are earned ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/equipment` | List equipment records | | POST | `/equipment` | Create an equipment record | | GET | `/certification` | List certifications | | POST | `/certification` | Create a certification | | GET | `/cost-code` | List project cost codes | | GET | `/budget-cost` | List budget cost entries | | GET | `/authoritative-signature` | List authoritative signatures | | GET | `/api-key` | List API keys | ## Key resources - **Equipment** — Create, read, and update equipment records - **Certifications** — List and create employee certifications - **Cost codes** — List and create project cost codes - **Budget costs** — Read and create budget cost entries for jobs - **Authoritative signatures** — Retrieve signature records tied to time entries ## Why Jentic - **Setup:** Wiring the BusyBusy REST API by hand means provisioning an API key, learning each resource's record shape, and building create and read calls for equipment, certifications, and costs. Through Jentic you install once, import busybusy from the API Directory, store the key once, and your agent reads and writes those records. - **Permission scoping:** busybusy's endpoints act on collections, so you scope your agent by operation. A rule can allow reading equipment and certifications while withholding the create and update operations, so the agent reports without changing records. You choose which operations it may call, and every call is logged. - **Credential handling:** Your busybusy API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list equipment' or 'create a cost code', and Jentic returns the matching busybusy operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Clockify** — Time tracking API for projects, tasks, and timesheets - **Toggl Track** — Time tracking API with projects, tags, and reporting - **Deputy** — Workforce scheduling and shift management API ## FAQ ### What authentication does the BusyBusy REST API use? The BusyBusy REST API authenticates with an API key sent in the X-API-Key request header per its OpenAPI spec, generated from your busybusy account. Through Jentic the key is held encrypted by your own Jentic One instance and attached at call time, so it never reaches the agent's context. ### Can I create equipment and cost codes with the BusyBusy REST API? Yes. The API exposes create operations for equipment, certifications, cost codes, and budget costs, alongside read operations to confirm what exists. An agent can set up a job's records and read them back in the same run. ### What are the rate limits for the BusyBusy REST API? The OpenAPI spec does not specify rate limits. Check the busybusy developer documentation at https://api.busybusy.io/docs for current limits and usage guidance. ### Can I limit what my agent is allowed to do with the BusyBusy REST API? Yes. The endpoints act on collections rather than individual records in the path, so scope your agent by operation: allow reading equipment and certifications while withholding create and update. You choose which operations it may call, and every call is logged. ### How do I sync busybusy records through Jentic? Search Jentic for 'list equipment' or 'create a cost code', add the BusyBusy REST API from the directory, and store your key once. Your agent then reads and writes the records your rule permits. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a busybusy MCP server? You don't need an MCP server to give your agent the BusyBusy REST API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent reads and writes workforce records. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.