Pages API not exposed in public REST API on self-hosted instances
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Description
On self-hosted Plane v1.3.0, the pages endpoints are not reachable through the public REST API (/api/v1/) with API key authentication.
Reproduction
curl -H "x-api-key: <YOUR_KEY>" \
"https://<your-plane-instance>/api/v1/workspaces/<slug>/projects/<project_id>/pages/"
# Returns: HTTP 404 Not Found
All other endpoints (issues, cycles, modules, projects, states, labels, etc.) work correctly with the same key.
Expected
Pages should be accessible via the public REST API, with full CRUD support, like the other resources.
Why this matters
Pages are essential to manage documentation and structured content in Plane. Without API access, they remain locked behind the web UI.Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the curl request against a self-hosted instance and compare the pages route with working resources such as issues or projects. Done means the /api/v1/workspaces//projects/<project_id>/pages/ endpoint is reachable with x-api-key authentication and supports the expected full CRUD operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100