Get pipeline data for date range

What is the Pipeline? The Pipeline is Leadtime’s weekly planning tool that provides a visual overview of all tasks scheduled for team members during a selected period. It shows team members vertically and calendar weeks horizontally, with each colored card representing a planned task. The pipeline is used in weekly planning meetings to schedule tasks according to importance and capacity, optimizing the use of available working time.

What data is returned: The response contains a complete pipeline view for the specified date range:

• users: Object keyed by userId, each containing:
  • Employee information (employeeId, userId, name)
  • days: Array of day data including work day length, weekends, holidays, vacations, and sickness
  • items: Array of pipeline items (planned tasks) with task details, dates, and times
  • reality: Array of actual time logs (if enabled and user has permission)
• ready: Boolean indicating if the week is marked as active/approved
• year and week: ISO week number for the pipeline period

How it works:

• Pipeline items are filtered to include tasks that start, end, or span across the specified date range
• The order of tasks in the pipeline automatically transfers to each team member’s personal stack (Kanban board)
• Dates are normalized to UTC and should be provided in ISO format (YYYY-MM-DD)
• The pipeline supports two view modes: Overview (8-hour blocks) and Spacious (15-minute increments)

Permission-based Filtering:

• usersFilter: "all" - Requires Pipeline.canViewAll permission to view all users
• usersFilter: "me" - Requires Pipeline.canViewOwnTeams or Pipeline.canViewAll permission to view own data
• usersFilter: "team:{teamId}" - Requires Pipeline.canViewOwnTeams permission and user must be a member of the specified team

Reality Data (Time Logs):

• Set withReality: true to include actual booked working hours alongside planned tasks
• Only includes time logs if user has Tasks.seeLoggedTime permission
• If permission is missing, the reality array will be empty
• This helps compare planned vs. actual work and improve future capacity estimates

Important - Understanding Time Format: In the response, items[].dateStart and items[].dateEnd contain both date and time components:

• The date part (YYYY-MM-DD) represents the calendar day
• The time part (HH) represents hours since the beginning of the work day, NOT since midnight
• Times are stored in 15-minute increments (0, 15, 30, 45, 60, etc.) from work day start
• Example: If work day starts at 09:00:
  • "2025-10-20T00:30:00Z" means 09 on Oct 20
  • "2025-10-20T05:30:00Z" means 14 on Oct 20
• When reading these values, extract the time component relative to work day start, not midnight

Use cases:

• Display weekly planning view in custom dashboards or integrations
• Export pipeline data for reporting and analysis
• Compare planned vs. actual work (with reality data)
• Build custom planning tools that integrate with Leadtime’s pipeline system

curl -X GET "https://leadtime.app/api/public/tasks/pipeline?dateStart=2025-10-20&dateEnd=2025-11-02&usersFilter=me" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

const response = await fetch("https://leadtime.app/api/public/tasks/pipeline?dateStart=2025-10-20&dateEnd=2025-11-02&usersFilter=me", {
  method: "GET",
  headers: {
    "Authorization": "Bearer YOUR_ACCESS_TOKEN"
  }
});

import requests

response = requests.get(
    "https://leadtime.app/api/public/tasks/pipeline?dateStart=2025-10-20&dateEnd=2025-11-02&usersFilter=me",
    headers={
        "Authorization": "Bearer YOUR_ACCESS_TOKEN"
    },
)

{
  "ready": true,
  "users": {
    "user-id-1": {
      "days": [],
      "employeeId": "employee-id-1",
      "items": [],
      "name": "John Doe",
      "reality": [],
      "userId": "user-id-1"
    }
  },
  "week": 43,
  "year": 2025
}