API support for managing GitHub App IP allow list entries

[chriszheng278]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

API

Body

Summary

There is currently no API (REST or GraphQL) to programmatically manage IP allow list entries on a GitHub App's own settings (docs
(https://docs.github.com/en/apps/maintaining-github-apps/managing-allowed-ip-addresses-for-a-github-app)). This can only be done through the UI at Settings > Developer settings > GitHub Apps > [App] > IP allow
list. We'd like an API to add, list, update, and delete CIDR entries on a GitHub App's IP allow list.

Current state

GitHub provides comprehensive GraphQL API support for the consumer side — organizations can manage their own IP allow lists (createIpAllowListEntry, updateIpAllowListEntry, deleteIpAllowListEntry) and toggle
whether to inherit IPs from installed apps (updateIpAllowListForInstalledAppsEnabledSetting).

However, the producer side — the GitHub App's own IP allow list, which is the source of entries that orgs inherit — can only be managed manually through the web UI. There is no REST endpoint or GraphQL mutation
for it.

This creates an asymmetry: organizations can programmatically control whether to consume app IPs, but app owners cannot programmatically manage the IPs they publish.

Problem

Organizations that enforce IP allow lists and manage their own GitHub Apps need to keep App-level IP entries in sync with their infrastructure. When IPs change (e.g., due to cloud infrastructure scaling, region
changes, or CI/CD runner IP rotations), updating these entries manually through the UI is error-prone and doesn't fit into infrastructure-as-code workflows.

This becomes especially painful at scale. Organizations managing multiple GitHub Apps across multiple orgs must manually update each app's IP allow list individually through the UI whenever infrastructure IPs
change.

Current workaround

There is none beyond manually navigating to each GitHub App's settings page and editing entries by hand. This is not auditable, not version-controlled, and doesn't scale.

Proposed solution

Add API support for managing a GitHub App's IP allow list entries, authenticated via the App's JWT (consistent with other /app/* endpoints).

REST:

• GET /app/ip-allow-list — list entries
• POST /app/ip-allow-list — create entry (CIDR, name, isActive)
• PATCH /app/ip-allow-list/{entry_id} — update entry
• DELETE /app/ip-allow-list/{entry_id} — delete entry

Or GraphQL mutations analogous to the existing org-level ones, scoped to a GitHub App owner.

Use cases

• Infrastructure as Code: Manage GitHub App IP allow lists alongside other org security settings (e.g., via Terraform, Pulumi, or policy-as-code tools)
• Automated IP rotation: Programmatically update entries when infrastructure IPs change, without manual UI intervention
• Audit and compliance: Maintain a version-controlled source of truth for which IPs are authorized for a GitHub App

Related discussions

• [Feature Request] Installation-level IP Allowlist Bypass #180338 (https://github.com/orgs/community/discussions/180338) — Feature request for installation-level IP allowlist bypass, highlighting broader gaps in IP allow list management capabilities

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