Access token not authorized: subject not found

We recently got a 403 error when fetching /smartlock for a client account (connected via OAuth) with the error

Your access token is not authorized: Subject not found.

Under what circumstances will this error be thrown? I thought it might have been caused by the user’s email changing, but was unable to reproduce it with our account.

Hello Max,

The 403 code could indicate that the authentication is correct but the scopes are incorrect. May be the user is not allowed to view the smartlock, and hence it is 403: Forbidden or in this case, this error message is received. If you are still getting this, could you please DM (do not share on the forum) the SL ID for us to check? Thanks.