GitHub REST API
/projects/* endpoint removal
Stopped workingSubscribe to GitHub REST APIShare
Calls to /projects/* on GitHub REST API stopped working on April 1, 2025.
Calls it hits
/projects/*
What to use instead of these calls
Migrate to Projects (the new experience) and use its GraphQL API or the REST endpoints under /orgs/{org}/projectsV2 and /users/{user_id}/projectsV2.
In GitHub REST API's words
April 1, 2025: The REST API for Projects (classic) will be sunset.
Facts
- API
- GitHub REST API
api.github.com - Kind
- Endpoint removal
- Announced
- May 23, 2024
- Takes effect
- April 1, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against GitHub REST API's own pages
Questions
When does this change take effect?
Calls to /projects/* on GitHub REST API stopped working on April 1, 2025.
What happens to calls after April 1, 2025?
They have failed since April 1, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from GitHub REST API 10
-
/orgs/{id}/projectsEndpoint removal Stopped working -
/orgs/{id}/teams/{id}/projects*Endpoint removal Stopped working -
/repos/{id}/{id}/projectsEndpoint removal Stopped working -
/teams/{id}/projects*Endpoint removal Stopped working -
GET /users/{id}/projectsEndpoint removal Stopped working -
POST /user/projectsEndpoint removal Stopped working -
GET /enterprises/{id}/settings/billing/actionsEndpoint removal Stopped working -
GET /enterprises/{id}/settings/billing/packagesEndpoint removal Stopped working -
GET /enterprises/{id}/settings/billing/shared-storageEndpoint removal Stopped working -
GET /orgs/{id}/settings/billing/actionsEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.