# Blocking GetAccount example is ambiguous

**URL:** <https://forum.heroiclabs.com/t/blocking-getaccount-example-is-ambiguous/3146>\
**Category:** Game Design\
**Tags:** golang\
**Created:** [October 7, 2022, 6:12pm UTC](https://forum.heroiclabs.com/t/blocking-getaccount-example-is-ambiguous/3146 "2022-10-07T18:12:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![thealphadollar](https://avatars.discourse-cdn.com/v4/letter/t/a183cd/32.png) [@thealphadollar](https://forum.heroiclabs.com/u/thealphadollar)\
**Post date:** [October 7, 2022, 6:12pm UTC](https://forum.heroiclabs.com/t/blocking-getaccount-example-is-ambiguous/3146/1 "2022-10-07T18:12:48Z")

</div>

```auto
if err := initializer.RegisterBeforeGetAccount(func(ctx context.Context, logger runtime.Logger, db *sql.DB, nk runtime.NakamaModule) error {
    return nil
  }); err != nil {
    return err
  }

```

The above code is provided as an example to disable the GetAccount API call from the client side. However, in a successful case as well, the endpoint would return a `nil` in the response as only `error` type is accepted as the return.

How is disabling distinguished from a successful BeforeGetAccount hook?

Ref: L52 on [Nakama: Guarding APIs | Heroic Labs Documentation](https://heroiclabs.com/docs/nakama/guides/server-framework/guarding-apis/#using-before-hooks)
