List project page templates
Return the page templates that belong to one project, as a paginated list.
The list holds this project's templates only. It doesn't include workspace-level templates, which are on List workspace page templates. In a workspace with workspace governance turned on, Plane has moved project page templates to the workspace, so this list is usually empty there.
Rows leave out description_html and template_data unless you ask for them with ?fields=.
Path Parameters
slug:requiredstringThe workspace slug. It appears in your Plane URLs, so in https://app.plane.so/my-team/projects/ the slug is my-team.
project_id:requiredstringThe project whose page templates you want to list. Accepts the project UUID or its identifier, for example ENG.
Query Parameters
Filters combine with AND.
name:optionalstringReturn templates whose name matches exactly, ignoring case.
is_published:optionalbooleanReturn only published (true) or only unpublished (false) templates.
short_id:optionalstringReturn the template with this short_id.
search:optionalstringA search term matched against name and short_description.
Ordering
order_by:optionalstringField to sort by. Prefix with - for descending. Defaults to -created_at, newest first.
created_at,-created_atid,-id
Both orderings work with cursor pagination.
Pagination
per_page:optionalintegerPage size. Defaults to 50, maximum 200.
offset:optionalintegerNumber of rows to skip from the start of the result set. Maximum 10000. Read the next value from the response rather than computing offsets yourself.
paginate:optionalstringSet to cursor to opt into the COUNT-free keyset envelope, which returns next_cursor and has_more instead of next and total_count. Omit it for the default offset envelope.
count:optionalbooleanDefaults to true. Set to false to skip the COUNT(*) behind total_count. The field is then omitted from the response.
Response shaping
fields:optionalstringComma-separated list of fields to return on each row. Unrequested keys are omitted from the response, not returned as null, so absent means "not requested" and null means "actually null". id always comes back whether or not you name it.
Pass all for every requestable field. An unknown name is a 400 that lists the valid set and suggests the closest match, so a typo can't silently cost you the saving.
description_html and template_data are deferred on list rows. Name them, or pass all, to include them.
Requestable here: created_at, created_by_id, description_html, id, is_published, name, project_id, short_description, short_id, slug, template_data, template_type, updated_at, updated_by_id.
See Sparse fields.
Scopes
templates.pages:read
Errors
| Status | Code | Cause |
|---|---|---|
400 | invalid_request | ?fields= names an unknown field. |
401 | unauthorized | Missing or invalid credentials. |
402 | payment_required | Page templates aren't in your plan, or the feature is switched off for this workspace. |
403 | forbidden | Your role or token scope can't read this project's page templates. |
404 | not_found | No such workspace or project, or it's outside your tenant. |
406 | not_acceptable | The Accept header asks for a representation the API can't produce. |
429 | rate_limited | Throttled. Honor the Retry-After header before retrying. |
curl -X GET \
"https://api.plane.so/api/v2/workspaces/my-team/projects/4af68566-94a4-4eb3-94aa-50dc9427067b/page-templates/?per_page=50" \
-H "X-Api-Key: $PLANE_API_KEY"import requests
response = requests.get(
"https://api.plane.so/api/v2/workspaces/my-team/projects/4af68566-94a4-4eb3-94aa-50dc9427067b/page-templates/",
headers={"X-Api-Key": "your-api-key"},
params={"per_page": 50},
)
print(response.json())const params = new URLSearchParams({ per_page: "50" });
const response = await fetch(
`https://api.plane.so/api/v2/workspaces/my-team/projects/4af68566-94a4-4eb3-94aa-50dc9427067b/page-templates/?${params}`,
{
headers: {
"X-Api-Key": "your-api-key",
},
},
);
const data = await response.json();{
"data": [
{
"id": "9e1c7a52-3b4d-4f86-a0d2-5c8e7b1f3a94",
"name": "Incident postmortem",
"short_description": "Timeline, impact, root cause, and follow-ups",
"template_type": "page",
"is_published": false,
"short_id": "m5v8c1",
"slug": "incident-postmortem",
"project_id": "4af68566-94a4-4eb3-94aa-50dc9427067b",
"created_at": "2026-01-14T09:22:41.478363Z",
"updated_at": "2026-01-14T09:22:41.478363Z",
"created_by_id": "16c61a3a-512a-48ac-b0be-b6b46fe6f430",
"updated_by_id": null
},
{
"id": "1a7d3e9b-5c2f-4b80-9e46-8d0c2f7a1b53",
"name": "Design review",
"short_description": "Context, options considered, and the decision",
"template_type": "page",
"is_published": false,
"short_id": "d2h6ne",
"slug": "design-review",
"project_id": "4af68566-94a4-4eb3-94aa-50dc9427067b",
"created_at": "2026-01-09T11:37:54.019362Z",
"updated_at": "2026-01-09T11:37:54.019362Z",
"created_by_id": "16c61a3a-512a-48ac-b0be-b6b46fe6f430",
"updated_by_id": null
}
],
"next": null,
"previous": null,
"total_count": 2,
"pagination": {
"style": "offset"
}
}
