[Bug Report: API Field Missing]

[Fahad-Habib]

🐛 Describe the Bug

If the user does not exist in the system, we are getting 401 Unauthorized and same is the case for Invalid JWT, I believe there should be a proper status code (404) in case of non-existent Users. Also, I have noticed that if I try to access the details of a user that was deleted, the response of the API is different and if the user ID never existed in the CRM, the response is different.

📍 API Endpoint

https://services.leadconnectorhq.com/users/:userId

✅ Expected Behavior

I believe there should be a proper status code (404) in case of non-existent Users.

💻 Screenshots or Code Samples

{
    "message": "The user does not exist.",
    "error": "Unauthorized",
    "statusCode": 401
}

Product Area

users

📋 Use Case

I need to handle different cases when making GHL request and in case of token expiry I need to refresh token and for that I am using 401 status, but if the multiple cases can return 401 status that will cause integrity issues in our system.

🚨 Why Should This Be Prioritized?

It's blocking our integration of User related webhooks, since the webhook does not provide the user_type and only provides user_role, I need to call the GHL API to fetch the user details on every webhook that we receive.

🧠 Additional Context

No response

[github-actions]

✅ Issue processed successfully!

Your issue has been reviewed and assigned to the appropriate team.

[i-am-rad]

This also affects the ability to query userId for agency type users if you have a location scoped token. We should get limited details back on the agency user rather than nothing. Often times its agency users/admins installing and interacting with our apps. The new api for marketplace installs is helpful, but we need to ensure get user id returns back the same user details. We get this back if we try to query a userId with location token: "[400] The user id is invalid. Bad Request"

[garvjeet-highlevel]

Fixed: User Not Found now returns 404 instead of 401

Thanks for reporting. This is fixed. The API now returns 404 (Not Found) for non-existent users instead of 401 (Unauthorized), so you can distinguish authentication errors from missing resources.

New API behavior

Before:

{
  "message": "The user does not exist.",
  "error": "Unauthorized",
  "statusCode": 401
}

After:

{
  "message": "The user does not exist.",
  "error": "Not Found",
  "statusCode": 404
}