Float is a resource management and workforce planning platform that gives teams real-time visibility into who is working on what and when. It combines a visual schedule with project, people, and time-tracking data so managers can plan capacity, assign work, and track time off. Its REST API exposes people, projects, clients, allocations, time off, logged time, and milestones, supporting ingestion and write-back.
Power end-to-end data operations for your Float API with Nexla. Our bi-directional Float connector is purpose-built for Float, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Float or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Float workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
To connect Nexla to Float, you will need a Float API key. Float uses Bearer token authentication — all API requests are authenticated using an API key passed in the Authorization request header.
Float API keys are available to Account Owners and Admins in the Float Team Settings. Only one API key is active per account at a time; regenerating the key will invalidate the previous one.
Click your name or avatar in the bottom-left corner, then select Team Settings.
In Team Settings, click the Integrations tab.
Under the API section, your API access token is displayed. Click Copy to copy the token to your clipboard.
Only Account Owners can view and manage the API key. If you do not see the Integrations tab or the API section, contact your Float Account Owner to obtain the token or to request that an API key be generated for your integration use case.
Store the copied API key securely. Treat it like a password — do not share it or embed it in publicly accessible code repositories. The key remains valid until it is regenerated in the Float Team Settings.
Important
Regenerating your Float API key will immediately invalidate the previous key. Any existing integrations using the old key will stop working until they are updated with the new key.
To create a new Float credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Float uses API Key authentication with a Bearer token passed in the Authorization header. All requests to the Float API are made over HTTPS to the base URL https://api.float.com/v3. Enter your Float API key in the API Key field. This is the access token you copied from your Float Team Settings in the Prerequisites section above. Nexla will send this key as a Bearer token in the Authorization header of every API request (i.e., Authorization: Bearer <your-api-key>).
Your Float API key authenticates all requests made on behalf of your Float account. Keep this key confidential and rotate it in Float Team Settings if you suspect it has been compromised. After regenerating the key in Float, update this credential in Nexla to maintain uninterrupted data flows.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Float connector tile, then select the credential that will be used to connect to the Float instance, and click Next; or, create a new Float credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Float API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List Accounts
Returns a list of all accounts accessible to the authenticated user. Use this endpoint to retrieve Float account-level information, including account IDs and configuration details, which can be useful as a reference for other API operations or for audit purposes.
This endpoint requires no additional configuration beyond selecting the template. Nexla will automatically retrieve all account records accessible to the API key associated with your credential.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
Float returns up to 200 records per page. For accounts with a large number of accessible accounts, Nexla will handle multi-page retrieval automatically using page-based pagination.
List Departments
Returns a list of all departments defined in your Float account. Use this endpoint to extract organizational structure data, such as department names and IDs, which can be joined with people and project data for workforce reporting and analysis.
This endpoint requires no additional configuration. Nexla will automatically retrieve all department records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
Department records include the department name and its unique identifier. Use the department ID when cross-referencing people records that include a department_id field.
List People
Returns a list of all people (team members) in your Float account. This is one of the most commonly used endpoints, providing access to all team member records including names, job titles, departments, roles, work hours configurations, contractor status, email addresses, and tags. Use this endpoint for workforce reporting, headcount analysis, or to build a people directory.
This endpoint requires no additional configuration. Nexla will automatically retrieve all people records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
People records include the people_id field, which is used as a foreign key in allocations, time off, and logged time records. Retaining this field is recommended when building joins across Float data sets.
List Roles
Returns a list of all roles defined in your Float account. Roles represent job functions or skill categories (e.g., "Designer," "Developer," "Project Manager") that can be assigned to team members. Use this endpoint to extract role definitions for workforce planning reports or skills-based analytics.
This endpoint requires no additional configuration. Nexla will automatically retrieve all role records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
List Public Holidays
Returns a list of all public holidays configured in your Float account. Float allows teams to configure public holiday calendars so that scheduled time off and work hours respect regional holidays. Use this endpoint to extract public holiday data for capacity planning, payroll systems, or compliance reporting.
This endpoint requires no additional configuration. Nexla will automatically retrieve all public holiday records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
List Holidays
Returns a list of all team holidays in your Float account. Unlike public holidays, team holidays are custom holidays defined specifically for your team or organization. Use this endpoint to retrieve team-specific time-off periods for capacity planning or HR reporting.
This endpoint requires no additional configuration. Nexla will automatically retrieve all team holiday records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
List Projects
Returns a list of all projects in your Float account. Project records include fields such as project name, client, color, tags, budget type, budget totals, project managers, and project team members. Use this endpoint to extract project data for project portfolio reporting, budget tracking, or integration with project management tools.
This endpoint requires no additional configuration. Nexla will automatically retrieve all project records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
Projects include a project_id field that is referenced in allocations, phases, milestones, and project tasks. Retaining this field is recommended when building joins across Float data sets.
Get Status
Returns current status information from the Float API, including status records associated with people or projects. Use this endpoint to retrieve status data for reporting or monitoring purposes.
This endpoint requires no additional configuration. Nexla will automatically retrieve all status records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
List Time Off
Returns a list of all time off entries in your Float account. Time off records include information about which team members have scheduled time away, the type of time off, and the associated dates and hours. Use this endpoint for absence reporting, capacity planning, and HR analytics.
This endpoint requires no additional configuration. Nexla will automatically retrieve all time off records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
Time off records reference people_id and timeoff_type_id fields. Use the List People and List Time Off Types endpoints to retrieve the corresponding reference data for building complete reports.
List Time Off Types
Returns a list of all time off types defined in your Float account (e.g., "Vacation," "Sick Leave," "Personal"). Use this endpoint to retrieve time off type definitions for use as a lookup reference when analyzing time off entries.
This endpoint requires no additional configuration. Nexla will automatically retrieve all time off type records from your Float account.
List Clients
Returns a list of all clients in your Float workspace. Client records store client names and their unique identifiers, which are referenced by project records. Use this endpoint to extract client data for billing reports, client portfolio analysis, or CRM integrations.
This endpoint requires no additional configuration. Nexla will automatically retrieve all client records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
List Phases
Returns a list of all project phases in your Float workspace. Phases represent distinct stages within a project (e.g., "Discovery," "Design," "Development," "Launch") and include start and end dates. Use this endpoint to track project progress across phases or to feed project timeline data into reporting tools.
This endpoint requires no additional configuration. Nexla will automatically retrieve all phase records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
List Project Tasks
Returns a list of all project tasks in your Float workspace. Project tasks define the types of work that can be allocated to team members within a project, including task names and associated budget hours. Use this endpoint to extract task definitions for project planning reports or budget utilization analysis.
This endpoint requires no additional configuration. Nexla will automatically retrieve all project task records from your Float account.
List Milestones
Returns a list of all project milestones in your Float workspace. Milestones mark key dates or deliverables within a project. Use this endpoint to extract milestone data for project tracking dashboards, delivery reporting, or project management tool integrations.
This endpoint requires no additional configuration. Nexla will automatically retrieve all milestone records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
List Tasks
Returns a list of all allocations (tasks) in your Float workspace. In Float, allocations represent scheduled work assignments that link a team member to a project for a specified date range and number of hours. Allocation records include fields such as people_id, project_id, start and end dates, hours, billable status, and repeat settings. This is one of the most analytically rich endpoints for understanding how team capacity is being utilized across projects.
This endpoint requires no additional configuration. Nexla will automatically retrieve all allocation records from your Float account.
Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.
Allocation records reference both people_id and project_id. Use the List People and List Projects endpoints to retrieve the corresponding reference data for building complete utilization and capacity reports. The Float API documentation refers to allocations as "tasks" in its endpoint path (/v3/tasks).
List Logged Time
Returns a list of all time log entries in your Float workspace. Logged time records capture actual hours worked by team members against projects and tasks, as distinct from planned allocations. Use this endpoint to extract actuals data for timesheet reporting, billing, payroll, or planned-vs-actual analysis.
This endpoint requires no additional configuration. Nexla will automatically retrieve all logged time records from your Float account.
Logged time records include people_id, project_id, date, and hours fields. Combining logged time data with allocation data enables planned-versus-actual utilization analysis across your team.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Float data sources can also be manually configured to ingest data from any valid Float API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
All Float API endpoints use the base URL https://api.float.com/v3 (e.g., https://api.float.com/v3/people); a full list of endpoint paths is available in the Float API Reference. Float's read endpoints exclusively use the GET method, accept dates in yyyy-MM-dd format, and typically return a top-level JSON array, so use $[*] as the Path to Data. The Float API also requires a User-Agent header containing your application name and a contact email (e.g., User-Agent:NexlaFloatIntegration/1.0 (your@email.com)); the Authorization header is added automatically by Nexla from your credential.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Float data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Float destination, and select the Send to Destination option from the menu. Select the Float connector from the list of available destination connectors, then select the credential that will be used to connect to the Float account, and click Next; or, create a new Float credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Float API write operations. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create Client
Creates a new client record in Float. Use this endpoint when you need to add client records to Float programmatically—for example, when synchronizing a CRM or project management tool with Float, or when onboarding new clients in bulk.
Map the client name to the name field in your Nexset. This is the required field for creating a client record in Float. Float will reject requests where the name field is absent or empty.
Each record in your Nexset will be sent to Float as a separate API call, creating one client per record.
After creation, Float assigns each client a unique client_id. This ID is referenced by project records when associating a project with a client. Consider chaining a List Clients source after this destination if downstream flows need the assigned client IDs.
Create Person
Creates a new team member (person) record in Float. Use this endpoint to add team members to Float programmatically—for example, when synchronizing an HR system or directory with Float, or when onboarding multiple new employees at once.
Map the following fields from your Nexset to the corresponding Float fields:
name (required): The full name of the team member.
email (optional): The team member's email address.
job_title (optional): The team member's job title.
department_id (optional): The ID of the department to which this person belongs. Use the List Departments source to retrieve valid department IDs.
tags (optional): An array of tags to associate with this person.
work_days_hours (optional): A configuration array specifying the number of working hours per day for each day of the week.
contractor (optional): A boolean indicating whether this person is a contractor (true) or a full-time employee (false).
Each record in your Nexset will be sent to Float as a separate API call, creating one person per record.
After creation, Float assigns each person a unique people_id. This ID is referenced by allocations, time off entries, and logged time records. Consider chaining a List People source after this destination if downstream flows need the assigned IDs.
Create Project
Creates a new project record in Float. Use this endpoint to add projects to Float programmatically—for example, when synchronizing a project management tool, ERP system, or CRM with Float to keep project records in sync.
Map the following fields from your Nexset to the corresponding Float fields:
name (required): The name of the project.
client_id (optional): The ID of the client associated with this project. Use the List Clients source to retrieve valid client IDs.
color (optional): A hex color code used to display the project in the Float schedule (e.g., #FF5733).
tags (optional): An array of tags to associate with this project.
budget_type (optional): The type of budget tracking for this project (e.g., hours or money-based).
budget_total (optional): The total budget allocated to this project.
project_manager (optional): The people_id of the team member assigned as project manager.
Each record in your Nexset will be sent to Float as a separate API call, creating one project per record.
After creation, Float assigns each project a unique project_id. This ID is referenced by allocations, phases, milestones, and project tasks. Consider chaining a List Projects source after this destination if downstream flows need the assigned project IDs.
Create Allocation
Creates a new allocation (scheduled work assignment) in Float. An allocation links a team member to a project for a specific date range and number of hours. Use this endpoint to programmatically schedule work in Float—for example, when ingesting project plans from an external tool or automating resource assignment workflows.
Map the following fields from your Nexset to the corresponding Float fields:
people_id (required): The ID of the team member to whom this work is assigned. Use the List People source to retrieve valid people IDs.
project_id (required): The ID of the project this allocation is associated with. Use the List Projects source to retrieve valid project IDs.
start_date (required): The start date of the allocation in yyyy-MM-dd format.
end_date (required): The end date of the allocation in yyyy-MM-dd format.
hours (required): The number of hours per day allocated for this assignment.
name (optional): A label or note for this allocation.
notes (optional): Additional notes about the allocation.
status (optional): The status of the allocation (e.g., confirmed or tentative).
billable (optional): A boolean indicating whether this allocation is billable.
repeat_state (optional): A value indicating whether and how the allocation repeats.
repeat_end_date (optional): The date on which a repeating allocation should stop, in yyyy-MM-dd format.
Each record in your Nexset will be sent to Float as a separate API call, creating one allocation per record.
Dates must be provided in yyyy-MM-dd format (e.g., 2026-06-15). The people_id and project_id values must correspond to existing records in Float. Use the List People and List Projects source endpoints to retrieve valid IDs before creating allocations.
Create Logged Time
Creates a new logged time entry in Float. Logged time records capture actual hours worked by a team member on a project on a specific date. Use this endpoint to write time-tracking data into Float from an external timesheet system or to bulk-import historical time records.
Map the following fields from your Nexset to the corresponding Float fields:
people_id (required): The ID of the team member who logged the time. Use the List People source to retrieve valid people IDs.
project_id (required): The ID of the project the time was logged against. Use the List Projects source to retrieve valid project IDs.
date (required): The date on which the time was worked, in yyyy-MM-dd format.
hours (required): The number of hours logged.
Each record in your Nexset will be sent to Float as a separate API call, creating one logged time entry per record.
The people_id and project_id values must correspond to existing records in Float. Dates must be in yyyy-MM-dd format.
Create Department
Creates a new department record in Float. Use this endpoint to add departments to Float programmatically—for example, when syncing organizational structure from an HR system.
Map the department name to the name field in your Nexset. This is the primary field for creating a department in Float.
Each record in your Nexset will be sent to Float as a separate API call, creating one department per record.
Create Project Expense
Creates a new project expense entry in Float. Project expenses track costs incurred for a project, such as software subscriptions, travel, or materials. Use this endpoint to log project expenses in Float from an external expense management system or financial tool.
Map the following fields from your Nexset to the corresponding Float fields:
name (required): A descriptive name for the expense (e.g., "Software License," "Travel").
date (required): The date of the expense in yyyy-MM-dd format.
cost (required): The cost amount of the expense.
project_id (required): The ID of the project this expense is associated with. Use the List Projects source to retrieve valid project IDs.
billable (optional): A boolean indicating whether this expense is billable to the client.
markup (optional): A markup percentage or amount applied to the expense for billing.
markup_type (optional): The type of markup (e.g., percentage or fixed amount).
Each record in your Nexset will be sent to Float as a separate API call, creating one expense record per record.
Create Milestone
Creates a new project milestone in Float. Milestones mark key dates or deliverables within a project. Use this endpoint to programmatically add milestones to Float projects—for example, when importing a project plan from an external scheduling or project management tool.
Map the milestone name, associated project ID, and target date fields from your Nexset to the corresponding Float fields.
Each record in your Nexset will be sent to Float as a separate API call, creating one milestone per record.
The project_id value must correspond to an existing project in Float. Dates must be in yyyy-MM-dd format.
Update Client
Updates an existing client record in Float. Use this endpoint to modify client attributes—for example, renaming a client or updating their details when a change occurs in your CRM or billing system.
Enter the ID of the client to be updated in the Client Id parameter field. This is a required parameter that identifies which client record Float should update. Use the List Clients source to retrieve valid client IDs.
Map the updated client fields from your Nexset (such as name) to the corresponding Float fields. Only the fields included in the payload will be updated; other fields will remain unchanged.
Each record in your Nexset will be sent to Float as a separate PATCH request, updating one client per record.
The Float API uses PATCH for update operations, meaning only the fields included in the request body will be modified. Fields not included in the payload will retain their existing values.
Update Department
Updates an existing department record in Float. Use this endpoint to rename or modify department attributes when organizational changes occur.
Enter the ID of the department to be updated in the Department Id parameter field. This is a required parameter. Use the List Departments source to retrieve valid department IDs.
Map the updated department fields from your Nexset to the corresponding Float fields. Only the fields included in the payload will be updated.
Each record in your Nexset will be sent to Float as a separate PATCH request, updating one department per record.
Update Logged Time
Updates an existing logged time entry in Float. Use this endpoint to correct or modify previously logged time records—for example, to adjust hours, update the date, or add notes to an existing entry.
Enter the ID of the logged time entry to be updated in the Logged Time Id parameter field. This is a required parameter. Use the List Logged Time source to retrieve valid logged time IDs.
Map the updated fields from your Nexset (such as hours, date, or notes) to the corresponding Float fields. Only the fields included in the payload will be updated.
Each record in your Nexset will be sent to Float as a separate PATCH request, updating one logged time entry per record.
Update Project Task
Updates an existing project task definition in Float. Use this endpoint to modify project task attributes such as task name or budget hours when project scope or planning changes.
Enter the ID of the project task to be updated in the Task Id parameter field. This is a required parameter. Use the List Project Tasks source to retrieve valid task IDs.
Map the updated task fields from your Nexset (such as name or budget_hours) to the corresponding Float fields. Only the fields included in the payload will be updated.
Each record in your Nexset will be sent to Float as a separate PATCH request, updating one project task per record.
Update Time Off
Updates an existing time off entry in Float. Use this endpoint to modify time off records when dates, hours, or other attributes change—for example, when syncing approved time off from an HR system into Float.
Enter the ID of the time off entry to be updated in the Timeoff Id parameter field. This is a required parameter. Use the List Time Off source to retrieve valid time off IDs.
Map the updated fields from your Nexset to the corresponding Float fields. Only the fields included in the payload will be updated.
Each record in your Nexset will be sent to Float as a separate PATCH request, updating one time off entry per record.
The Float API uses PATCH for update operations, meaning only the fields included in the request body will be modified. Fields not included in the payload will retain their existing values.
Create a Project Phase
Creates a new project phase in Float. Phases represent distinct stages within a project (e.g., "Discovery," "Design," "Development," "Launch") and include start and end dates. Use this endpoint to programmatically add phases to Float projects when managing project timelines from an external planning tool.
Map the phase name, associated project ID, start date, and end date fields from your Nexset to the corresponding Float fields.
Each record in your Nexset will be sent to Float as a separate API call, creating one phase per record.
The project_id value must correspond to an existing project in Float. Dates must be in yyyy-MM-dd format.
Float destinations can also be manually configured to send data to any valid Float API endpoint not covered by the pre-built templates. Using manual configuration, you can also configure Nexla to automatically send the response received from the Float API after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Float uses POST to create new records, PATCH for partial updates, PUT to replace records entirely, and DELETE to remove records, all in application/json format at the base URL https://api.float.com/v3 (e.g., https://api.float.com/v3/projects to create a project, or https://api.float.com/v3/clients/123 to update client 123). The Float API also requires a User-Agent header containing your application name and a contact email (e.g., User-Agent:NexlaFloatIntegration/1.0 (your@email.com)); the Authorization header is added automatically by Nexla from your credential.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Float endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Float until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
