Endpoints¶
Configuration¶
API URL : https://api.neomia.ai/pulse
API Key
To use this API, please send your neomia Pulse API key in the headers for each request.
1 | |
<APIKEY> with your own api key.
For further details, please consult our documentation Swagger here.
User Reference
The parameter indicated userRef represents your custom user ID. We recommend using a name respecting email format conventions.
Request : Status¶
GET /status
This endpoint allows to know if Pulse API is up to receive request.
Response : OK¶
1 2 3 4 5 6 7 | |
Response : NOK¶
1 2 3 4 5 6 7 | |
Request : User Verify¶
POST /user-verify/{userRef}
This is the main API endpoint that allows to check the pattern of a user.
- If a tId is provided, the pattern will be compared to a reference pattern having the same tId.
- If a tId is not provided, the pattern will be compared to the existing associated patterns.
- If the user does not exists in the database, the API return a
404when the headers does not containx-enrollment : USERproperty.
User Enrollment
By default this endpoint does not create a user. If you want allow the user creation please add the following header property :
1 | |
If the user allready exists, this has no effect.
Request Body (Pattern)¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 | |
Response : Enrollment¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | |
Response : Verify¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 | |
Response : User does not exists¶
1 2 3 4 5 6 7 8 9 10 11 | |
Status code : 404
Response : Robot detected¶
If a pattern is generated by a bot (for example, a password manager), Pulse returns a bot detection response.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 | |
Status code : 200
Request : User Action¶
POST /user-action/{userRef}
Allow the client to execute different actions in relation with the specific userRef. The variable type determines the action and can take following values :
LINK_PATTERN: add the sended pattern as reference to user's profile.LINK_PATTERN_ID: add the recorded pattern with the specific pattern identifier to user's profile.UNLINK_PATTERN_ID: remove the recorded pattern with the specific pattern identifier to user's profile.RESET_BIOMETRIC_PROFILE: remove all reference patterns from user's profile. If there is a pattern or a pattern id indataattribute, this pattern will be linked.
Add pattern ID as reference¶
Request body¶
1 2 3 4 | |
Or
1 2 3 4 | |
Successful response¶
1 2 3 4 5 6 7 | |
Add pattern as reference¶
Request body¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 | |
Successful response¶
1 2 3 4 5 6 7 | |
Reset biometric profile¶
Request body¶
1 2 3 | |
Successful response¶
1 2 3 4 5 6 7 | |
Deletes patterns in references.
We recommend using the Pulse Dahboard to perform this operation !
Request : Get Users¶
GET /users/{userRef}
This endpoint get information about a user and his associated patterns.
Response : User Exist¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | |
Status code : 200
Patterns Status
-
If the value of
refPatternsStatus.textVisibleisok, the user is ready to be authenticated with Pulse BiometricPass. -
If the value of
refPatternsStatus.textVisibleisnok, the user must be re-onboarded. We recommend using the procedure indicated here to re-onboard the user (methodcomplete-profile).
Response : User not Exist¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | |
Status code : 404
Request : Delete Users¶
DELETE /users/{userRef}
This endpoint delete a user and his associated patterns.
Successful Response¶
The API response return the number of patterns that has been deleted.
1 2 3 4 5 6 7 | |