# Lock library: log stream

**URL:** <https://community.auth0.com/t/lock-library-log-stream/98697>\
**Category:** Get Help\
**Tags:** users, management-api\
**Created:** [January 23, 2023, 9:53am UTC](https://community.auth0.com/t/lock-library-log-stream/98697 "2023-01-23T09:53:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![snacker00](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/snacker00/32/42908_2.png) [@snacker00](https://community.auth0.com/u/snacker00)\
**Post date:** [January 23, 2023, 9:53am UTC](https://community.auth0.com/t/lock-library-log-stream/98697/1 "2023-01-23T09:53:23Z")

</div>

According to the documentation (link below), you can update user metadata using the Lock library.  
If you update user metadata via this library, will the event show up in the log stream, and will it be possible to monitor it as a SAPI event?

> **[Understand How Metadata Works in User Profiles](https://auth0.com/docs/manage-users/user-accounts/metadata#use-the-lock-library)**
>
> Describes Auth0 user, application, and client metadata. Learn how you can use metadata to store information that does not originate from an identity provider.

---

<div class="post-metadata">

**Author:** ![SaqibHussain](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/saqibhussain/32/42924_2.png) [@SaqibHussain](https://community.auth0.com/u/SaqibHussain)\
**Post date:** [January 23, 2023, 2:42pm UTC](https://community.auth0.com/t/lock-library-log-stream/98697/2 "2023-01-23T14:42:16Z")

</div>

Hi @snacker00

Welcome to the Auth0 Community.

Yes it is possible to update metadata via Lock using additionalSignUpFields as per this example [https://auth0.com/docs/libraries/lock/lock-configuration#text-fields](https://auth0.com/docs/libraries/lock/lock-configuration#text-fields)

However, the metadata update will not show in the log as a separate item, you will only see it under the Success Signup (type: ss) under Raw Data i.e. amongst the data that was posted as part of the user creation process.

Warm regards.

---

<div class="post-metadata">

**Author:** ![snacker00](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/snacker00/32/42908_2.png) [@snacker00](https://community.auth0.com/u/snacker00)\
**Post date:** [January 24, 2023, 1:00pm UTC](https://community.auth0.com/t/lock-library-log-stream/98697/3 "2023-01-24T13:00:58Z")

</div>

Thank you for the quick answer.  
One more question, is this SDK based on management API or public?

Best.

---

<div class="post-metadata">

**Author:** ![SaqibHussain](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/saqibhussain/32/42924_2.png) [@SaqibHussain](https://community.auth0.com/u/SaqibHussain)\
**Post date:** [January 24, 2023, 1:38pm UTC](https://community.auth0.com/t/lock-library-log-stream/98697/4 "2023-01-24T13:38:15Z")

</div>

Hi @snacker00  
I believe the Lock SDK uses the sign up endpoint from the Authentication API [https://auth0.com/docs/api/authentication#signup](https://auth0.com/docs/api/authentication#signup)

Warm regards.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [February 7, 2023, 1:38pm UTC](https://community.auth0.com/t/lock-library-log-stream/98697/5 "2023-02-07T13:38:33Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.