Support
Where to look when an integration is not behaving, and where the operational guidance lives.
This page is an index. Every link below goes to documentation that already exists in this repository.
Something is failing
Start with the symptom.
| Symptom | Page |
|---|---|
| A request is rejected and you want to decode the response | Common errors |
401 or 403 on a call you expect to be authorised |
Authentication troubleshooting |
| An issuer will not activate, or is not accepting issuance | Issuer readiness |
| Issuance starts but no credential arrives | Issuance |
| A presentation is not verifying | Verification |
Understanding errors
The shape of an error response, the status codes the APIs use, and which failures are worth retrying are described in the error model.
- Error model - the response shape and what each field means
- Handle API errors - handling them in code
- Rate limits - what is returned when you exceed them
- Idempotency - making retries safe
Operating safely
Guidance that matters before an integration carries real credentials and real people's data.
Raising an issue
Bugs, documentation problems and questions about the APIs go to the repository issue tracker:
https://github.com/AESMAITS/DiligenceID/issues
Include the x-ms-request-id or X-Correlation-Id from the response when reporting a failed call. Every API
response carries both, and they are how a specific request is located.
Do not include API keys, bearer tokens, or credential claim data in an issue.