APZWatch

API

Authenticate with Bearer keys (azw_live_… / azw_test_…). Optional Idempotency-Key header on screen calls (8–255 chars; same key + same body replays the original result; different body → 409). Base path /api/v1. Machine-readable contract: /openapi.json.

Endpoints

curl -s https://apzwatch.apzportal.apzor.com/api/v1/screens/person \
  -H "Authorization: Bearer azw_live_…" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: person-kyc-001" \
  -d '{
    "fullName": "Jane Example",
    "givenName": "Jane",
    "familyName": "Example",
    "dateOfBirth": "1980-01-15",
    "nationality": "ZA",
    "countryOfResidence": "ZA",
    "email": "jane@example.com",
    "passportNumber": "A12345678",
    "nationalId": "8001015009087"
  }'

# Every screen response includes auditable listVersions
# (listName, listCode, effectiveDate, publishedAt, fetchedAt,
#  recordCount, contentHash, sourceUrl).
# Live hit categories today: sanctions | terror | wallet_designation
# Hits include matchBand (strong|likely|possible|unlikely), matchReasons, entityProfileId.
# Exact name alone is never strong — needs DOB/country/ID/wallet corroboration.
# (durable adverse_media / compromised corpora still expanding)