/user/installations returns the wrong repositories_url

[xmo-odoo]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

API

Body

/user/installations lists the app installations accessible to a user access token.

However the installations it lists have the following hardcoded value:

'repositories_url': 'https://api.github.com/installation/repositories',

This is

List repositories accessible to the app installation

it is only accessible via installation tokens, from which it gets the installation, it fails with a 403 if accessed via a user access token (and would have no idea what installation's repositories to return besides). The correct endpoint when fetching installations via a user access token should be

GET /user/installations/{installation_id}/repositories
List repositories accessible to the user access token

Returning the access_tokens_url entry also seems dubious.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[AhmadHassan-BTed]

It's a long-standing quirk in GitHub's API design.

The issue happens because GitHub reuses the exact same Installation JSON schema across multiple different API endpoints. So, whether you call /user/installations (with a user token) or /app/installations (with an app JWT), it spits out the identical object containing those hardcoded URLs (repositories_url and access_tokens_url).

Because those URLs are statically designed for the App's context rather than the User's context, following them with a User Access Token throws a 403 Forbidden error.

Like you pointed out, the only real workaround right now is to completely ignore the repositories_url provided in the response payload and manually construct the correct URL yourself using the ID:
[https://api.github.com/user/installations/](https://api.github.com/user/installations/){installation_id}/repositories

The same goes for access_tokens_url; it requires a JWT, making it completely useless for a user token. It is definitely a misleading schema choice, but ignoring the payload URLs and hardcoding the correct route is the only way to handle it right now.