The Float connector lets your AI agent act in each user's Float account. Each user connects their own Float access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 70 tools.
- Tools
- 70
- What they doRead · write · destructive
- 44 · 23 · 344 read23 write3 destructive
- Users sign in with
- Access token
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the Float connection
In AgentKit > Connections, create a Float connection. The name you give it is the
connection_nameyour code passes. See Configure connections.Authorize a user and make your first call
quickstart.mts import { ScalekitClient } from '@scalekit-sdk/node'import 'dotenv/config'import { createInterface } from 'node:readline/promises'const scalekit = new ScalekitClient(process.env.SCALEKIT_ENVIRONMENT_URL,process.env.SCALEKIT_CLIENT_ID,process.env.SCALEKIT_CLIENT_SECRET,)const actions = scalekit.actionsconst connector = 'float'const identifier = 'user_123'// Generate an authorization link for the userconst { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })console.log('Authorize Float:', link)const rl = createInterface({ input: process.stdin, output: process.stdout })await rl.question('Press Enter after authorizing...')rl.close()// Make your first callconst result = await actions.executeTool({connector,identifier,toolName: 'float_accounts_list',toolInput: {},})console.log(result)Terminal window npx tsx quickstart.mtsquickstart.py import osfrom scalekit import ScalekitClientfrom dotenv import load_dotenvload_dotenv()scalekit_client = ScalekitClient(env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),client_id=os.getenv("SCALEKIT_CLIENT_ID"),client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),)actions = scalekit_client.actionsconnection_name = "float"identifier = "user_123"# Generate an authorization link for the userlink_response = actions.get_authorization_link(connection_name=connection_name,identifier=identifier,)print("Authorize Float:", link_response.link)input("Press Enter after authorizing...")# Make your first callresult = actions.execute_tool(tool_input={},tool_name="float_accounts_list",connection_name=connection_name,identifier=identifier,)print(result)Terminal window python quickstart.pyEach user opens the link once and enters their Float credentials there. See Authorize a user for the full flow and statuses.
Tools
Pass the exact name toexecute_toolfloat_account_getRetrieve a single account from your Float account by ID.Read-onlyGet Account
Retrieve a single account from your Float account by ID. Returns the account record with fields such as account_id, name, email, timezone, avatar, account_type, access, department_filter. Use float_account_get when you already have the ID; use float_accounts_list to search or browse. Requires account_id, typically from float_accounts_list.
Inputs
account_idintegerrequired- The account ID. Example: 123
expandstring- Use `people_id` to return an additional `people_id` field that can reference a record on `/people`, or `null` if a guest. Example: Expand
float_accounts_listList accounts in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Accounts
List accounts in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of account records with fields such as account_id, name, email, timezone, avatar, account_type, access, department_filter. Use float_accounts_list to browse or filter accounts; use float_account_get to fetch one account by its ID.
Inputs
expandstring- Use `people_id` to return an additional `people_id` field that can reference a record on `/people`, or `null` if a guest. Example: Expand
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50
float_allocation_getRetrieve a single allocation from your Float account by ID.Read-onlyGet Allocation
Retrieve a single allocation from your Float account by ID. Returns the task record with fields such as task_id, root_task_id, parent_task_id, project_id, phase_id, start_date, end_date, start_time. Use float_allocation_get when you already have the ID; use float_allocations_list to search or browse. Requires task_id, typically from float_allocations_list.
Inputs
task_idintegerrequired- The allocation as a task ID. Example: 123
float_allocations_listList allocations in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Allocations
List allocations in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of task records with fields such as task_id, root_task_id, parent_task_id, project_id, phase_id, start_date, end_date, start_time. Use float_allocations_list to browse or filter allocations; use float_allocation_get to fetch one allocation by its ID.
Inputs
billableinteger- Filter response on `0` = non-billable or `1` = billable. Example: 1
client_idinteger- A client ID associated with projects to filter the response on. Example: 123
end_datestring- End of date range in format YYYY-MM-DD. Must be used together with `start_date`. Will be inclusive of `repeat_end_date` date. Example: 2025-01-31
expandstring- Use `task_days` to return an additional array of dates `[YYYY-MM-DD]` calculated by taking into account the date range & `repeat_end_date` of each `task_id` plus holidays & availability of all associated people. (e.g. weekends and holidays dates will not be returned). By default, a date is returned if any person is available, the `people_id` filter may be used to limit this. The `start_date` and `end_date` filters must always be provided. Example: Expand
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
modified_sincestring- Datetime in either `YYYY-MM-DD hh:mm:ss` or as a Unix timestamp in seconds to filter on all records with an equal or later `modified` timestamp. Example: 2025-01-31
pageinteger- The page number of the page of results to return, default `1`.default
1 people_idinteger- A people ID to filter the response on. Example: 123
per_pageinteger- The number of items per page, max is `200`.default
50 phase_idinteger- A phase ID associated with a project to filter the response on. Example: 123
project_idinteger- A project ID to filter the response on. Example: 123
repeat_stateinteger- Filter response on the repeat state. `0` = No repeat, `1` = Weekly, `2` = Monthly, `3` = Every two weeks, `4` = Every three weeks, `5` = Every six weeks, `6` = Every two months, `7` = Every three months, `8` = Every six months, `9` = Yearly. Example: 1
sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
start_datestring- Start of date range in format YYYY-MM-DD. Must be used together with `end_date`. Example: 2025-01-31
statusinteger- Filter response on the Status. `1` = Tentative, `2` = Confirmed, `3` = Complete" Example: 1
task_meta_idinteger- A project task ID to filter the response on. Example: 123
float_client_getRetrieve a single client from your Float account by ID.Read-onlyGet Client
Retrieve a single client from your Float account by ID. Returns the client record with fields such as client_id, name. Use float_client_get when you already have the ID; use float_clients_list to search or browse. Requires client_id, typically from float_clients_list.
Inputs
client_idintegerrequired- The client's ID. Example: 123
float_clients_listList clients in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Clients
List clients in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of client records with fields such as client_id, name. Use float_clients_list to browse or filter clients; use float_client_get to fetch one client by its ID.
Inputs
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50
float_currencies_listList currencies in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Currencies
List currencies in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of currency records with fields such as id, source_currency, target_currency, fx_rates. Use float_currencies_list to browse or filter currencies; use float_currency_get to fetch one currency by its ID.
Inputs
expandstring- Comma-delimited values expands the response with additional fields: `fx_rates`. Example: Expand
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50
float_currency_getRetrieve a single currency from your Float account by ID.Read-onlyGet Currency
Retrieve a single currency from your Float account by ID. Returns the currency record with fields such as id, source_currency, target_currency, fx_rates. Use float_currency_get when you already have the ID; use float_currencies_list to search or browse. Requires currency_id, typically from float_currencies_list.
Inputs
currency_idintegerrequired- The currency record's ID. Example: 123
expandstring- Comma-delimited values expands the response with additional fields: `fx_rates`. Example: Expand
float_department_getRetrieve a single department from your Float account by ID.Read-onlyGet Department
Retrieve a single department from your Float account by ID. Returns the department record with fields such as department_id, parent_id, name. Use float_department_get when you already have the ID; use float_departments_list to search or browse. Requires department_id, typically from float_departments_list.
Inputs
department_idintegerrequired- The department's id. Example: 123
float_departments_listList departments in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Departments
List departments in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of department records with fields such as department_id, parent_id, name. Use float_departments_list to browse or filter departments; use float_department_get to fetch one department by its ID.
Inputs
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50
float_logged_time_getRetrieve a single logged time entry from your Float account by ID.Read-onlyGet Logged Time Entry
Retrieve a single logged time entry from your Float account by ID. Returns the loggedtime record with fields such as logged_time_id, people_id, date, reference_date, hours, billable, notes, project_id. Use float_logged_time_get when you already have the ID; use float_logged_times_list to search or browse. Requires logged_time_id, typically from float_logged_times_list.
Inputs
logged_time_idstringrequired- Unique ID of the specific logged time entry to be retrieved. Example: 123
float_logged_times_listList logged time entries in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Logged Time Entries
List logged time entries in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of loggedtime records with fields such as logged_time_id, people_id, date, reference_date, hours, billable, notes, project_id. Use float_logged_times_list to browse or filter logged time entries; use float_logged_time_get to fetch one logged time entry by its ID.
Inputs
end_datestring- End of date range in format YYYY-MM-DD. Must be used together with `start_date`. Example: 2025-01-31
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
modified_sincestring- Datetime in either `YYYY-MM-DD hh:mm:ss` or as a Unix timestamp in seconds to filter on all records with an equal or later `modified` timestamp. Example: 2025-01-31
pageinteger- The page number of the page of results to return, default `1`.default
1 people_idinteger- A people ID to filter the response on. Example: 123
per_pageinteger- The number of items per page, max is `200`.default
50 phase_idinteger- A phase ID associated with a project to filter the response on. Example: 123
project_idinteger- A project ID to filter the response on. Example: 123
sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
start_datestring- Start of date range in format YYYY-MM-DD. Must be used together with `end_date`. Example: 2025-01-31
task_meta_idinteger- A project task ID to filter the response on. Example: 123
float_milestone_getRetrieve a single milestone from your Float account by ID.Read-onlyGet Milestone
Retrieve a single milestone from your Float account by ID. Returns the record record with fields such as milestone_id, name, project_id, phase_id, date, end_date, created, modified. Use float_milestone_get when you already have the ID; use float_milestones_list to search or browse. Requires milestone_id, typically from float_milestones_list.
Inputs
milestone_idintegerrequired- The milestone's ID. Example: 123
float_milestones_listList milestones in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Milestones
List milestones in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of record records with fields such as milestone_id, name, project_id, phase_id, date, end_date, created, modified. Use float_milestones_list to browse or filter milestones; use float_milestone_get to fetch one milestone by its ID.
Inputs
client_idinteger- A client ID associated with projects to filter the response on. Example: 123
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50 phase_idinteger- A phase ID associated with a project to filter the response on. Example: 123
project_idinteger- A project ID to filter the response on. Example: 123
float_people_listList people in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList People
List people in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of person records with fields such as people_id, name, people_code, email, job_title, role_id, department, notes. Use float_people_list to browse or filter people; use float_person_get to fetch one person by its ID.
Inputs
activeinteger- Filter only on `0` = non-active or `1` = active entities in the response. Example: 1
department_idinteger- A department ID to filter the response on. Example: 123
emailstring- An email address to filter the response (exact match, non-case sensitive) Example: sarahjane@example.com
employee_typeinteger- The employee type to filter the response on `1` = Full time, `0` = Part time. Example: 1
expandstring- Comma-delimited values expands the response with additional fields: `account`, `managers`, and `contracts`. Example: Expand
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
modified_sincestring- Datetime in either `YYYY-MM-DD hh:mm:ss` or as a Unix timestamp in seconds to filter on all records with an equal or later `modified` timestamp. Example: 2025-01-31
pageinteger- The page number of the page of results to return, default `1`.default
1 people_codestring- Case-insensitive, URL encoded match of a people code to filter the list response to a single person. Example: People Code
people_type_idstring- The people type to filter the response on `1` = Employee, `2` = Contractor, `3` = Placeholder, `4` = Role placeholder. Type `4` is not returned by default. Note: This parameter accepts comma-separated values (e.g., `people_type_id=1,2` or `people_type_id=4`). Example: 123
per_pageinteger- The number of items per page, max is `200`.default
50 sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
tag_namestring- Case-insensitive, URL encoded, exact text match of tag names to filter the response on. Comma-delimited values will return all matching records. Example: design
float_person_getRetrieve a single person from your Float account by ID.Read-onlyGet Person
Retrieve a single person from your Float account by ID. Returns the person record with fields such as people_id, name, people_code, email, job_title, role_id, department, notes. Use float_person_get when you already have the ID; use float_people_list to search or browse. Requires people_id, typically from float_people_list.
Inputs
people_idintegerrequired- The person's id. Example: 123
expandstring- Comma-delimited values expands the response with additional fields: `account`, `managers`, and `contracts`. Example: Expand
float_phase_getRetrieve a single phase from your Float account by ID.Read-onlyGet Phase
Retrieve a single phase from your Float account by ID. Returns the phase record with fields such as phase_id, project_id, name, color, notes, start_date, end_date, budget_total. Use float_phase_get when you already have the ID; use float_phases_list to search or browse. Requires phase_id, typically from float_phases_list.
Inputs
phase_idintegerrequired- The phase's ID. Example: 123
expandstring- Comma-delimited values expands the response with additional fields: `phase_tasks`, `phase_team`. Example: Expand
float_phases_listList phases in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Phases
List phases in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of phase records with fields such as phase_id, project_id, name, color, notes, start_date, end_date, budget_total. Use float_phases_list to browse or filter phases; use float_phase_get to fetch one phase by its ID.
Inputs
activeinteger- Filter only on `0` = non-active or `1` = active entities in the response. Example: 1
expandstring- Comma-delimited values expands the response with additional fields: `phase_tasks`, `phase_team`. Example: Expand
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
modified_sincestring- Datetime in either `YYYY-MM-DD hh:mm:ss` or as a Unix timestamp in seconds to filter on all records with an equal or later `modified` timestamp. Example: 2025-01-31
non_billableinteger- Filter response on `0` = billable or `1` = non-billable phases. Example: 1
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50 project_idinteger- A project ID to filter the response on. Example: 123
sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
float_project_expense_getRetrieve a single project expense from your Float account by ID.Read-onlyGet Project Expense
Retrieve a single project expense from your Float account by ID. Returns the project expense record with fields such as id, name, date, cost, project_id, phase_id, billable, markup. Use float_project_expense_get when you already have the ID; use float_project_expenses_list to search or browse. Requires project_expense_id, typically from float_project_expenses_list.
Inputs
project_expense_idintegerrequired- The project expense's ID. Example: 123
float_project_expenses_listList project expenses in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Project Expenses
List project expenses in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of project expense records with fields such as id, name, date, cost, project_id, phase_id, billable, markup. Use float_project_expenses_list to browse or filter project expenses; use float_project_expense_get to fetch one project expense by its ID.
Inputs
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50 project_idinteger- A project ID to filter the response on. Example: 123
sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
float_project_getRetrieve a single project from your Float account by ID.Read-onlyGet Project
Retrieve a single project from your Float account by ID. Returns the project record with fields such as project_id, name, project_code, client_id, color, notes, tags, budget_type. Use float_project_get when you already have the ID; use float_projects_list to search or browse. Requires project_id, typically from float_projects_list.
Inputs
project_idintegerrequired- The project's ID. Example: 123
expandstring- Comma-delimited values expands the response with additional fields: `expenses`, `phases`, `project_tasks`, `project_team`, `currency`. Example: Expand
float_project_stage_getRetrieve a single project stage from your Float account by ID.Read-onlyGet Project Stage
Retrieve a single project stage from your Float account by ID. Returns the projectstage record with fields such as id, name, description, project_status, active, sort_order, color, created. Use float_project_stage_get when you already have the ID; use float_project_stages_list to search or browse. Requires id, typically from float_project_stages_list.
Inputs
idintegerrequired- The project stage's ID. Example: 123
expandstring- Comma-delimited values expands the response with additional fields: `project_count`. Example: Expand
float_project_stages_listList project stages in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Project Stages
List project stages in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of projectstage records with fields such as id, name, description, project_status, active, sort_order, color, created. Use float_project_stages_list to browse or filter project stages; use float_project_stage_get to fetch one project stage by its ID.
Inputs
activeinteger- Filter only on `0` = non-active or `1` = active entities in the response. Example: 1
expandstring- Comma-delimited values expands the response with additional fields: `project_count`. Example: Expand
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50 sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
float_project_task_getRetrieve a single project task from your Float account by ID.Read-onlyGet Project Task
Retrieve a single project task from your Float account by ID. Returns the project task record with fields such as task_meta_id, project_id, phase_id, task_name, billable, budget, count_tasks, count_logged_time. Use float_project_task_get when you already have the ID; use float_project_tasks_list to search or browse. Requires project_task_id, typically from float_project_tasks_list.
Inputs
project_task_idintegerrequired- The project tasks ID as described in the `task_meta_id` field. Example: 123
float_project_tasks_listList project tasks in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Project Tasks
List project tasks in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of project task records with fields such as task_meta_id, project_id, phase_id, task_name, billable, budget, count_tasks, count_logged_time. Use float_project_tasks_list to browse or filter project tasks; use float_project_task_get to fetch one project task by its ID.
Inputs
billableinteger- Filter response on `1` = billable or `0` = non-billable entities. Example: 1
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50 project_idinteger- A project ID to filter the response on. Example: 123
sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
float_project_template_getRetrieve a single project template from your Float account by ID.Read-onlyGet Project Template
Retrieve a single project template from your Float account by ID. Returns the projecttemplate record with fields such as project_template_id, name, client_id, color, notes, tags, budget_type, budget_total. Use float_project_template_get when you already have the ID; use float_project_templates_list to search or browse. Requires project_template_id, typically from float_project_templates_list.
Inputs
project_template_idintegerrequired- The project template's ID. Example: 123
float_project_templates_listList project templates in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Project Templates
List project templates in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of projecttemplate records with fields such as project_template_id, name, client_id, color, notes, tags, budget_type, budget_total. Use float_project_templates_list to browse or filter project templates; use float_project_template_get to fetch one project template by its ID.
Inputs
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50 sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
float_projects_listList projects in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Projects
List projects in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of project records with fields such as project_id, name, project_code, client_id, color, notes, tags, budget_type. Use float_projects_list to browse or filter projects; use float_project_get to fetch one project by its ID.
Inputs
activeinteger- Filter only on `0` = non-active or `1` = active entities in the response. Example: 1
client_idinteger- A client ID associated with projects to filter the response on. Example: 123
expandstring- Comma-delimited values expands the response with additional fields: `expenses`, `phases`, `project_tasks`, `project_team`, `currency`. Example: Expand
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
modified_sincestring- Datetime in either `YYYY-MM-DD hh:mm:ss` or as a Unix timestamp in seconds to filter on all records with an equal or later `modified` timestamp. Example: 2025-01-31
non_billableinteger- Filter response on `0` = billable or `1` = non-billable projects. Example: 1
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50 project_codestring- Case-insensitive, URL encoded match of a project code to filter the list response to a single project. Example: Project Code
sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
statusinteger- Filter response on the `status` of a project. Example: 1
tag_namestring- Case-insensitive, URL encoded, exact text match of tag names to filter the response on. Comma-delimited values will return all matching records. Example: design
float_public_holiday_getRetrieve a single public holiday from your Float account by ID.Read-onlyGet Public Holiday
Retrieve a single public holiday from your Float account by ID. Returns the public holiday record with fields such as id, name, region, dates. Use float_public_holiday_get when you already have the ID; use float_public_holidays_list to search or browse. Requires public_holiday_id, typically from float_public_holidays_list.
Inputs
public_holiday_idintegerrequired- The public holiday's ID. Example: 123
end_datestring- End of date range in format YYYY-MM-DD. Must be used together with `start_date`. Example: 2025-01-31
start_datestring- Start of date range in format YYYY-MM-DD. Must be used together with `end_date`. Example: 2025-01-31
yearstring- Returns all results in the given year in format YYYY. Default if omitted is the current year. Overridden by `start_date` and `end_date` parameters. Example: Yeardefault
2023
float_public_holidays_listList public holidays in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Public Holidays
List public holidays in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of public holiday records with fields such as id, name, region, dates. Use float_public_holidays_list to browse or filter public holidays; use float_public_holiday_get to fetch one public holiday by its ID.
Inputs
end_datestring- End of date range in format YYYY-MM-DD. Must be used together with `start_date`. Example: 2025-01-31
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50 regioninteger- Filter results by one or more specific region ID (comma separated) Example: 1
start_datestring- Start of date range in format YYYY-MM-DD. Must be used together with `end_date`. Example: 2025-01-31
yearstring- Returns all results in the given year in format YYYY. Default if omitted is the current year. Overridden by `start_date` and `end_date` parameters. Example: Yeardefault
2023
float_rate_card_getRetrieve a single rate card from your Float account by ID.Read-onlyGet Rate Card
Retrieve a single rate card from your Float account by ID. Returns the ratecard record with fields such as rate_card_id, name, currency_code, active, client_ids, roles, project_count, created_by. Use float_rate_card_get when you already have the ID; use float_rate_cards_list to search or browse. Requires rate_card_id, typically from float_rate_cards_list.
Inputs
rate_card_idintegerrequired- The rate card's ID. Example: 123
expandstring- Comma-delimited values expands the response with additional fields: `roles`, `project_count`. Example: Expand
float_rate_cards_listList rate cards in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Rate Cards
List rate cards in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of ratecard records with fields such as rate_card_id, name, currency_code, active, client_ids, roles, project_count, created_by. Use float_rate_cards_list to browse or filter rate cards; use float_rate_card_get to fetch one rate card by its ID.
Inputs
activeinteger- Filter response on `0` = inactive or `1` = active rate cards. Example: 1
client_idsstring- Comma-delimited list of client IDs. Filters the response to rate cards restricted to any of the given clients. Example: 1,2
currency_codestring- Filter the response to rate cards with this currency code. Example: Currency Code
expandstring- Comma-delimited values expands the response with additional fields: `roles`, `project_count`. Example: Expand
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50
float_report_people_getRetrieve aggregated schedule utilization for people between two dates.Read-onlyGet People Report
Retrieve aggregated schedule utilization for people between two dates. Returns an object whose people array holds one record per item, with fields such as name, people_id, department_id, department, people_type_id, wk_day_hrs, capacity, timeoff. Use float_report_people_get for capacity, scheduled, billable and unscheduled hour totals; use float_allocations_list for the individual allocations behind them. Requires start_date and end_date. Reports are not paginated and have a lower rate limit (30 requests per minute).
Inputs
end_datestringrequired- Required: End date of the report duration in the format YYYY-MM-DD. Example: 2025-01-31
start_datestringrequired- Required: Start date of the report duration in the format YYYY-MM-DD. Example: 2025-01-31
people_idinteger- A people ID to filter the response on. Example: 123
float_report_projects_getRetrieve aggregated schedule utilization for projects between two dates.Read-onlyGet Project Report
Retrieve aggregated schedule utilization for projects between two dates. Returns an object whose projects array holds one record per item, with fields such as name, project_id, client_id, scheduled, billable, nonBillable. Use float_report_projects_get for capacity, scheduled, billable and unscheduled hour totals; use float_allocations_list for the individual allocations behind them. Requires start_date and end_date. Reports are not paginated and have a lower rate limit (30 requests per minute).
Inputs
end_datestringrequired- Required: End date of the report duration in the format YYYY-MM-DD. Example: 2025-01-31
start_datestringrequired- Required: Start date of the report duration in the format YYYY-MM-DD. Example: 2025-01-31
project_idinteger- A project ID to filter the response on. Example: 123
float_role_getRetrieve a single role from your Float account by ID.Read-onlyGet Role
Retrieve a single role from your Float account by ID. Returns the role record with fields such as id, name, default_hourly_rate, created, created_by, modified, modified_by, cost_rate_history. Use float_role_get when you already have the ID; use float_roles_list to search or browse. Requires role_id, typically from float_roles_list.
Inputs
role_idintegerrequired- The role's ID. Example: 123
expandstring- Comma-delimited values expands the response with additional fields: `cost_rate_history`, `people_ids`,`people_count`. Example: Expand
float_roles_listList roles in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Roles
List roles in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of role records with fields such as id, name, default_hourly_rate, created, created_by, modified, modified_by, cost_rate_history. Use float_roles_list to browse or filter roles; use float_role_get to fetch one role by its ID.
Inputs
expandstring- Comma-delimited values expands the response with additional fields: `cost_rate_history`, `people_ids`,`people_count`. Example: Expand
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50
float_status_getRetrieve a single status from your Float account by ID.Read-onlyGet Status
Retrieve a single status from your Float account by ID. Returns the status record with fields such as status_id, status_type_id, people_id, status_name, start_date, end_date, repeat_state, repeat_end_date. Use float_status_get when you already have the ID; use float_statuses_list to search or browse. Requires status_id, typically from float_statuses_list.
Inputs
status_idintegerrequired- The status's id. Example: 123
float_statuses_listList statuses in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Statuses
List statuses in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of status records with fields such as status_id, status_type_id, people_id, status_name, start_date, end_date, repeat_state, repeat_end_date. Use float_statuses_list to browse or filter statuses; use float_status_get to fetch one status by its ID.
Inputs
end_datestring- End of date range in format YYYY-MM-DD. Must be used together with `start_date`. Example: 2025-01-31
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
pageinteger- The page number of the page of results to return, default `1`.default
1 people_idinteger- A people ID to filter the response on. Example: 123
per_pageinteger- The number of items per page, max is `200`.default
50 start_datestring- Start of date range in format YYYY-MM-DD. Must be used together with `end_date`. Example: 2025-01-31
status_type_idinteger- A status type ID to filter the response on. Example: 123
float_team_holiday_getRetrieve a single team holiday from your Float account by ID.Read-onlyGet Team Holiday
Retrieve a single team holiday from your Float account by ID. Returns the holiday record with fields such as holiday_id, name, date, end_date. Use float_team_holiday_get when you already have the ID; use float_team_holidays_list to search or browse. Requires holiday_id, typically from float_team_holidays_list.
Inputs
holiday_idintegerrequired- The holiday ID. Example: 123
float_team_holidays_listList team holidays in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Team Holidays
List team holidays in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of holiday records with fields such as holiday_id, name, date, end_date. Use float_team_holidays_list to browse or filter team holidays; use float_team_holiday_get to fetch one team holiday by its ID.
Inputs
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50
float_timeoff_getRetrieve a single time off entry from your Float account by ID.Read-onlyGet Time Off Entry
Retrieve a single time off entry from your Float account by ID. Returns the timeoff record with fields such as timeoff_id, timeoff_type_id, start_date, end_date, start_time, hours, timeoff_notes, repeat_state. Use float_timeoff_get when you already have the ID; use float_timeoffs_list to search or browse. Requires timeoff_id, typically from float_timeoffs_list.
Inputs
timeoff_idintegerrequired- The time off's ID. Example: 123
float_timeoff_type_getRetrieve a single time off type from your Float account by ID.Read-onlyGet Time Off Type
Retrieve a single time off type from your Float account by ID. Returns the timeoff type record with fields such as timeoff_type_id, timeoff_type_name, color, active, created_by. Use float_timeoff_type_get when you already have the ID; use float_timeoff_types_list to search or browse. Requires timeoff_type_id, typically from float_timeoff_types_list.
Inputs
timeoff_type_idintegerrequired- The time off type's ID. Example: 123
float_timeoff_types_listList time off types in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Time Off Types
List time off types in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of timeoff type records with fields such as timeoff_type_id, timeoff_type_name, color, active, created_by. Use float_timeoff_types_list to browse or filter time off types; use float_timeoff_type_get to fetch one time off type by its ID.
Inputs
activeinteger- Filter only on `0` = non-active or `1` = active entities in the response. Example: 1
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50
float_timeoffs_listList time off entries in your Float account, with optional filters, sorting, and page-based pagination.Read-onlyList Time Off Entries
List time off entries in your Float account, with optional filters, sorting, and page-based pagination. Returns an array of timeoff records with fields such as timeoff_id, timeoff_type_id, start_date, end_date, start_time, hours, timeoff_notes, repeat_state. Use float_timeoffs_list to browse or filter time off entries; use float_timeoff_get to fetch one time off entry by its ID.
Inputs
end_datestring- End of date range in format YYYY-MM-DD. Must be used together with `start_date`. Example: 2025-01-31
fieldsstring- Comma-delimited set of fields to include in the response. Example: name,email
full_dayinteger- Filter only on if timeoff is full day: `1` = Yes, `0` = No. Example: 1
modified_sincestring- Datetime in either `YYYY-MM-DD hh:mm:ss` or as a Unix timestamp in seconds to filter on all records with an equal or later `modified` timestamp. Example: 2025-01-31
pageinteger- The page number of the page of results to return, default `1`.default
1 per_pageinteger- The number of items per page, max is `200`.default
50 sortstring- A field to sort the list values in the response, ascending (default), pre-fix `-` to apply descending. (Limited fields, varies per endpoint) Example: -modified
start_datestring- Start of date range in format YYYY-MM-DD. Must be used together with `end_date`. Example: 2025-01-31
statusinteger- Filter on the Status of the time off: `1` = tentative, `2` = confirmed. Example: 1
timeoff_type_idinteger- Filter on the ID of the timeoff type. Example: 123
float_allocation_createCreate a new allocation in your Float account.WriteCreate Allocation
Create a new allocation in your Float account. An allocation is a scheduled block of hours for a person (or role placeholder) on a project. Returns the task record with fields such as task_id, root_task_id, parent_task_id, project_id, phase_id, start_date, end_date, start_time. Use float_allocation_create to add a new allocation; use float_allocation_update to change an existing one.
Inputs
end_datestringrequired- End date of this allocation. Example: 2023-11-22
hoursnumberrequired- Number of hours per day. Example: 4.5
project_idintegerrequired- The ID of the project for this allocation. Example: 1345
start_datestringrequired- Start date of this allocation. Example: 2023-11-16
namestring- Name of the associated project task. Example: Concepting
notesstring- Additional details about the work required. Example: Sketches and wireframes only.
parent_task_idinteger- The ID of the direct parent of a linked allocation. Example: 7654321
people_idinteger- The ID of the person assigned to the allocation (omit when using `people_ids` field) Example: 11223344
people_idsarray- List of one or more people IDs assigned to the allocation (ignored if `people_id` is set) Example: ["1234","5678"]
phase_idinteger- The ID of the project phase for this allocation. Example: 153
repeat_end_datestring- Date that the repeating allocation will cease. Example: 2023-03-16
repeat_stateinteger- Frequency that this allocation repeats. `0` = No repeat, `1` = Weekly, `2` = Monthly, `3` = Every two weeks, `4` = Every three weeks, `5` = Every six weeks, `6` = Every two months, `7` = Every three months, `8` = Every six months, `9` = Yearly. Example: 0
root_task_idinteger- The ID of the earliest linked allocation in a chain. Example: 1234567
start_timestring- Start time in 24 hr format. Example: 14:00
statusinteger- Status; `0` = Draft, `1` = Tentative, `2` = Confirmed, `3` = Complete, `4` = Canceled. Example: 2
task_meta_idinteger- The ID of the associated project task (named for backwards compatibility), takes higher priority over `name`. Example: 1234567
float_allocation_updateUpdate an existing allocation in your Float account; only the fields you provide are changed.WriteUpdate Allocation
Update an existing allocation in your Float account; only the fields you provide are changed. Returns the task record with fields such as task_id, root_task_id, parent_task_id, project_id, phase_id, start_date, end_date, start_time. Use float_allocation_update to modify a allocation; use float_allocation_create to add a new one. Requires task_id, typically from float_allocations_list.
- Idempotent
Inputs
task_idintegerrequired- The allocation as a task ID. Example: 123
end_datestring- End date of this allocation. Example: 2023-11-22
hoursnumber- Number of hours per day. Example: 4.5
namestring- Name of the associated project task. Example: Concepting
notesstring- Additional details about the work required. Example: Sketches and wireframes only.
parent_task_idinteger- The ID of the direct parent of a linked allocation. Example: 7654321
people_idinteger- The ID of the person assigned to the allocation (omit when using `people_ids` field) Example: 11223344
people_idsarray- List of one or more people IDs assigned to the allocation (ignored if `people_id` is set) Example: ["1234","5678"]
phase_idinteger- The ID of the project phase for this allocation. Example: 153
project_idinteger- The ID of the project for this allocation. Example: 1345
repeat_end_datestring- Date that the repeating allocation will cease. Example: 2023-03-16
repeat_stateinteger- Frequency that this allocation repeats. `0` = No repeat, `1` = Weekly, `2` = Monthly, `3` = Every two weeks, `4` = Every three weeks, `5` = Every six weeks, `6` = Every two months, `7` = Every three months, `8` = Every six months, `9` = Yearly. Example: 0
root_task_idinteger- The ID of the earliest linked allocation in a chain. Example: 1234567
start_datestring- Start date of this allocation. Example: 2023-11-16
start_timestring- Start time in 24 hr format. Example: 14:00
statusinteger- Status; `0` = Draft, `1` = Tentative, `2` = Confirmed, `3` = Complete, `4` = Canceled. Example: 2
task_meta_idinteger- The ID of the associated project task (named for backwards compatibility), takes higher priority over `name`. Example: 1234567
float_client_createCreate a new client in your Float account.WriteCreate Client
Create a new client in your Float account. Returns the client record with fields such as client_id, name. Use float_client_create to add a new client; use float_client_update to change an existing one.
Inputs
namestringrequired- The name of the client. Example: Red Circle
float_client_updateUpdate an existing client in your Float account; only the fields you provide are changed.WriteUpdate Client
Update an existing client in your Float account; only the fields you provide are changed. Returns the client record with fields such as client_id, name. Use float_client_update to modify a client; use float_client_create to add a new one. Requires client_id, typically from float_clients_list.
- Idempotent
Inputs
client_idintegerrequired- The client's ID. Example: 123
namestring- The name of the client. Example: Red Circle
float_department_createCreate a new department in your Float account.WriteCreate Department
Create a new department in your Float account. Returns the department record with fields such as department_id, parent_id, name. Use float_department_create to add a new department; use float_department_update to change an existing one.
Inputs
namestringrequired- The name of the department. Example: Engineers
parent_idinteger- The ID of this department's parent department (identifies this as a sub-department if not `null`) Example: 123
float_department_updateUpdate an existing department in your Float account; only the fields you provide are changed.WriteUpdate Department
Update an existing department in your Float account; only the fields you provide are changed. Returns the department record with fields such as department_id, parent_id, name. Use float_department_update to modify a department; use float_department_create to add a new one. Requires department_id, typically from float_departments_list.
- Idempotent
Inputs
department_idintegerrequired- The department's id. Example: 123
namestring- The name of the department. Example: Engineers
parent_idinteger- The ID of this department's parent department (identifies this as a sub-department if not `null`) Example: 123
float_logged_time_createCreate a new logged time entry in your Float account.WriteCreate Logged Time Entry
Create a new logged time entry in your Float account. Logs actual hours worked by a person on a project. Returns an array of loggedtime records with fields such as logged_time_id, people_id, date, reference_date, hours, billable, notes, project_id. Use float_logged_time_create to add a new logged time entry; use float_logged_time_update to change an existing one.
Inputs
datestringrequired- Date of the logged time entry. Example: 2022-12-12
hoursnumberrequired- Total hours of the logged time entry, will be rounded to 2 decimal places, `0` values are valid however this acts as a soft-delete so the response is hidden. Example: 5.25
people_idintegerrequired- The ID of the person for the logged time entry. Example: 9876
project_idintegerrequired- The ID of the project on which this entry was logged. Example: 4567
notesstring- Additional notes about this logged time entry. Example: This took a lot longer than planned because I didn't have the original illustrations
phase_idinteger- The ID of the project phase for which this entry was logged. A value of `0` indicates no phase is used. Example: 335
reference_datestring- The date on which to suppress a log time suggestion of the corresponding `task_id` in the UI. Example: 2025-04-12
task_idinteger- The ID of a scheduled allocation, when used with `reference_date` it suppresses a matching log time suggestion in the UI. Example: 7654321
task_meta_idinteger- The ID of the associated project task (named for backwards compatibility), takes higher priority over `task_name`. Example: 1234567
task_namestring- The name of the project task against which this entry was logged, will create a project task name. Example: Front-end Development
float_logged_time_updateUpdate an existing logged time entry in your Float account; only the fields you provide are changed.WriteUpdate Logged Time Entry
Update an existing logged time entry in your Float account; only the fields you provide are changed. Returns the loggedtime record with fields such as logged_time_id, people_id, date, reference_date, hours, billable, notes, project_id. Use float_logged_time_update to modify a logged time entry; use float_logged_time_create to add a new one. Requires logged_time_id, typically from float_logged_times_list.
- Idempotent
Inputs
logged_time_idstringrequired- Unique ID of the specific logged time entry to be updated. Example: 123
datestring- Date of the logged time entry. Example: 2022-12-12
hoursnumber- Total hours of the logged time entry, will be rounded to 2 decimal places, `0` values are valid however this acts as a soft-delete so the response is hidden. Example: 5.25
notesstring- Additional notes about this logged time entry. Example: This took a lot longer than planned because I didn't have the original illustrations
people_idinteger- The ID of the person for the logged time entry. Example: 9876
phase_idinteger- The ID of the project phase for which this entry was logged. A value of `0` indicates no phase is used. Example: 335
project_idinteger- The ID of the project on which this entry was logged. Example: 4567
reference_datestring- The date on which to suppress a log time suggestion of the corresponding `task_id` in the UI. Example: 2025-04-12
task_idinteger- The ID of a scheduled allocation, when used with `reference_date` it suppresses a matching log time suggestion in the UI. Example: 7654321
task_meta_idinteger- The ID of the associated project task (named for backwards compatibility), takes higher priority over `task_name`. Example: 1234567
task_namestring- The name of the project task against which this entry was logged, will create a project task name. Example: Front-end Development
float_milestone_createCreate a new milestone in your Float account.WriteCreate Milestone
Create a new milestone in your Float account. Returns the record record with fields such as milestone_id, name, project_id, phase_id, date, end_date, created, modified. Use float_milestone_create to add a new milestone; use float_milestone_update to change an existing one.
Inputs
datestringrequired- Start date of the milestone. Example: 2019-12-01 09:00
namestringrequired- The name of the milestone. Example: Sprint #14
project_idintegerrequired- The project that this milestone belongs to. Example: 1
end_datestring- End date of the milestone if more than 1 day. Example: 2019-12-05 17:00
phase_idinteger- The phase that this milestone belongs to. Example: 1
float_milestone_updateUpdate an existing milestone in your Float account; only the fields you provide are changed.WriteUpdate Milestone
Update an existing milestone in your Float account; only the fields you provide are changed. Returns the record record with fields such as milestone_id, name, project_id, phase_id, date, end_date, created, modified. Use float_milestone_update to modify a milestone; use float_milestone_create to add a new one. Requires milestone_id, typically from float_milestones_list.
- Idempotent
Inputs
milestone_idintegerrequired- The milestone's ID. Example: 123
datestring- Start date of the milestone. Example: 2019-12-01 09:00
end_datestring- End date of the milestone if more than 1 day. Example: 2019-12-05 17:00
namestring- The name of the milestone. Example: Sprint #14
phase_idinteger- The phase that this milestone belongs to. Example: 1
project_idinteger- The project that this milestone belongs to. Example: 1
float_person_createCreate a new person in your Float account.WriteCreate Person
Create a new person in your Float account. Creating a person does not create a sign-in account, and each active person uses a billing seat. Returns the person record with fields such as people_id, name, people_code, email, job_title, role_id, department, notes. Use float_person_create to add a new person; use float_person_update to change an existing one.
Inputs
namestringrequired- The person's full name. Example: Sarah-Jane Smith
activeinteger- Is this person active or archived? `1` = Active, `0` = Archived. Archived people do not show on the schedule or contribute to billing seats and will have their access removed. Example: 1
auto_emailinteger- Should this person's schedule be emailed at start of week? 1 = Yes, 0 = No. Example: 0
default_hourly_ratestring- Default hourly rate applied when the person is added to a fee-based project, the request also accepts a decimal `number`. Example: 100.50
departmentobject- The current department the person belongs to. Example: {}
emailstring- Email address for this person. Example: sarahjane@example.com
employee_typeinteger- Full-time or part-type. `1` = Full-time, `0` = Part-time. Example: 0
end_datestring- Date the person finished. Example: 2019-11-11
expandstring- Comma-delimited values expands the response with additional fields: `account`, `managers`, and `contracts`. Example: Expand
job_titlestring- The name of the person's role as defined by their `role_id`. Example: Designer
notesstring- Any notes related to this person. Example: Sarah-Jane can't work on weekends.
people_codestring- An optional third-party identifier unique across all people enforced using case-insensitive comparison. Example: EMP-123456
people_type_idinteger- Is this person an `1` = Employee (default), `2` = Contractor, `3` = Placeholder, `4` = Role placeholder? Type `4` is not returned by default when listing people. Example: 1
region_idinteger- ID of the public holiday region to which the person belongs. Example: 1234
role_idinteger- ID of a role associated with this person, `role.name` is used for `job_title`, during updates `role_id` is higher order. Example: 0
start_datestring- Date the person started. Example: 2019-05-20
tagsarray- Tags. Example: [1,2]
work_days_hoursarray- Hours that a part-time person is available for scheduling each day in order from Sunday to Saturday. Example: [0,8,8,8,8,4,0]
float_person_updateUpdate an existing person in your Float account; only the fields you provide are changed.WriteUpdate Person
Update an existing person in your Float account; only the fields you provide are changed. Setting active to 0 archives the person and revokes their account access. Returns the person record with fields such as people_id, name, people_code, email, job_title, role_id, department, notes. Use float_person_update to modify a person; use float_person_create to add a new one. Requires people_id, typically from float_people_list.
- Idempotent
Inputs
people_idintegerrequired- The person's id. Example: 123
activeinteger- Is this person active or archived? `1` = Active, `0` = Archived. Archived people do not show on the schedule or contribute to billing seats and will have their access removed. Example: 1
auto_emailinteger- Should this person's schedule be emailed at start of week? 1 = Yes, 0 = No. Example: 0
default_hourly_ratestring- Default hourly rate applied when the person is added to a fee-based project, the request also accepts a decimal `number`. Example: 100.50
departmentobject- The current department the person belongs to. Example: {}
emailstring- Email address for this person. Example: sarahjane@example.com
employee_typeinteger- Full-time or part-type. `1` = Full-time, `0` = Part-time. Example: 0
end_datestring- Date the person finished. Example: 2019-11-11
expandstring- Comma-delimited values expands the response with additional fields: `account`, `managers`, and `contracts`. Example: Expand
job_titlestring- The name of the person's role as defined by their `role_id`. Example: Designer
namestring- The person's full name. Example: Sarah-Jane Smith
notesstring- Any notes related to this person. Example: Sarah-Jane can't work on weekends.
people_codestring- An optional third-party identifier unique across all people enforced using case-insensitive comparison. Example: EMP-123456
people_type_idinteger- Is this person an `1` = Employee (default), `2` = Contractor, `3` = Placeholder, `4` = Role placeholder? Type `4` is not returned by default when listing people. Example: 1
region_idinteger- ID of the public holiday region to which the person belongs. Example: 1234
role_idinteger- ID of a role associated with this person, `role.name` is used for `job_title`, during updates `role_id` is higher order. Example: 0
start_datestring- Date the person started. Example: 2019-05-20
tagsarray- Tags. Example: [1,2]
work_days_hoursarray- Hours that a part-time person is available for scheduling each day in order from Sunday to Saturday. Example: [0,8,8,8,8,4,0]
float_phase_createCreate a new phase in your Float account.WriteCreate Phase
Create a new phase in your Float account. Returns the phase record with fields such as phase_id, project_id, name, color, notes, start_date, end_date, budget_total. Use float_phase_create to add a new phase; use float_phase_update to change an existing one.
Inputs
end_datestringrequired- The end date of this phase which is either manually set or calculated from the latest milestone, allocation, or logged time within this phase. Example: 2025-02-23
namestringrequired- The name of the phase. Example: Design
project_idintegerrequired- The ID of the project to which this phase belongs. Example: 4567
start_datestringrequired- The start date of this phase which is either manually set or calculated from the earliest milestone, allocation, or logged time within this phase. Example: 2024-12-12
activeinteger- Is this phase active or archived? `1` = Active, `0` = Archived. Example: 1
budget_totalnumber- The budget amount for 'hours by phase' or 'fee by phase' project budgets. Example: 1000.5
colorstring- Phase's color in hexadecimal (defaults to project color) Example: 0095D7
default_hourly_ratestring- The default hourly rate for fee-based budgets, the request also accepts a decimal `number`. Example: 55.50
non_billableinteger- Is this phase billable? `0` = Billable, `1` = Non-billable. Example: 1
notesstring- Notes for this phase. Example: Due at the start of July. Paul to present
phase_teamarray- `expand` field. A list of assignees on this phase by `people_id`, `role_id`, and `hourly_rate`, the list may be empty. Example: [1,2]
statusinteger- The status of the phase `0` = Draft, `1` = Tentative, `2` = Confirmed, `3` = Completed, `4` = Canceled. Draft phases can belong to a project of any status. Tentative phases must belong to tentative or confirmed projects. Confirmed, completed, and canceled phases must match their project's status. Example: 2
tentativeinteger- (Deprecated - see `status`): Is this phase tentative? `1` = Yes, `0` = No. Example: 0
float_phase_updateUpdate an existing phase in your Float account; only the fields you provide are changed.WriteUpdate Phase
Update an existing phase in your Float account; only the fields you provide are changed. Returns the phase record with fields such as phase_id, project_id, name, color, notes, start_date, end_date, budget_total. Use float_phase_update to modify a phase; use float_phase_create to add a new one. Requires phase_id, typically from float_phases_list.
- Idempotent
Inputs
phase_idintegerrequired- The phase's ID. Example: 123
activeinteger- Is this phase active or archived? `1` = Active, `0` = Archived. Example: 1
budget_totalnumber- The budget amount for 'hours by phase' or 'fee by phase' project budgets. Example: 1000.5
colorstring- Phase's color in hexadecimal (defaults to project color) Example: 0095D7
default_hourly_ratestring- The default hourly rate for fee-based budgets, the request also accepts a decimal `number`. Example: 55.50
end_datestring- The end date of this phase which is either manually set or calculated from the latest milestone, allocation, or logged time within this phase. Example: 2025-02-23
expandstring- Comma-delimited values expands the response with additional fields: `phase_tasks`, `phase_team`. Example: Expand
namestring- The name of the phase. Example: Design
non_billableinteger- Is this phase billable? `0` = Billable, `1` = Non-billable. Example: 1
notesstring- Notes for this phase. Example: Due at the start of July. Paul to present
phase_teamobject- Manages the composition and details of the phase team. Example: {}
project_idinteger- The ID of the project to which this phase belongs. Example: 4567
start_datestring- The start date of this phase which is either manually set or calculated from the earliest milestone, allocation, or logged time within this phase. Example: 2024-12-12
statusinteger- The status of the phase `0` = Draft, `1` = Tentative, `2` = Confirmed, `3` = Completed, `4` = Canceled. Draft phases can belong to a project of any status. Tentative phases must belong to tentative or confirmed projects. Confirmed, completed, and canceled phases must match their project's status. Example: 2
tentativeinteger- (Deprecated - see `status`): Is this phase tentative? `1` = Yes, `0` = No. Example: 0
float_project_createCreate a new project in your Float account.WriteCreate Project
Create a new project in your Float account. Returns the project record with fields such as project_id, name, project_code, client_id, color, notes, tags, budget_type. Use float_project_create to add a new project; use float_project_update to change an existing one.
Inputs
namestringrequired- The name of the project. Example: Website Redesign
activeinteger- Is this project active or archived? `1` = Active, `0` = Archived. Example: 1
all_pms_scheduleinteger- Managers not assigned to the project team can edit this project. `1` = Yes, `0` = No. Example: 0
budget_per_phaseinteger- (Deprecated - see `budget_priority`): Is the budget set per Phase? `1` = Yes, `0` = No. Example: 1
budget_priorityinteger- Defines which level the budget will be determined from; `0` = Project, `1` = Phase, `2` = Task. For non-project levels, the total budget can be calculated from the sum of budgets in each Phase or Task. Example: 0
budget_totalnumber- The budget amount for Total hours or Total fee project budgets. Displays as `null` for Time & materials, Phase and Task budgets, also see `budget_priority`. Example: 1000.5
budget_typeinteger- Is there a project budget? `1` = Total hours, `2` = Total fee, `3` = Time & materials. Example: 1
client_idinteger- The ID of the project's client. Example: 45672
colorstring- Project's color in hexadecimal. Example: 0095D7
currency_codestring- `expand` field. The ISO 4217 currency code assigned to this project. Only returned when using `expand=currency`. Can be set via POST and PATCH; the value must correspond to a `target_currency` in the company's currencies list. Example: CAD
default_hourly_ratestring- The hourly rate applied to every person on the project team by using the 'Set same for everyone' billing rate option, for fee-based budgets. The request also accepts a decimal `number`. If `rate_card_id` is also set on the project, the rate card takes priority and this field is not used to determine bill rates. Example: 55.50
end_datestring- The end date of this project which is either manually set or calculated from the latest phase, milestone, allocation, or logged time. Example: 2025-01-18
expensesarray- `expand` field. The expenses assigned to this project. Example: [1,2]
fx_ratenumber- `expand` field. The exchange rate applied to this project's currency. Only returned when using `expand=currency`. If omitted on POST or PATCH, the default `fx_rate` from the matching currency record is used. Example: 1.39
locked_task_listinteger- Are members locked from adding project tasks (Only Project Managers can add to this list)? 1 = Yes, locked to project editors, 0 = No, anyone can add tasks. Example: 1
non_billableinteger- Is this project billable? `0` = Billable, `1` = Non-billable. Example: 1
notesstring- Notes for this project. Example: Due at the start of July. Paul to present
phasesarray- `expand` field. A list of phases on this project (`phase_id`, `name`, `color`, `budget`, `start_date`, `end_date`), the list may be empty. Example: [1,2]
project_codestring- An optional third-party identifier unique across all projects enforced using case-insensitive comparison. Example: PRJ-123456
project_managerinteger- The account ID of the project owner. Example: 17393464
project_tasksarray- `expand` field. A list of the project tasks available in this project. Example: [1,2]
project_teamarray- `expand` field. A list of project-level team members by `people_id`, `role_id`, and `hourly_rate`. Only entries with `phase_id` = `0` are returned; for phase-specific roles and rates use `GET /phases?project_id=project_id` and add `expand=phase_team`. Example: [1,2]
rate_card_idinteger- The ID of the [rate card](/api_reference#Rate_Cards) applied to this project. Only supported for fee-based budgets (`budget_type` = `2` or `3`). When set, it determines the bill rate for each project team member based on their role, taking priority over `default_hourly_rate` and any per-person `hourly_rate` on `project_team`. Set to `null` to remove the rate card from the project. Example: 95020
stage_idinteger- The ID of the project stage for this project. This field takes precedence over `status` when both are provided. If omitted, the first available stage related to the project's `status` will be used. Example: 1
start_datestring- The start date of this project which is either manually set or calculated from the earliest phase, milestone, allocation, or logged time. Example: 2024-11-07
statusinteger- The status of the project `0` = Draft, `1` = Tentative, `2` = Confirmed, `3` = Completed, `4` = Canceled. If both `status` and `stage_id` are provided, `stage_id` takes precedence. If only `status` is provided, the first available stage for that status will be automatically selected. Example: 2
tagsarray- List of tags. Example: ["digital","pitch"]
tentativeinteger- (Deprecated - see `status`): Is this project tentative? `1` = Yes, `0` = No. Example: 0
float_project_from_template_createCreate a new project in Float by copying an existing project template.WriteCreate Project From Template
Create a new project in Float by copying an existing project template. Returns the record record with fields such as . Use float_project_from_template_create to start a project from a template; use float_project_create for a blank project. Requires project_template_id, typically from float_project_templates_list, plus a project_code and start_date.
Inputs
project_codestringrequired- Required. A third-party identifier unique across all projects, enforced using case-insensitive comparison. Maximum length is 32 characters. Used to retrieve the created project via `GET /projects?project_code={project_code}` after the asynchronous create completes. Example: PRJ-123456
project_template_idintegerrequired- The project template's ID. Example: 123
start_datestringrequired- Required. The start date of the new project. Phases, milestones, expenses, and project tasks are scheduled relative to this date using each item's `parent_offset` and `duration` from the template. Example: 2026-07-01
activeinteger- Is this project active or archived? `1` = Active, `0` = Archived. Example: 1
all_pms_scheduleinteger- Managers not assigned to the project team can edit this project. `1` = Yes, `0` = No. Example: 0
budget_priorityinteger- Defines which level the budget will be determined from; `0` = Project, `1` = Phase, `2` = Task. Overrides the template value when provided. Example: 0
budget_totalnumber- The budget amount for Total hours or Total fee project budgets. Displays as `null` for Time & materials, Phase and Task budgets, also see `budget_priority`. Overrides the template value when provided. Example: 1000.5
budget_typeinteger- Is there a project budget? `1` = Total hours, `2` = Total fee, `3` = Time & materials. Overrides the template value when provided. Example: 3
client_idinteger- The ID of the project's client. Overrides the template value when provided. Example: 45672
colorstring- Project's color in hexadecimal. Overrides the template value when provided. Example: 68DDFD
currency_codestring- The ISO 4217 currency code assigned to this project. The value must correspond to a `target_currency` in the company's currencies list. If provided, `fx_rate` is also required. See `expand=currency` on [projects](/api_reference#Projects) Example: USD
default_hourly_ratestring- The hourly rate applied to every person on the project team by using the 'Set same for everyone' billing rate option, for fee-based budgets. The request also accepts a decimal `number`. If a `rate_card_id` is applied to the project (inherited from the template or set explicitly in this request), the rate card takes priority and this field is not used to determine bill rates. Overrides the template value when provided. Example: 55.50
end_datestring- The end date of the new project. If omitted, calculated from `start_date` plus the template's `duration`. Example: 2026-09-30
fx_ratestring- The exchange rate applied to this project's currency. Required when `currency_code` is provided. Also accepts a decimal `number`. Example: 1
locked_task_listinteger- Are members locked from adding project tasks (Only Project Managers can add to this list)? 1 = Yes, locked to project editors, 0 = No, anyone can add tasks. Example: 1
namestring- The name of the project. If omitted, the template name is used. Example: Website Redesign
non_billableinteger- Is this project billable? `0` = Billable, `1` = Non-billable. Overrides the template value when provided. Example: 0
notesstring- Notes for this project. Overrides the template value when provided. Example: example
project_managerinteger- The account ID of the project owner. Example: 80851
rate_card_idinteger- The ID of the [rate card](/api_reference#Rate_Cards) applied to this project. Only supported for fee-based budgets (`budget_type` = `2` or `3`). When set, it determines the bill rate for each project team member based on their role, taking priority over `default_hourly_rate` and any per-person hourly rate inherited from the template. If omitted, the template's `rate_card_id` is inherited. Set to `null` to remove the rate card inherited from the template. Example: 95020
stage_idinteger- The ID of the project stage for this project. This field takes precedence over `status` when both are provided. If omitted, the first available stage related to the project's `status` will be used. Example: 101079
statusinteger- The status of the project `0` = Draft, `1` = Tentative, `2` = Confirmed, `3` = Completed, `4` = Canceled. If both `status` and `stage_id` are provided, `stage_id` takes precedence. If only `status` is provided, the first available stage for that status will be automatically selected. Example: 2
tagsarray- List of tags. Overrides the template value when provided. Example: []
float_project_task_createCreate a new project task in your Float account.WriteCreate Project Task
Create a new project task in your Float account. Returns the project task record with fields such as task_meta_id, project_id, phase_id, task_name, billable, budget, count_tasks, count_logged_time. Use float_project_task_create to add a new project task; use float_project_task_update to change an existing one.
Inputs
project_idintegerrequired- The ID of the project the project task belongs to. Example: 32154
task_namestringrequired- The name of the project task, an empty string is valid and is the default on the UI when a project task has not been chosen. Example: Design
billableinteger- `1` = Billable, `0` = Non-billable - Billable project tasks may not belong to non-billable projects or phases. Example: 1
budgetnumber- The budget amount for 'hours by task' or 'fee by task' project budgets. Example: 100.99
phase_idinteger- The ID of the phase the project task belongs to; `0` indicates it does not belong to a phase. Example: 123default
0
float_project_task_updateUpdate an existing project task in your Float account; only the fields you provide are changed.WriteUpdate Project Task
Update an existing project task in your Float account; only the fields you provide are changed. Returns the project task record with fields such as task_meta_id, project_id, phase_id, task_name, billable, budget, count_tasks, count_logged_time. Use float_project_task_update to modify a project task; use float_project_task_create to add a new one. Requires project_task_id, typically from float_project_tasks_list.
- Idempotent
Inputs
project_task_idintegerrequired- The project tasks ID as described in the `task_meta_id` field. Example: 123
billableinteger- `1` = Billable, `0` = Non-billable - Billable project tasks may not belong to non-billable projects or phases. Example: 1
budgetnumber- The budget amount for 'hours by task' or 'fee by task' project budgets. Example: 100.99
phase_idinteger- The ID of the phase the project task belongs to; `0` indicates it does not belong to a phase. Example: 123default
0 project_idinteger- The ID of the project the project task belongs to. Example: 32154
task_namestring- The name of the project task, an empty string is valid and is the default on the UI when a project task has not been chosen. Example: Design
float_project_updateUpdate an existing project in your Float account; only the fields you provide are changed.WriteUpdate Project
Update an existing project in your Float account; only the fields you provide are changed. Returns the project record with fields such as project_id, name, project_code, client_id, color, notes, tags, budget_type. Use float_project_update to modify a project; use float_project_create to add a new one. Requires project_id, typically from float_projects_list.
- Idempotent
Inputs
project_idintegerrequired- The project's ID. Example: 123
activeinteger- Is this project active or archived? `1` = Active, `0` = Archived. Example: 1
all_pms_scheduleinteger- Managers not assigned to the project team can edit this project. `1` = Yes, `0` = No. Example: 0
budget_per_phaseinteger- (Deprecated - see `budget_priority`): Is the budget set per Phase? `1` = Yes, `0` = No. Example: 1
budget_priorityinteger- Defines which level the budget will be determined from; `0` = Project, `1` = Phase, `2` = Task. For non-project levels, the total budget can be calculated from the sum of budgets in each Phase or Task. Example: 0
budget_totalnumber- The budget amount for Total hours or Total fee project budgets. Displays as `null` for Time & materials, Phase and Task budgets, also see `budget_priority`. Example: 1000.5
budget_typeinteger- Is there a project budget? `1` = Total hours, `2` = Total fee, `3` = Time & materials. Example: 1
client_idinteger- The ID of the project's client. Example: 45672
colorstring- Project's color in hexadecimal. Example: 0095D7
currency_codestring- `expand` field. The ISO 4217 currency code assigned to this project. Only returned when using `expand=currency`. Can be set via POST and PATCH; the value must correspond to a `target_currency` in the company's currencies list. Example: CAD
default_hourly_ratestring- The hourly rate applied to every person on the project team by using the 'Set same for everyone' billing rate option, for fee-based budgets. The request also accepts a decimal `number`. If `rate_card_id` is also set on the project, the rate card takes priority and this field is not used to determine bill rates. Example: 55.50
end_datestring- The end date of this project which is either manually set or calculated from the latest phase, milestone, allocation, or logged time. Example: 2025-01-18
expandstring- Comma-delimited values expands the response with additional fields: `expenses`, `phases`, `project_tasks`, `project_team`, `currency`. Example: Expand
expensesarray- `expand` field. The expenses assigned to this project. Example: [1,2]
fx_ratenumber- `expand` field. The exchange rate applied to this project's currency. Only returned when using `expand=currency`. If omitted on POST or PATCH, the default `fx_rate` from the matching currency record is used. Example: 1.39
locked_task_listinteger- Are members locked from adding project tasks (Only Project Managers can add to this list)? 1 = Yes, locked to project editors, 0 = No, anyone can add tasks. Example: 1
namestring- The name of the project. Example: Website Redesign
non_billableinteger- Is this project billable? `0` = Billable, `1` = Non-billable. Example: 1
notesstring- Notes for this project. Example: Due at the start of July. Paul to present
phasesarray- `expand` field. A list of phases on this project (`phase_id`, `name`, `color`, `budget`, `start_date`, `end_date`), the list may be empty. Example: [1,2]
project_codestring- An optional third-party identifier unique across all projects enforced using case-insensitive comparison. Example: PRJ-123456
project_managerinteger- The account ID of the project owner. Example: 17393464
project_tasksarray- `expand` field. A list of the project tasks available in this project. Example: [1,2]
project_teamobject- Manages the composition and details of the project team. Example: {}
rate_card_idinteger- The ID of the [rate card](/api_reference#Rate_Cards) applied to this project. Only supported for fee-based budgets (`budget_type` = `2` or `3`). When set, it determines the bill rate for each project team member based on their role, taking priority over `default_hourly_rate` and any per-person `hourly_rate` on `project_team`. Set to `null` to remove the rate card from the project. Example: 95020
stage_idinteger- The ID of the project stage for this project. This field takes precedence over `status` when both are provided. If omitted, the first available stage related to the project's `status` will be used. Example: 1
start_datestring- The start date of this project which is either manually set or calculated from the earliest phase, milestone, allocation, or logged time. Example: 2024-11-07
statusinteger- The status of the project `0` = Draft, `1` = Tentative, `2` = Confirmed, `3` = Completed, `4` = Canceled. If both `status` and `stage_id` are provided, `stage_id` takes precedence. If only `status` is provided, the first available stage for that status will be automatically selected. Example: 2
tagsarray- List of tags. Example: ["digital","pitch"]
tentativeinteger- (Deprecated - see `status`): Is this project tentative? `1` = Yes, `0` = No. Example: 0
float_role_createCreate a new role in your Float account.WriteCreate Role
Create a new role in your Float account. Returns the role record with fields such as id, name, default_hourly_rate, created, created_by, modified, modified_by, cost_rate_history. Use float_role_create to add a new role; use float_role_update to change an existing one.
Inputs
namestringrequired- The name of the role. Example: Senior prompt engineer
cost_rate_historyarray- `expand` field. List of cost rates applied to people with the role and the effective date when they apply from. Example: [1,2]
default_hourly_ratestring- Default hourly rate applied to a fee-based project/phase team member using this role. Example: 260.000
people_countinteger- `expand` field. Count of all people currently assigned to the role. Example: 4
people_idsarray- `expand` field. List of all people by `people_id` that are currently assigned to the role. Example: [1,2]
float_role_updateUpdate an existing role in your Float account; only the fields you provide are changed.WriteUpdate Role
Update an existing role in your Float account; only the fields you provide are changed. Returns the role record with fields such as id, name, default_hourly_rate, created, created_by, modified, modified_by, cost_rate_history. Use float_role_update to modify a role; use float_role_create to add a new one. Requires role_id, typically from float_roles_list.
- Idempotent
Inputs
role_idintegerrequired- The role's ID. Example: 123
cost_rate_historyarray- `expand` field. List of cost rates applied to people with the role and the effective date when they apply from. Example: [1,2]
default_hourly_ratestring- Default hourly rate applied to a fee-based project/phase team member using this role. Example: 260.000
expandstring- Comma-delimited values expands the response with additional fields: `cost_rate_history`, `people_ids`,`people_count`. Example: Expand
namestring- The name of the role. Example: Senior prompt engineer
people_countinteger- `expand` field. Count of all people currently assigned to the role. Example: 4
people_idsarray- `expand` field. List of all people by `people_id` that are currently assigned to the role. Example: [1,2]
float_timeoff_createCreate a new time off entry in your Float account.WriteCreate Time Off Entry
Create a new time off entry in your Float account. Can book the same time off for several people at once. Returns the timeoff record with fields such as timeoff_id, timeoff_type_id, start_date, end_date, start_time, hours, timeoff_notes, repeat_state. Use float_timeoff_create to add a new time off entry; use float_timeoff_update to change an existing one.
Inputs
end_datestringrequired- End date of this time off. Example: 2019-12-06
hoursnumberrequired- Number of hours per day for this time off. Not required when a full day. Example: 6.5
people_idsarrayrequired- List of people IDs assigned to this time off. Example: ["23442","22321"]
start_datestringrequired- Start date of this time off. Example: 2019-11-16
timeoff_type_idintegerrequired- The ID of this time off type. Example: 1345
full_dayinteger- Is this time off for a full day? `1` = Yes, `0` = No. Example: 1
repeat_endstring- Date that the repeating time off will cease. Example: 2019-03-16
repeat_stateinteger- Frequency that this timeoff repeats. `0` = No repeat, `1` = Weekly, `2` = Monthly, `3` = Every two weeks, `4` = Every three weeks, `5` = Every six weeks, `6` = Every two months, `7` = Every three months, `8` = Every six months, `9` = Yearly. Example: 0
start_timestring- Start time of this time off in 24 hr format. Example: 14:00
statusinteger- Status of the time off. `1` = Tentative, `2` = Confirmed. Example: 2
timeoff_notesstring- Additional notes about the time off. Example: example
float_timeoff_updateUpdate an existing time off entry in your Float account; only the fields you provide are changed.WriteUpdate Time Off Entry
Update an existing time off entry in your Float account; only the fields you provide are changed. Returns the timeoff record with fields such as timeoff_id, timeoff_type_id, start_date, end_date, start_time, hours, timeoff_notes, repeat_state. Use float_timeoff_update to modify a time off entry; use float_timeoff_create to add a new one. Requires timeoff_id, typically from float_timeoffs_list.
- Idempotent
Inputs
timeoff_idintegerrequired- The time off's ID. Example: 123
end_datestring- End date of this time off. Example: 2019-12-06
full_dayinteger- Is this time off for a full day? `1` = Yes, `0` = No. Example: 1
hoursnumber- Number of hours per day for this time off. Not required when a full day. Example: 6.5
people_idsarray- List of people IDs assigned to this time off. Example: ["23442","22321"]
repeat_endstring- Date that the repeating time off will cease. Example: 2019-03-16
repeat_stateinteger- Frequency that this timeoff repeats. `0` = No repeat, `1` = Weekly, `2` = Monthly, `3` = Every two weeks, `4` = Every three weeks, `5` = Every six weeks, `6` = Every two months, `7` = Every three months, `8` = Every six months, `9` = Yearly. Example: 0
start_datestring- Start date of this time off. Example: 2019-11-16
start_timestring- Start time of this time off in 24 hr format. Example: 14:00
statusinteger- Status of the time off. `1` = Tentative, `2` = Confirmed. Example: 2
timeoff_notesstring- Additional notes about the time off. Example: example
timeoff_type_idinteger- The ID of this time off type. Example: 1345
float_allocation_deleteDelete a allocation from your Float account.DestructiveDelete Allocation
Delete a allocation from your Float account. This permanently removes the allocation. Returns no content (HTTP 204) on success. Use float_allocation_delete only to permanently remove a allocation; use float_allocation_update to change it instead. Requires task_id, typically from float_allocations_list.
- Idempotent
Inputs
task_idintegerrequired- The allocation as a task ID. Example: 123
float_logged_time_deleteDelete a logged time entry from your Float account.DestructiveDelete Logged Time Entry
Delete a logged time entry from your Float account. This permanently removes the logged time entry. Returns no content (HTTP 204) on success. Use float_logged_time_delete only to permanently remove a logged time entry; use float_logged_time_update to change it instead. Requires logged_time_id, typically from float_logged_times_list.
- Idempotent
Inputs
logged_time_idstringrequired- Unique ID of the specific logged time entry to be deleted. Example: 123
float_timeoff_deleteDelete a time off entry from your Float account.DestructiveDelete Time Off Entry
Delete a time off entry from your Float account. This permanently removes the time off entry. Returns no content (HTTP 204) on success. Use float_timeoff_delete only to permanently remove a time off entry; use float_timeoff_update to change it instead. Requires timeoff_id, typically from float_timeoffs_list.
- Idempotent
Inputs
timeoff_idintegerrequired- time off id to delete. Example: 123
No tools match.