Summary

The API request was not authenticated. 

Possible Causes and Suggested Actions

If you are seeing this error, user your API Key to invoke the following API:

  GET /api/v3/info/{acc}/access

where {acc} is your account number. If this request returns HTTP status 200, then your API Key is OK. If this request reurns status 401 then your API Key is INVALID.

Here are several possible causes for a request that returns status 401 and error code 3401001:

  • You did not specify a HTTP x-api-key header containing an API Key. 

  • Your request specified an invalid API Key as the value of the x-api-key header. In the Integration Center of the TeamworkIQ application, generate a new API Key. Copy it and deploy your client with this key.

  • Your API Key has been revoked. A new one may or may not have been generated. In the Integration Center of the TeamworkIQ application, generate a new API Key. Copy it and deploy your client with this key.

  • The App for which your API Key was granted has been deleted. Create a new one and generate a new API Key.

  •  Your account has subscribed to a downgraded plan that does not support API access. Contact the owner of your account and request that the account be upgraded to a plan that supports the developer API.

  • Your account is locked, perhaps due to non-payment. Verify that your account is not locked by logging into the TeamworkIQ web application.  

Did this answer your question?