The Float API is the resource-planning interface for the Float scheduling platform, focused on the core entities a project planner needs: people, projects, tasks, departments, clients, time off, and logged time. This is the curated subset of Float's REST surface, with each endpoint mapping cleanly to a single resource. It supports both JSON and XML responses and uses bearer token authentication.
18 endpointsJentic publishes the only available OpenAPI specification for Float API, keeping it validated and agent-ready. This is the full Float resource-planning API surface, covering people, departments, roles, statuses, projects, project stages, project tasks, phases, project expenses, clients, accounts, public and team holidays, time off, time-off types, and reports for both people and projects. It is the larger sibling to the curated Float spec and gives agents reach into every entity Float exposes for scheduling, allocation, and reporting.
86 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffloat.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffloat.com" | 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.