Skip to main content

Employee Verification Failed (2850 / 2851)

Symptoms​

When calling the Turing Platform API, you receive an HTTP 403 Forbidden response whose body contains one of the following error codes:

Error CodeMessageMeaning
2850Your employee account has been marked inactive. Please login to Turing Portal (https://login.tcl.com/siam/login) to re-verify your status.The employee account has been marked as inactive
2851Employee status could not be verified. Please login to Turing Portal (https://login.tcl.com/siam/login) to continue using the API.Employee active status could not be confirmed (first use or not verified for an extended period)

Example response:

{
  "error": {
    "code": 2851,
    "message": "Employee status could not be verified. Please login to Turing Portal (https://login.tcl.com/siam/login) to continue using the API.",
    "type": "forbidden"
  }
}

Why Does This Happen?​

The Turing Platform performs an active-employee identity check on API Key holders to ensure that platform resources are used only by current employees. Verification relies on TCL's unified identity source (SIAM) and is triggered in the following scenarios:

  1. First use of an API Key: The platform has not yet retrieved your latest employment status.
  2. No login to Turing Portal for an extended period: The previous verification record has expired and must be renewed.
  3. Employee has left, transferred, or had their account disabled: SIAM has marked the account as inactive (corresponds to 2850).
info

Identity verification is account-level, not API Key-level. All API Keys under the same employee ID are affected.

Resolution​

Case 1: 2851 — Status Cannot Be Confirmed​

  1. Open a browser and go to https://login.tcl.com/siam/login.
  2. Log in to SIAM using your TCL employee ID and password.
  3. After a successful login, visit Turing Portal; the system will automatically refresh your employment status.
  4. Wait approximately 1 minute, then retry the API call.

In most cases, completing the steps above resolves the issue.

Case 2: 2850 — Account Marked as Inactive​

This typically indicates that your account status in SIAM is genuinely abnormal. Possible causes include:

  • Offboarding or transfer procedures have been completed.
  • HR system synchronization delay or data inconsistency.
  • The account has been temporarily disabled.

Follow these steps to investigate:

  1. First, log in to Turing Portal following the steps in Case 1 to rule out a status cache issue.
  2. If 2850 persists, contact HR / IT to confirm whether your active status in SIAM is correct.
  3. If you are confirmed to be active but the status is still incorrect, contact Turing Platform operations for assistance.

Frequently Asked Questions​

Q: I was able to use the API before. Why am I suddenly getting 2851 today?
A: Employment status verification has an expiration period. Once it expires, you must log in to Turing Portal again to refresh your status. This is expected security behavior.

Q: I only want to call the API from a server. Can I skip the browser login?
A: No. Both the initial activation and periodic renewal require completing a SIAM login through a browser to ensure the verification is performed by the actual employee.

Q: We're using a team-shared API Key, and the key owner has left the company. What should we do?
A: Have an active team member apply for a new API Key. Continuing to use a Key belonging to a departed employee is not recommended — once their account is disabled in SIAM, the Key will stop working immediately.

Getting Help​

If the issue persists after following the steps above, contact technical support via Get Help.