Error codes
Pulse
Pulse API
Every Pulse API error uses the envelope {"timestamp", "success": false, "message", "reason"}.
| HTTP status |
reason |
Cause |
Resolution |
| 400 |
invalid-data |
Missing or expired X-Pulse-Session header; missing member_ref on a generic account. |
Call GET /users/{userRef} to bootstrap the session; pass member_ref for shared accounts. |
| 401 |
— |
Missing or unknown API key. |
Check the apikey header. |
| 404 |
user-not-found |
The user does not exist. |
Create it with POST /users/{userRef} and enroll it. |
| 409 |
quota-exceeded |
A license quota is reached (message prefixed by ACCOUNTS_QUOTA_EXCEEDED:, SHARED_ACCOUNTS_QUOTA_EXCEEDED: or SHARED_ACCOUNT_MEMBERS_EXCEEDED:). |
Contact your provider to adjust the license. |
| 409 |
invalid-action |
Account-type change requiring consent or blocked; duplicate member reference. |
See Account Management. |
| 422 |
invalid-data / detection-bot |
Invalid pattern (too short, too long, unsupported recorder version), bot-generated pattern, or weak security code. |
Check the recorder version and the captured pattern; ask the user for a stronger code. |
| 500 |
internal-error |
Internal error. |
Contact support with the request id from the message. |
| 503 |
— |
Service temporarily in degraded mode. |
Retry later; check GET /status. |
Pulse CAS
| Code |
Cause |
Resolution |
100 |
Communication with Pulse API failed. |
Please check if the API is UP and check the plugin version. |
101 |
Pulse plugin cannot found user information in LDAP |
Please verify your pulse plugin configuration. |
102 |
An invalid email has been detected |
Please verify if the personnal user email is correct. |
103 |
Invalid One Time Password |
Fill in the OTP field with the last OTP sent by email. |
104 |
Invalid Pulse Pattern received by CAS server |
Please check if the plugin has correctly setup the frontend. |
106 |
Pulse cannot send the OTP at the personal user email address. |
Please check your mail server configuration and the user mail address. |
107 |
Pulse has detected pattern generated by a robot. |
Please retry with a humman. |
108 |
User not exists in Pulse database. |
Please complete the enrollment process. |
109 |
Pulse has blocked the authentication process (fraud detection). |
Reset the biometrcis profile |
110 |
Pulse has challenged the authentication process. |
Complete the challenge process. |
111 |
Pulse user verify process failed. |
If the problem persists, please contact neomia. |
113 |
The provided OTP has expired. |
Please retry with the new OTP sent by email. |
Agent C#
| Code |
Cause |
Resolution |
201 |
Communication between API and agent failed. |
Please check if the API is UP and check the library version. |
202 |
Invalid API Key. |
Please check your Pulse API key. |
203 |
Invalid pattern format, Pulse cannot use provided pattern. |
Please check if the pattern is correctly formatted and if it contains enought keyboard events. |
204 |
Pulse API has detected an invalid pattern probably generated by a bot. |
Please use an human. |
205 |
User not exists in Pulse database. |
Add enrollment parameter (true) when you call UserVerify. |
206 |
User verify failed, unintelligible answer. |
Please check if you have the latest version of the agent. |
207 |
Invalid API URL. |
Please check your Pulse API URL. |
208 |
Invalid tag added in a pattern. |
Please check if your tag contains a valid key and value. |
210 |
Invalid user reference. |
User reference must contains simple chars only. |
More support ?
You cannot solve your problem ? Please contact us at : dev@neomia.ai