Attestation recorded
Delivered to every enabled webhook endpoint immediately after an attestation is written. An attestation is created whenever a field tech scans a barcode and the app evaluates the result against the asset’s recorded location. The request body is a JSON object populated from the payload template you configure in Webhook Settings. The canonical template (recommended) produces the schema documented here. Custom templates may produce different shapes — the field definitions below describe the values available for substitution.
Body
The JSON body delivered to your webhook endpoint. All fields are strings. Location is expressed as a human-readable path — Forager has no GPS coordinates.
Always "attestation". Useful for routing if your endpoint receives multiple event types.
"attestation""attestation"
The barcode value of the scanned asset. Matches the asset_tag column in Forager's asset registry and in your CMDB.
"BIO-4721"
The outcome of the attestation evaluation:
match— the tech's current location matched the asset's recorded location.mismatch_confirmed— the tech confirmed the asset is present but in the wrong location. The asset's location record is updated.mismatch_dismissed— the tech dismissed the mismatch prompt without confirming. No location update.new_asset— the scanned barcode was not in Forager's registry. A new asset record was auto-created at the tech's current location.
match, mismatch_confirmed, mismatch_dismissed, new_asset "match"
Full location breadcrumb from the root node to the room where the tech was standing at the time of the scan. Segments are separated by " / ". Forager's location data is building/floor/room — there are no GPS coordinates.
"Memorial Hospital / Floor 3 / Biomedical Storage"
The leaf node of location_path — the room name only. Convenient for systems that store location as a single room field rather than a full path.
"Biomedical Storage"
The display name of the team member who performed the scan.
"Maria Ortega"
ISO 8601 UTC timestamp of when the attestation was written to the database. Format: YYYY-MM-DDTHH:MM:SSZ.
"2026-06-07T14:23:11Z"
Response
Any 2xx status is treated as successful delivery. Forager does not retry on success.