Support Hub/Troubleshooting/Callback URL Not Receiving Data: A Checklist
Fix

Callback URL Not Receiving Data: A Checklist

If punches do not arrive at your callback URL, go through these checks in order.

  1. Does the device reach Cams? Open the Device Status page. If the device is offline, see Why a device shows offline.
  2. Is the URL right? Check the callback URL saved in your API Monitor account.
  3. Does your server answer correctly? Always reply with {"status":"done"} and HTTP status 200, even if your own processing fails. Do the heavy work later, in a queue, so Cams is never kept waiting.
  4. Is the endpoint reachable from the internet? Use port 80 (HTTP) or 443 (HTTPS) for production. Port 8123 is for testing only. Allow these ports through your firewall.
  5. Is HTTPS set up properly? HTTPS with a valid SSL certificate on port 443 is supported and recommended. Make sure the certificate renews without a server restart.
  6. Do you read the body as raw JSON? Requests are raw JSON in UTF-8, not form fields.
  7. Is the AuthToken check correct? Each callback carries an AuthToken. Compare it with the token set in the API Monitor and reject a mismatch. Make sure you are not rejecting good requests by comparing with the wrong token.
  8. Is encryption switched on? If a Security Key is set in the API Monitor, the payloads are encrypted. Your server must decrypt them with the same key. If you did not mean to use encryption, remove the key.
  9. Did delivery pause? If your server answered with an unexpected response, delivery is tried up to three times and then paused, with a new try every three hours. Fix the server and restart the queue from the Device Status page. See Punches not transmitting or queuing up.

Test it

Events that could not be delivered are kept and sent once your server is back. See Punches made while a device was offline.

Still stuck? Email support@camsbiometrics.com with the device serial number and a short description of the problem.

Was this article helpful?