Beebole API

Name: Beebole API API
Brand: Beebole API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask Managementbasic57 EndpointsREST

For Agents

Log billable time, manage projects and subprojects, track absences, and run timesheet submit-approve-lock workflows through Beebole's 57 time-tracking endpoints.

Quickstart

Get started with Beebole API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"log a project time entry"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Beebole API API.

Log a time entry against a person, project, subproject, and task with hours and a date

Submit a person's timesheet for approval, then approve, reject, or lock it

Create projects and subprojects with billable status, currency, and budget settings

Maintain the people roster with activate and deactivate operations rather than hard delete

GET STARTED

Start building with Beebole API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Beebole API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Beebole API, keeping it validated and agent-ready. Beebole is a project time tracking platform used by services firms, agencies, and consultancies to log billable hours, manage projects and subprojects, track absences, and run timesheet approval workflows. The API exposes 57 POST operations grouped by domain (time entries, projects, people, companies, tasks, absences, groups), each endpoint following a verb path like /time_entry/create or /project/list, secured by HTTP Basic auth using the account's API token as the username.

Use Cases

Patterns agents use Beebole API API for, with concrete tasks.

★ Weekly timesheet submission and approval

Services firms run a weekly cycle where staff log hours, submit for approval, and managers approve or reject before the timesheet is locked for billing. Beebole exposes /time_entry/create for logging, /time_entry/submit, /time_entry/approve, /time_entry/reject, and /time_entry/lock to drive the cycle programmatically. Approved and locked entries can then be pulled via /time_entry/export for invoicing.

Submit person 1124's timesheet for week ending 2026-06-08 and then approve all pending entries on projects flagged client_billable

Project and budget setup at kickoff

Agencies and consultancies create a project record at kickoff with billable rate, currency, budget, and team assignment so time logged against it can be reported against scope. The API's /project/create, /subproject/create, /task/create, and /group operations let an integration provision the project tree from a CRM-won deal in one batch, ready for staff to log hours.

Create a project Q3 Migration billed in EUR with a 200-hour budget, three subprojects Discovery, Build, and Cutover, and the engineering group assigned

Absence and capacity tracking

HR and operations track vacation, sick, and other absence types alongside billable time so capacity planning reflects who is actually available. /absence/create logs an absence against a person and date range, /absence/list reports across the team, and the activate and deactivate flags let admins retire policies without losing historical records.

Record a vacation absence for person 5512 from 2026-07-14 to 2026-07-18 and confirm it does not overlap an existing absence

AI agent integration for time-tracking workflows

Operations leads use AI agents through Jentic to handle nudge-and-approve workflows: remind staff to submit timesheets, auto-approve recurring entries, and pull weekly reports for billing. The agent searches Jentic for the right Beebole operation, loads the schema, and executes with the API token held in the Jentic vault, so the token never enters the agent transcript.

Through Jentic, find Beebole's time entry list operation and return all unsubmitted entries from last week so the agent can nudge each person to submit

Key Endpoints

57 endpoints — jentic publishes the only available openapi specification for beebole api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/time_entry/create

Log a time entry

POST

/time_entry/submit

Submit a person's timesheet

POST

/time_entry/approve

Approve submitted time entries

POST

/time_entry/lock

Lock approved time entries for billing

POST

/time_entry/export

Export time entries for invoicing

POST

/project/create

Create a project

POST

/person/create

Create a person

POST

/absence/create

Record an absence

POST

/time_entry/create

Log a time entry

POST

/time_entry/submit

Submit a person's timesheet

POST

/time_entry/approve

Approve submitted time entries

POST

/time_entry/lock

Lock approved time entries for billing

POST

/time_entry/export

Export time entries for invoicing

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Beebole API token is stored encrypted in the Jentic vault. Jentic constructs the HTTP Basic Authorization header (token as username, x as password) at execution time so the token never enters agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. log a time entry or submit my timesheet) and Jentic returns the matching Beebole operation with its input schema, so the agent calls /time_entry/create or /time_entry/submit without browsing docs.

Time to first call

Direct Beebole integration: 1-2 days to wire the verb-path call style and approval state machine. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Toggl

Time tracking with a lighter solo and small-team footprint than Beebole's approval-and-lock workflow.

Choose Toggl when the agent only needs to start, stop, and report timers without running a formal timesheet approval cycle.

Alternative

Clockify

Time tracking platform with a free tier and broader integrations than Beebole.

Choose Clockify when the agent prioritises a free-tier or wide third-party integration surface over Beebole's approval and lock workflow.

Complementary

ClickUp

Project and task management often paired with a dedicated time-tracker for billable hours.

Use ClickUp alongside Beebole when the agent manages tasks and sprint scope in ClickUp but logs billable time in Beebole for invoicing.

FAQs

Specific to using Beebole API API through Jentic.

Why is there no official OpenAPI spec for Beebole API?

Beebole does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Beebole API via structured 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 Beebole API use?

Beebole uses HTTP Basic authentication where the API token is sent as the username and the literal string x as the password. Jentic stores the token in its vault and constructs the Authorization header at execution time so the token never appears in agent context.

Can I run a timesheet approval workflow with the Beebole API?

Yes. The /time_entry resource exposes submit, approve, reject, lock, and unlock operations alongside create. A typical flow is /time_entry/create over the week, /time_entry/submit on Friday, /time_entry/approve by the manager, then /time_entry/lock once payroll has been run.

How do I export approved time entries for billing through Jentic?

Search Jentic for export Beebole time entries to find POST /time_entry/export. Load the schema and execute with a date range, person or project filters, and the desired export format. The response can be piped into the agent's invoice generator or a BI ingest job.

Does the Beebole API support absence and vacation tracking?

Yes. POST /absence/create records an absence against a person and date range. The /absence/list, /absence/activate, and /absence/deactivate operations let an integration manage absence policies and read aggregate availability without hard-deleting historical records.

Why does the Beebole API use POST for read operations like list?

Beebole's API design uses POST with a JSON body for every operation, including reads. Filters and pagination parameters are sent in the request body rather than the query string, which keeps complex filter shapes typed but means tools that expect GET-for-read need adapter logic. Jentic's schema-driven execution handles this transparently.

What are the rate limits for the Beebole API?

Beebole does not publish explicit rate limits in the spec. Production integrations should back off on HTTP 429 responses with exponential delay and contact Beebole support to confirm headroom for high-volume export or sync jobs.