Application Identity Profile Resource

Application Identity Profiles store game data associated with a user's identity in your application. This data powers Game Stats Widgets on Discord user profiles.

Profile records are stored on a user's Application Identity for your application. Each Application Identity is identified by an external account key: a provider type, an optional provider ID, and a provider-issued user ID.

For profile-only writes, if the user does not already have an Application Identity for your application, the first successful profile update creates an Application Identity with provider type NONE and the provider_issued_user_id from the request path. If an Application Identity already exists for the user and application, profile updates must use a provider_issued_user_id that matches one of the user's existing application identities.

Pre-configured fields meant to be generic across many games. All fields are optional.

Dynamic fields let you specify custom stats when the pre-configured primary fields don't cover your needs. Each dynamic field has a type that determines its value format. The name is the data key you reference in the widget editor when configuring a User Data field. It is not shown to players; display labels are configured on the widget's fields in the editor.

{
  "username": "johndoe123",
  "metadata": null,
  "data": {
    "primary": {
      "season": "Season 3",
      "rank_name": "Silver",
      "rank_image": {"url": "https://example.com/assets/rank-images/silver.png"},
      "highest_rank": "Platinum",
      "highest_rank_image": {"url": "https://example.com/assets/rank-images/platinum.png"},
      "featured_played_character": "John Doe",
      "featured_played_character_image": {"url": "https://example.com/assets/character-images/john-doe.png"},
      "playtime_hours": 69.41,
      "total_wins": 57,
      "current_period_wins": 8,
      "total_games": 100,
      "current_period_games": 10,
      "total_kills": 253,
      "current_period_kills": 35,
      "total_assists": 478,
      "current_period_assists": 68,
      "total_deaths": 561,
      "current_period_deaths": 21
    },
    "dynamic": [
      {
        "type": 1,
        "name": "my_string",
        "value": "hello"
      },
      {
        "type": 2,
        "name": "my_number",
        "value": 123.45
      },
      {
        "type": 3,
        "name": "my_media",
        "value": {"url": "https://example.com/some-media.png"}
      }
    ]
  }
}

/applications/{application_id}/users/{user_id}/identities/{provider_issued_user_id}/profile

Updates the profile data on the user's matching Application Identity record. Returns an Application Identity Profile object.

If the user does not have an Application Identity for your application yet, the first successful update creates a profile-only Application Identity with provider type NONE and the provider_issued_user_id from the path. If the user already has an Application Identity for your application, the provider_issued_user_id in the path must match an existing Application Identity.

Requires a bot token for authorization. The target user must have authorized the application via OAuth2 with the application_identities.write scope. If you are building a Social SDK integration, this scope is included in the Social SDK scopes.

The 10 KB limit applies to the serialized data object in your request, not the raw HTTP body.

Returns 201 Created on first write, 204 No Content on subsequent updates.

The Application Identity conflict errors above usually mean the requested provider_issued_user_id does not match the user's current Application Identity state. See Resolving External ID Conflicts for cleanup guidance.

/applications/{application_id}/users/{user_id}/identities/{provider_issued_user_id}/profile

Returns the Application Identity Profile object stored on the matching Application Identity for the specified user and application.

Requires a bot token for authorization. The target user must have authorized the application via OAuth2 with the application_identities.write scope. If you are building a Social SDK integration, this scope is included in the Social SDK scopes.

/users/{user_id}/application-identities/{application_id}

Returns the application identities for the specified user and application. Use this endpoint to discover the exact external ID values (provider_type, provider_issued_user_id, and optional provider_id) for a user's application identities.

This endpoint does not return profile data. To read game stats for a specific identity, use Get Application Identity Profile.

To delete an identity, use the returned values with Delete Application Identity.

Requires a bot token for authorization. The caller must authenticate as the bot for {application_id} and can only fetch identities for its own application. The target user must have authorized the application via OAuth2 with the application_identities.write scope. If you are building a Social SDK integration, this scope is included in the Social SDK scopes.

Returns 200 OK with a wrapped list of Application Identity objects. provider_id is omitted from an identity when it is absent or empty.

{
  "identities": [
    {
      "user_id": "<user_id>",
      "provider_type": "<provider_type>",
      "provider_id": "<provider_id>",
      "provider_issued_user_id": "<provider_issued_user_id>"
    }
  ]
}

/applications/{application_id}/application-identities/{provider_type}/{provider_issued_user_id}

Returns the application identities for the user/application record currently associated with the specified external ID (combination of provider_type, provider_issued_user_id, and optional provider_id). Use this endpoint when you need to resolve the Discord user_id for an Application Identity but only know the external ID fields.

This endpoint does not return profile data. To read game stats for a specific identity, use Get Application Identity Profile.

To delete an identity, use the returned values with Delete Application Identity.

Requires a bot token for authorization. The caller must authenticate as the bot for {application_id} and can only fetch identities for its own application. The matched user must have authorized the application via OAuth2 with the application_identities.write scope. If you are building a Social SDK integration, this scope is included in the Social SDK scopes.

Returns 200 OK with a wrapped list of Application Identity objects. provider_id is omitted from an identity when it is absent or empty. If no identity matches the external account key, identities is empty.

{
  "identities": [
    {
      "user_id": "<user_id>",
      "provider_type": "<provider_type>",
      "provider_id": "<provider_id>",
      "provider_issued_user_id": "<provider_issued_user_id>"
    }
  ]
}

/users/{user_id}/application-identities/{application_id}/{provider_type}/{provider_issued_user_id}/delete

Deletes one Application Identity and its associated profile data for the specified user and application. Use this endpoint when a stale provider-issued user ID prevents you from writing profile data for the user's current identity.

Uses the same bot/application authorization and OAuth2 authorization checks as Get Application Identities.

The JSON body is optional.

Deletion is blocked if it would remove the user's last account-linking identity for the application.

Profile-only NONE identities can be deleted. Deleting an identity also deletes the profile data stored on that identity.

Returns 204 No Content on success.