How are webhook deliveries authenticated?
Venue Authority signs each webhook with the endpoint secret shown once at creation. The payload includes a stable event ID so consumers can verify the signature and process at-least-once delivery safely.
Merchant monitoring API
Resolve each food-service facility to its regulator record, then use merchant risk monitoring to watch supported source changes and receive signed events.
Risk teams repeatedly decide whether a supported regulator source changed after a merchant passed onboarding.
A periodic place search can miss regulator identifiers, replay the wrong facility, or hide whether a change came from a validated source snapshot.
Venue Authority provides account-scoped watchlists, stable event IDs, signed webhooks, delivery history, retries, and source evidence for supported changes.
The response gives you the canonical facility identifier needed to enroll one supported record in monitoring.
curl -X POST https://venueauthority.com/api/v1/resolve \
-H 'Authorization: Bearer YOUR_ONE_TIME_KEY' \
-H 'X-Request-Id: onboarding-000001' \
-H 'Content-Type: application/json' \
--data '{"name":"REDACTED MERCHANT","address":"REDACTED STREET ADDRESS"}'{
"disposition": "accepted",
"reason": "The name and address clear the corpus resolution policy.",
"record": {
"jurisdiction": "nyc",
"sourceId": "REDACTED",
"name": "REGULATOR-REPORTED NAME",
"sourceUrl": "https://data.cityofnewyork.us/..."
},
"snapshot": {"manifestSha256":"...","schemaVersion":"runtime-corpus/v1"},
"requestId": "onboarding-000001"
}Venue Authority signs each webhook with the endpoint secret shown once at creation. The payload includes a stable event ID so consumers can verify the signature and process at-least-once delivery safely.
A failed source refresh does not promote partial data. Venue Authority keeps the last validated snapshot serving and reports the bounded failure class and freshness state.
No. Public evidence pages use materialized artifacts tied to retained source provenance. Page views and crawlers do not trigger live regulator history or rights requests.
Portfolio Proof uses the same resolver policy and returns bounded aggregate evidence without storing the uploaded CSV.
Run Portfolio Proof