# Node js library - Error codes -- Documentation Wrong?

**URL:** <https://community.openai.com/t/node-js-library-error-codes-documentation-wrong/833488>\
**Category:** Documentation\
**Tags:** gpt-35-turbo\
**Created:** [June 21, 2024, 8:33pm UTC](https://community.openai.com/t/node-js-library-error-codes-documentation-wrong/833488 "2024-06-21T20:33:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Velkamhell](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/velkamhell/32/556332_2.png) [@Velkamhell](https://community.openai.com/u/Velkamhell)\
**Post date:** [June 22, 2024, 1:04am UTC](https://community.openai.com/t/node-js-library-error-codes-documentation-wrong/833488/3 "2024-06-22T01:04:33Z")

</div>

Thanks for your welcome!

Of course, on the [docs](https://platform.openai.com/docs/guides/error-codes/api-errors) you can find both `Api Errors` and `Python Library Errors` but for the `Api Errors` the docs don’t show any schema or object or property that you can use to identify and handle the possible errors, the docs only show the `status-code` related to each error but this is not very useful since there are many responses with these `status-codes`.

I find out the `invalid_request_error` because this is a simple error that you can cause by changing the `api-key` or passing an invalid param, but there are other errors like “Rate limit reached” or “Engine overloaded” that are very important to handle in production and they are not easy to simulate or trigger manually. So at this moment, I am just trusting in this only error response.

I may be wrong or I may not have done enough research, but I hope the docs can be updated soon to prevent any failure or unhandled exceptions in the apps that use this Node js library.

If someone knows more about this topic or has more experience using this library I will be grateful for any help. Thanks again.

---

_[View the full topic](https://community.openai.com/t/node-js-library-error-codes-documentation-wrong/833488)._
