Skip to content
Venue Authority

Merchant risk monitoring API

Watch supported regulator records for source changes.

Resolve the facility first, add its canonical record to a watchlist, and receive signed change events.

Last reviewed: 2026-08-13

The recurring decision

Risk teams repeatedly decide whether a supported regulator source changed after a merchant passed onboarding.

Why horizontal data falls short

A periodic place search can miss regulator identifiers, replay the wrong facility, or hide whether a change came from a validated source snapshot.

What Venue Authority returns

Venue Authority provides tenant-scoped watchlists, stable event IDs, signed webhooks, delivery history, retries, and source evidence for supported changes.

Production-compatible API shape

The response provides the canonical facility identifier required 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"
}

Questions buyers ask

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.

Last updated: 2026-08-13

What happens after a refresh failure?

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.

Last updated: 2026-08-13

Can a crawler trigger regulator requests?

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.

Last updated: 2026-08-13

Measure your own sample before choosing capacity.

Portfolio Proof uses the same resolver policy and returns bounded aggregate evidence without storing the uploaded CSV.

Run Portfolio Proof