Troubleshooting
Start with View Event Logs in the dashboard. It shows each event we sent, the status and your endpoint’s response.
No events arrive
Section titled “No events arrive”- Check that the webhook is active and subscribed to the right events.
- Check that your endpoint accepts
POSTrequests from the public internet over HTTPS. - Check the member’s medical record number. Events are sent only for members whose medical record number is a UUID.
- Only finished results are sent. A test with no result yet does not send an event.
- We don’t send from a fixed list of IP addresses. If your firewall filters by IP, allow the request and rely on the signature instead.
Signature verification fails
Section titled “Signature verification fails”- Use the raw request body. Parsing the JSON and serializing it again changes the bytes.
- Join the ID, timestamp and body with periods, in that order:
id.timestamp.body. - Compare against the Base64 signature, not a hex string.
- Check that you are using the secret for this webhook. Each webhook has its own.
- If you rotated the secret, the old one stopped working right away.
Deliveries fail or time out
Section titled “Deliveries fail or time out”- Return a
2xxstatus.4xxand5xxresponses count as failures. - Use the final URL for your endpoint. A redirect can drop the request body.
- Respond within 30 seconds. Move slow work to a background job.
- Check your server logs for the
X-YAA-Webhook-Idshown in the event log.
The same event arrives twice
Section titled “The same event arrives twice”This is expected. Skip events whose X-YAA-Webhook-Id you have already handled. See Duplicates.
A date is off by one day
Section titled “A date is off by one day”test_date on toxicology events is a calendar day in UTC with the time set to midnight. Read the date part only. See Test dates.
Still stuck
Section titled “Still stuck”Email integrations@youareaccountable.com with the X-YAA-Webhook-Id of an affected event.