> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Planning projections

> Read the Blueprint critical path and blocked tasks over the Platform API.

The planning projections read tasks across a roadmap or the whole deployment. They use the `objectives:read` scope and require that permission at the deployment root, and the credential's scopes must also include `projects:read`: a task is included only when it is an ordinary project task (it has a project and no factory) whose project the caller may read (`projects:read` at the project's home). Other tasks are omitted without a count, and no assignee is ever named, so the answer is narrower than the Console's views.

## Operations

* [Get critical path](https://docs.gloo.com/forge/reference/http-api/planning/getCriticalPath.md) — a roadmap's tasks, least slack first
* [List blocked tasks](https://docs.gloo.com/forge/reference/http-api/planning/listBlockedTasks.md) — `BLOCKED` tasks that name a blocker, newest first

Each answer is `{ tasks }` with `meta.partial`. `meta.partial` is `true` when a read bound was reached, more than 50 distinct projects had to be decided in one request, or a project's read could not be decided; narrow the request (a workstream or a project) to see the rest. A person's own blockers and the tasks they could help with stay Console views.

## My blocked tasks and tasks I could help with

These admin routes run the Blueprint's two person views for a Personal key, which acts as its owner. Any other key, and an External App, is refused with `403` and `personRequired: true`.

* `GET /api/v3/me/blockers` lists the owner's own tasks that wait on a blocker.
* `GET /api/v3/planning-could-help` lists the blocked tasks the owner could help with, newest first: for a person, the tasks of the people in their org units and unassigned tasks; for an agent's owner, the tasks its skills match; with no worker record, every blocked task not the owner's.

Both need `objectives:read` at the deployment root, as the Console does, and take an optional `limit` (1 to 100, default 50; a larger value is `400` `too_big`). Each lists only what the [planning projections](https://docs.gloo.com/forge/reference/http-api/planning) list: an ordinary project task (it has a project and no factory) whose project the key may read (`projects:read` at the project's home). Other tasks are left out without a count, so a key whose scopes stop short of `projects:read` reads none. No assignee is named. The answer is `{ tasks, partial }`: `partial` is `true` when the raw read reached its bound or a project's decision ran out.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.