{"version":"2.1.190","anchor":"credits-balance-api-graceful-handling-when-amount-is-missing","canonical_anchor":"credits-balance-api-graceful-handling-when-amount-is-missing","heading":"Credits Balance API: Graceful Handling When Amount is Missing","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.190\/e\/credits-balance-api-graceful-handling-when-amount-is-missing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.190","markdown":"### Credits Balance API: Graceful Handling When Amount is Missing\n\nThe prepaid credits balance fetch now checks whether the `amount` field in the API response is a number before using it. If the field is absent (for example, on accounts or regions where the endpoint is not supported), the fetch returns null and records a `not_supported` telemetry event rather than passing undefined through to the balance display.\n\n**Evidence**\n\nguard added before `ke(\"api_prepaid_balance_fetch\")` (search for `\"not_supported\"` in prepaid balance fetch context)"}