apiApplication

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "#/components/schemas/microsoft.graph.apiApplication",
  "title": "apiApplication",
  "required": [
    "@odata.type"
  ],
  "type": "object",
  "properties": {
    "acceptMappedClaims": {
      "type": "boolean",
      "description": "When true, allows an application to use claims mapping without specifying a custom signing key.",
      "nullable": true
    },
    "knownClientApplications": {
      "type": "array",
      "items": {
        "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
        "type": "string",
        "format": "uuid",
        "nullable": true
      },
      "description": "Used for bundling consent if you have a solution that contains two parts: a client app and a custom web API app. If you set the appID of the client app to this value, the user only consents once to the client app. Microsoft Entra ID knows that consenting to the client means implicitly consenting to the web API and automatically provisions service principals for both APIs at the same time. Both the client and the web API app must be registered in the same tenant."
    },
    "oauth2PermissionScopes": {
      "type": "array",
      "items": {
        "$ref": "#/components/schemas/microsoft.graph.permissionScope"
      },
      "description": "The definition of the delegated permissions exposed by the web API represented by this application registration. These delegated permissions may be requested by a client application, and may be granted by users or administrators during consent. Delegated permissions are sometimes referred to as OAuth 2.0 scopes."
    },
    "preAuthorizedApplications": {
      "type": "array",
      "items": {
        "$ref": "#/components/schemas/microsoft.graph.preAuthorizedApplication"
      },
      "description": "Lists the client applications that are preauthorized with the specified delegated permissions to access this application's APIs. Users aren't required to consent to any preauthorized application (for the permissions specified). However, any other permissions not listed in preAuthorizedApplications (requested through incremental consent for example) will require user consent."
    },
    "requestedAccessTokenVersion": {
      "maximum": 2147483647,
      "minimum": -2147483648,
      "type": "number",
      "description": "Specifies the access token version expected by this resource. This changes the version and format of the JWT produced independent of the endpoint or client used to request the access token.  The endpoint used, v1.0 or v2.0, is chosen by the client and only impacts the version of id_tokens. Resources need to explicitly configure requestedAccessTokenVersion to indicate the supported access token format.  Possible values for requestedAccessTokenVersion are 1, 2, or null. If the value is null, this defaults to 1, which corresponds to the v1.0 endpoint.  If signInAudience on the application is configured as AzureADandPersonalMicrosoftAccount or PersonalMicrosoftAccount, the value for this property must be 2.",
      "format": "int32",
      "nullable": true
    },
    "@odata.type": {
      "type": "string"
    }
  }
}