How can I know an app id #185358
Replies: 3 comments 3 replies
-
|
You’re getting a 404 because you’re calling the wrong GitHub API endpoint. The URL GitHub Apps have a numeric App ID, and that’s the only real identifier that works with the API. Unfortunately, GitHub does not provide any public API to convert a Marketplace URL or app name into an App ID. To find the real GitHub App ID, open the app’s GitHub Marketplace page, and search for Another way is to install the app on a repo or organization you control and check the installation webhook payload. |
Beta Was this translation helpful? Give feedback.
-
|
When calling the REST API endpoint like: GET https://api.github.com/apps/proven-cloud-login and similar (e.g., the PHI Network login app), getting a 404 is expected in many cases. The reason is: 404 doesn’t always mean the app doesn’t exist. GitHub returns 404 when the app isn’t publicly exposing its GitHub App metadata via the API or your token doesn’t have permission to view it. Not all Marketplace listings expose the GitHub App via the public REST response for /apps/{slug}, even if the app exists and is installable. The slug in the marketplace URL (like proven-cloud-login) is not guaranteed to return a public API object for all apps. How to find the real GitHub App ID A GitHub App actually has three identifiers: Numeric App ID – the canonical internal ID used by the API Slug – the human-readable URL part (what you see in the Marketplace) Client ID/Client Secret – for OAuth use if the app supports OAuth To reliably get the actual numeric App ID, do one of the following: ✅ If the app is installed on your org or user account: GET /users/{username}/installation or GET /orgs/{org}/installation If the app is installed, this will return an installation object and include the App ID. Alternatively, the installation listings page URL (/settings/installations) will show the installation ID in the browser, which maps back to the app. ✅ If you own or manage the GitHub App: Why /apps/{slug} returns 404 The public API for: GET https://api.github.com/apps/{slug} only works if the app has allowed public access to its metadata. Some Marketplace listings do not expose that info, so the API returns 404 instead of returning the app details. |
Beta Was this translation helpful? Give feedback.
-
|
Marketplace URL ≠ App slug – The human-readable URL (like proven-cloud-login) often doesn’t map to a public API slug. Many apps deliberately hide their metadata. No bulk listing endpoint – There’s no API to list all apps and their numeric App IDs. You can only see apps installed on your user/org, or ones you own. Marketplace plan IDs ≠ App IDs – URLs like marketplace_listing_plan_id=8335 are Marketplace-specific plans. They are not GitHub App IDs. Workarounds: Installed apps only: Use GET /orgs/{org}/installations or GET /users/{username}/installations to get App IDs for apps installed on your account/org. Developer access: If you own the app, the numeric App ID is in Developer Settings → GitHub Apps. Scraping HTML is unreliable: You could try inspecting Marketplace pages, but there’s no guaranteed numeric App ID exposed publicly. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Some apps like these for example:
https://github.com/marketplace/phi-network-login
https://github.com/marketplace/proven-cloud-login
return 404 when I try to call the api to get their ids: GET https://api.github.com/apps/proven-cloud-login
How can I find their actual github app id and how can I verify it's an actual id?
Beta Was this translation helpful? Give feedback.
All reactions