Common Errors

[This is a blank topic to use as a starting point for new topics. Use this for “concept” topics.]

Overview

This table describes common errors encountered when interacting with the Trimble Entitlement v3 API.

Error	Details
400	Cannot update an entitlement due to missing/invalid entitlement details or entitlement ID does not exist.
401	Unauthorized - The access token was not included in the API call.
403	Forbidden - The object is not accessible to the client TID Identity performing the request.
404	An object with the specified ID was not found. For new applications/users, you may get this error when trying to view a procedure that was shared with you if you have not successfully completed a call to the Pegasus API. The Pegasus API uses implicit authentication to register the client upon initial connection. To resolve the error, complete a call (e.g., list procedures) and request that the procedure owner update the shared_with value to include your application/user name.
422	Unprocessable Entity - This can be caused by any condition that prevents the request from being processed successfully. Conditions include: incorrect state for the operation and missing parameters. If you are trying to share a procedure with a new application/user, they may have not successfully completed a call to the Pegasus API. The Pegasus API uses implicit authentication to register the client upon initial connection. To resolve the issue, request that they complete a call (e.g., list procedures) and try again.
5xx	The server failed to fulfill a request. This is a system-level issue. It may be intermittent and resolved after a retry. If the issue persists, contact support@trimbledata.com.