Electronic Arts · OAuth Scopes

Electronic Arts OAuth Scopes

OAuth 2.0 searched

Electronic Arts publishes 4 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Electronic Arts API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

GamingVideo GamesEntertainmentConsumerPlayer ServicesFortune 1000

Scopes: 4 Flows: Method: searched

Scopes (4)

Scope	Description	Flows
openid	OpenID Connect authentication. Required to receive an RS256-signed ID token from accounts.ea.com. Description is the OIDC Core 1.0 definition; EA publishes none of its own.
email	Releases the email and email_verified claims, both of which are listed in claims_supported.
phone	Releases the phone_number and phone_number_verified claims, both listed in claims_supported.
profile	Releases the profile claims EA lists in claims_supported: name, given_name, family_name, gender, locale and auth_time.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-06'
method: searched
source: >-
  scopes_supported in https://accounts.ea.com/.well-known/openid-configuration (HTTP 200,
  fetched 2026-09-06, saved verbatim to well-known/electronic-arts-openid-configuration.json).
  No scope reference page is published by EA; searched www.ea.com, help.ea.com and the FC
  Community API announcement and none exists.
provider: Electronic Arts
providerId: electronic-arts
authorization_server: https://accounts.ea.com/connect/auth
scope_count: 4
scopes:
- name: openid
  description: >-
    OpenID Connect authentication. Required to receive an RS256-signed ID token from
    accounts.ea.com. Description is the OIDC Core 1.0 definition; EA publishes none of its own.
  source: discovery document
- name: email
  description: >-
    Releases the email and email_verified claims, both of which are listed in
    claims_supported.
  source: discovery document
- name: phone
  description: >-
    Releases the phone_number and phone_number_verified claims, both listed in
    claims_supported.
  source: discovery document
- name: profile
  description: >-
    Releases the profile claims EA lists in claims_supported: name, given_name, family_name,
    gender, locale and auth_time.
  source: discovery document
claims_supported:
- sub
- aud
- exp
- iat
- iss
- email
- email_verified
- family_name
- given_name
- gender
- auth_time
- locale
- name
- phone_number
- phone_number_verified
- c_hash
- at_hash
notes:
- >-
  These four are the IDENTITY scopes only. The EA SPORTS FC Community API grants partners
  permission to read Ultimate Team data — "players, formations, tactics, and more" in EA's
  own words — and whatever scope strings carry that grant are NOT published in the discovery
  document or anywhere else on EA's public surface.
- >-
  A consent screen exists (EA: "You'll be asked to grant that website permission to make
  specific requests to FC services on your behalf") but its scope labels are visible only
  to approved partners' users.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/electronic-arts-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.