FunnelHound / Guides / Apple Team ID
Apple Team ID: where to find it (and where it's needed)
Short version: sign in at developer.apple.com → Account → Membership details and read the Team ID row. Ten uppercase letters and digits, like A1B2C3D4E5. Xcode prints the same value in parentheses next to your team name under Signing & Capabilities. It is not in App Store Connect, and looking there is where most of the lost afternoons go.
Four places it shows up, ranked by how fast you get there
- 1. developer.apple.com → Account → Membership details. The Team ID has its own row. This is the canonical source; copy from here whenever a form asks for it.
- 2. Xcode → project → target → Signing & Capabilities → Team. The dropdown reads Team Name (A1B2C3D4E5). Same value, handy when you are already in the editor.
- 3. developer.apple.com → Certificates, Identifiers & Profiles → Identifiers. Open any App ID and look at the App ID Prefix. On current accounts the prefix is the Team ID.
- 4. Keychain Access → any Apple Development or Apple Distribution certificate. The Organizational Unit (OU) field carries the Team ID, because every signing certificate is stamped with the team that owns it.
Take option one unless you are already standing somewhere else. Option four exists for the morning the portal is down and a CI job wants the value in the next five minutes.
Not in App Store Connect. Stop looking there.
Apple runs two sites with two separate families of identifiers. developer.apple.com owns everything about signing and capabilities: Team ID, certificates, App IDs, push keys. App Store Connect owns everything about the store listing and its API: Issuer ID, Key IDs, Vendor Number. The Team ID belongs to the first family, so App Store Connect never puts it on a prominent page. Digging through Users and Access for it is the most common detour, and it ends at an Issuer ID that looks nothing like what you need.
A practical tell: FunnelHound never asks for the Team ID; it wants the App Store Connect API trio instead, which is the quickest way to tell the two families of IDs apart. If a tool asks for a .p8 file plus two IDs, it lives in the App Store Connect family. If it asks for a Team ID and a bundle ID, it lives on developer.apple.com.
What the Team ID is actually for
The Team ID is Apple's name for your account as a signing authority. Anything that has to prove "this app really comes from this team" carries it:
- Universal links. The apple-app-site-association file on your server lists appID values as TEAMID.bundle.id, so A1B2C3D4E5.com.company.app. Wrong Team ID and links open in Safari instead of the app, with no error anywhere.
- Entitlements. associated-domains and keychain-access-groups are prefixed with the App ID prefix, which is the Team ID. Xcode writes $(AppIdentifierPrefix) for you; the portal and most server configs want the literal value.
- Push notifications. With token-based APNs authentication, the provider JWT's iss claim is the Team ID, alongside an APNs Key ID in the header. Push services ask for all three: Team ID, Key ID, .p8.
- Wallet passes. teamIdentifier in pass.json has to match the team whose certificate signed the pass.
- Everything else that trusts your app. Sign in with Apple server configuration, App Groups shared between apps from one team, and any SDK with an "Apple Team ID" field: deep-link services, attribution, push providers.
Rule of thumb: if a feature involves a server that must trust your app, the Team ID is how that trust gets spelled.
Look-alikes that get pasted into the wrong box
| Value | Shape | Identifies | Lives on |
|---|---|---|---|
| Team ID | 10 chars, A1B2C3D4E5 | Your developer account | developer.apple.com |
| API Key ID | 10 chars | One App Store Connect API key | App Store Connect |
| APNs Key ID | 10 chars | One push key | developer.apple.com → Keys |
| Issuer ID | UUID | Your team, for the App Store Connect API | App Store Connect |
| Vendor Number | Numeric | Your sales-reporting entity | App Store Connect |
Three 10-character codes, three different meanings, and every one of them fits in the field meant for another. The API Key ID mix-up is frequent enough to get its own page. The UUID-shaped one is covered in the Issuer ID guide, and generating the key that goes with it is in the API key setup walkthrough. Check the shape before you paste: a UUID in a Team ID field is a wrong-family error, not a typo.
On more than one team?
Invited to a client's account, a day-job account and your own? That is three Team IDs. The one you want belongs to the team that owns the bundle ID you are shipping, which is the team selected in Xcode's dropdown for that target. Membership details on developer.apple.com follows the team picker at the top of the page, so confirm which team is active before copying anything.
Done with signing IDs? The store numbers live elsewhere
FunnelHound skips the Team ID entirely: Key ID, Issuer ID and a .p8 file, and your App Store funnel (impressions, taps, installs, deletions) lands on your iPhone, pulled straight from Apple.
Get FunnelHoundData notes: locations verified against developer.apple.com, Xcode and Keychain Access as of 2026. Apple relocates Membership details every few years; the account search box still finds it. A1B2C3D4E5 is a placeholder, not a real team. For current accounts the App ID prefix matches the Team ID; a handful of very old accounts still carry legacy prefixes that differ.