# Any documentation on all possible Notecard Status Codes for each request?

**URL:** <https://discuss.blues.com/t/any-documentation-on-all-possible-notecard-status-codes-for-each-request/3336>\
**Category:** Notecard API\
**Created:** [October 20, 2025, 2:40pm UTC](https://discuss.blues.com/t/any-documentation-on-all-possible-notecard-status-codes-for-each-request/3336 "2025-10-20T14:40:39Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tjvantoll](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tjvantoll/32/231_2.png) [@tjvantoll](https://discuss.blues.com/u/tjvantoll)\
**Post date:** [October 20, 2025, 3:45pm UTC](https://discuss.blues.com/t/any-documentation-on-all-possible-notecard-status-codes-for-each-request/3336/3 "2025-10-20T15:45:43Z")

</div>

Hey @Jakov,

And welcome to the Blues community!

> I’ve noticed that you’ve noted (here: [What is the list of possible return values for hub.sync.status? - #2 by bsatrom](https://discuss.blues.com/t/what-is-the-list-of-possible-return-values-for-hub-sync-status/68/2) ) the lack of documentation. But since then, was there any progress on this?

The guide you link to is the one main update we’ve since that thread. Were you looking for more information about the values coming back from `hub.sync.status` specifically, or was your question more broad?

In general, we recommend writing host firmware that checks for specific codes you expect or have encountered, while also handling unknown errors gracefully—since new versions of Notecard firmware may introduce additional codes over time.

TJ

---

_[View the full topic](https://discuss.blues.com/t/any-documentation-on-all-possible-notecard-status-codes-for-each-request/3336)._