GET /orgs/{org}/installations/{installation_id}/repositories — no API to list repos for a 3rd-party app installation as org admin

[segiddins]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

API

Body

After a conversation with GH Copilot:

Feature Request: API endpoint to list repositories accessible to a specific GitHub App installation, as an org admin

Problem

As an org admin, I can see which repositories a third-party GitHub App is installed on via the UI at:
https://github.com/organizations/{org}/settings/installations/{installation_id}

However, there is no API equivalent for this. Specifically:

• GET /orgs/{org}/installations returns which apps are installed and their repository_selection (all or selected) ✅
• But there is no endpoint to retrieve the specific repos for a given installation as an org admin ❌

The endpoint GET /user/installations/{installation_id}/repositories exists but requires an OAuth user-to-server token authorized by that specific app — which is not obtainable for a third-party app you don't own.

What I expected

Something like:
GET /orgs/{org}/installations/{installation_id}/repositories

...returning the list of repos the app has been granted access to, accessible to org admins with a standard PAT or gh CLI token or a GHA with Administrator: Read permissions.

Why it matters

Org admins need to audit which third-party apps have access to which repos for security and compliance purposes. The UI exposes this information but the API does not, making automated auditing impossible.

[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. ⭐

[Ayushgupta2408]

hi,
I ran into the same limitation while trying to audit third-party GitHub App access across organization repositories.

The information is already visible to organization administrators in the GitHub UI, so it would be extremely useful to have an API equivalent for automation purposes. Without it, organizations have to manually inspect each installation page, which doesn't scale well for security reviews, compliance checks, or periodic access audits.

The existing /user/installations/{installation_id}/repositories endpoint isn't a practical workaround because organization administrators typically don't have access to an OAuth token for third-party apps they don't own.

Having an endpoint such as:

GET /orgs/{org}/installations/{installation_id}/repositories

with appropriate organization-level administrative permissions would help bridge the gap between the UI and API and make governance workflows significantly easier.

+1 from me — this would be a valuable addition for organizations managing multiple third-party integrations.