{"version":"2.1.268","anchor":"rate-limit-api-error-message-component-gets-an-apierrorkin","canonical_anchor":"rate-limit-api-error-message-component-gets-an-apierrorkin","heading":"Rate-limit \/ API error message component gets an apiErrorKind prop","tier":"internal","area":"Errors","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/rate-limit-api-error-message-component-gets-an-apierrorkin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Rate-limit \/ API error message component gets an apiErrorKind prop\n\nThe API-error\/rate-limit message component now receives an apiErrorKind value\n\n**Unclear.** The finding does not say what values apiErrorKind can take or how they change what is displayed.\n\n**What**\n\nThe internal component that renders API error and rate-limit messages now takes a new `apiErrorKind` value in addition to the `isApiError` flag and its existing rate-limit callback handling.\n\n**Why**\n\nThis lets that message component distinguish between different kinds of API errors when deciding what to show, rather than only knowing that an error occurred.\n\n- Area: Errors\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}