Troubleshooting¶
This section gathers common issues, best practices and frequently asked questions.
Troubleshooting¶
If you are having problems using the API, please check the following list:
- Make sure you include required headers:
x-dasgate-tenant-idandAuthorization: Bearer <token>. - Make sure you are generating and including the JWT token in each request.
- make sure you are sending data as application/json
For 4xx errors make sure you read API definition to understand correct API usage:
- HTTP 400 error is usally caused by a broken rule or an impossible operation like adding an attendee for a non enrolled
user_id. - HTTP 422 error is caused by a bad formatted request: missing attributes, unknown attributes, unsupported values or formats for attributes.
FAQs¶
Where is data stored?¶
Most data is only stored in the Cloud encrypted databases, like selfies, personal data and biometric credentials. Biometric credentials are only distributed to access points and databases at the edge when, for example, attendees are added to an event.