Float API

Name: Float API API
Brand: Float API
Availability: InStock

✓ Official Vendor SpecProductivityTask Managementbearer18 EndpointsREST

For Agents

Schedule people across projects, log time, manage tasks and departments, and read clients and time-off records on the Float resource-planning platform.

Connect the Float API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Float 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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 instance

Jentic 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 Float API API.

Schedule a named person to a project task with hours per day and a start and end date

Log time entries against a project task for billable or capacity reporting

Read each person's department, role, and weekly capacity to plan upcoming work

List and update projects, including their client, billable status, and budget

GET STARTED

Start building with Float API API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ Resource scheduling automation

Operations teams pipe upcoming project demand into Float by calling /tasks to allocate named people to projects with hours and date ranges. The same endpoint clears or shifts allocations as priorities change, so a single source of truth drives the live capacity view in Float without manual editing.

Allocate 5 hours per day on task T42 to person P101 from 2026-06-15 to 2026-06-19

Time tracking integration

Time tracking tools and timesheet workflows sync to Float through /logged-time, recording the actual hours each person spent on each project task. This drives utilization reports, billable rollups, and capacity comparisons against the schedule represented in /tasks.

Post a logged-time entry of 2 hours against task T42 for person P101 on 2026-06-09

Client and department reporting

Reporting tools join Float clients and departments with project records to build per-client utilization and per-department capacity dashboards. /clients, /departments, /projects, and /people together expose the dimensional data needed without requiring a separate data warehouse for resource planning.

List all projects for the Acme client, then read the assigned people, departments, and total scheduled hours for each project

AI agent scheduling assistant

An AI scheduling agent uses Float through Jentic to answer natural-language requests such as 'who is free for design work next Wednesday'. Jentic returns the right Float operation per intent so the agent traverses people, departments, time-off, and tasks without hard-coding the path layout, and the same skill works whether the request is a query or a write.

Find every designer in the Design department who is not on time off next Wednesday, then return their available hours

Key Endpoints

18 endpoints — 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.

METHOD

PATH

DESCRIPTION

GET

/people

List people in the team

GET

/projects

List projects

GET

/tasks

List task allocations

POST

/tasks

Create a new task allocation

POST

/logged-time

Log time against a task

GET

/time-off

List time-off requests

GET

/clients

List clients

GET

/people

List people in the team

GET

/projects

List projects

GET

/tasks

List task allocations

POST

/tasks

Create a new task allocation

POST

/logged-time

Log time against a task

GET

/time-off

Why though Jentic?

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

Credential isolation

Float bearer tokens are stored encrypted in the Jentic vault and injected into the Authorization header at execution time, so the agent context only ever sees the response payload.

Intent-based discovery

Agents search Jentic by intent such as 'allocate a person to a project' and Jentic returns the matching Float operation with its input schema, so the agent does not need to learn whether the relevant resource is /tasks, /projects, or /logged-time.

Time to first call

Direct Float integration: 1-2 days for token handling, response format negotiation, and date-range payload construction. Through Jentic: under 1 hour to search, load the schema, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Float API (full)

The full Float API spec covers many more resources than this curated subset

Pick the float-api spec when the agent needs phases, project stages, expenses, roles, statuses, or other resources outside the curated 18-endpoint surface

Alternative

Asana API

Asana focuses on task tracking rather than resource scheduling and capacity

Choose Asana when the workflow is task tracking and assignments rather than time-based capacity allocation

Alternative

Monday.com API

Monday.com is a flexible work-management platform that overlaps with Float for project planning

Pick Monday.com when the team uses it as the system of record; pick Float when the priority is people-by-day scheduling

Complementary

Toggl API

Toggl tracks the actual hours that can then be reported back against Float allocations

Use Toggl when the time tracking happens elsewhere and only the totals need pushing into Float as logged time

FAQs

Specific to using Float API API through Jentic.

What authentication does the Float API use?

The Float API uses HTTP bearer tokens. Through Jentic the bearer token is held in the encrypted vault and injected into the Authorization header at execution time, so the raw token never enters the agent context.

Can I schedule a person to a project with the Float API?

Yes. POST to /tasks with the person ID, project ID, hours per day, and start and end dates to create the allocation.

How do I log time against a Float task?

Call POST /logged-time with the person ID, task ID, date, and hours value. Logged time is reported alongside the scheduled hours from /tasks for utilization comparisons.

What are the rate limits for the Float API?

Float does not document a fixed global rate limit in the spec. Limits are applied per token. Treat 429 responses as the source of truth and back off using the Retry-After header.

How do I allocate a person through Jentic?

Search Jentic for 'allocate a person to a project', load the schema for POST /tasks, and execute the call with the IDs and date range. Install with pip install jentic and sign up at https://app.jentic.com/sign-up.

Does the Float API support both JSON and XML responses?

Yes. Float responds in JSON or XML depending on the Accept header. JSON is the default and the form Jentic generates input schemas for.