If you’d like to preserve your Float schedule data offline or import it into another service, the Float API supports task export.

We’ll return all active tasks in order of task_id.

GET /v3/tasks HTTP/1.1
Host: https://api.float.com 

The response is a list of task objects:

HTTP/1.1 200 OK
Content-Type: application/json

[
    {
          {
            "task_id": 946615,
            "project_id": 101161,
            "start_date": "2017-02-01",
            "end_date": "2017-02-01",
            "hours": "2.0",
            "people_id": 54540,
            "priority": 0,
            "name": null,
            "notes": null,
            "repeat_state": 0,
            "repeat_end_date": null,
            "created_by": 24526,
            "created": "2017-02-04 13:16:04",
            "modified_by": 24526,
            "modified": "2017-02-04 21:01:18"
      },
      {
            "task_id": 946634,
            "project_id": 101161,
            "start_date": "2017-02-01",
            "end_date": "2017-02-02",
            "hours": "3.0",
            "people_id": 46680,
            "priority": 0,
            "name": null,
            "notes": null,
            "repeat_state": 0,
            "repeat_end_date": null,
            "created_by": 24526,
            "created": "2017-02-04 13:21:32",
            "modified_by": 0,
            "modified": "2017-02-04 13:21:32"
      }
]

You can customize this export range by specifying the start date, end date and specific person as query parameters. Say you needed to export all of your team’s tasks for 2017. You could filter by:

GET /v3/tasks?start_date=2017-01-01&end_date=2017-12-31 HTTP/1.1
Host: https://api.float.com 

If you’d like to export a specific department or person’s tasks, you could do that too by adding the people_id query parameter:

GET /v3/tasks?start_date=2017-01-01&end_date=2017-12-31&people_id=12345 HTTP/1.1
Host: https://api.float.com