Nmbrs API Error codes

Nmbrs API error codes

Error 1001: Invalid Authentication
Cause The email adress or the API token is not valid. 
Solution Make sure that the email and the token that you use are right. For more information see API error 1001: Invalid Authentication
Error 1002: Unauthorized Access
Cause You do not have the rights for the debtor, company or the employee employee services. 
Solution Contact the administrator of the environment and review the API template. 
Error 1003: Unauthorized Access Data
Cause You do not have the rights for the debtor or company.
Solution Contact the administrator of the environment and review access rights by tags/filters.  See where do users with an API token have access to?
Error 2001: Invalid Hour component
Cause Hour component number is not right. Hour component is not inserted.
Solution Use valid hour component number. To see the hour components that are in use see method HourModel_GetHourCodes.
Error 2002: Invalid Wage component
Cause Wage component number is not right therefor the wage component is not inserted.
Solution Insert valid wage component number. To see the hour components that are in use see method WageModel_GetWageCodes .
Error 2003: Unauthorized Access
Cause You do not have the rights to the employee that you are using the API method for. 
Solution 1  Make sure you have the right EmployeeID. For more information see How to get EmployeeId?
Error 2004: Unauthorized Access
Cause You do not have the rights to the company that you are using the API method for. 
Solution 1 Make sure you have the right CompanyID. For more information see How to get CompanyId?
Error 2006: Invalid Period
Cause Inserted period is not according company's period type. 
Solution Use the period type according to company settings. For more information see Company Period.
Error 2009: Unauthorized Access
Cause You do not have the rights to the debtor that you are using the API method for. 
Solution Make sure you have the right DebtorId. For more information see How to get DebtorID?
Error 2015: Protected mode: Cannot change in the past
Cause You are changing something in the past or future without unprotected mode on. 
Solution
You need to put the unprotected mode on by filling <UnprotectedMode>boolean</UnprotectedMode> with true.
Error 9999: Unknown

Cause Some input parameters are not in the correct format (integers, dates, strings).
Solution Check all data types and input values  of input parameters.
Make sure input values are in the expected format.
example, date types, enumerations, or integers. See References and enumerations  

External Errors

Volgen

Opmerkingen

Mogelijk gemaakt door Zendesk