Create re-verification schedule
POST/v2/verify/schedule
Creates an automated re-verification schedule for a customer. The system will periodically trigger proximity verifications using the latest location data from passive monitoring, eliminating the need for manual re-verification requests.
Use case: Ongoing due diligence for loan portfolios. Instead of asking customers to re-verify every quarter, the bank creates a schedule that automatically checks if the customer is still at their declared address using background location pings.
Cadence: checks_per_month determines frequency (1-30). Checks are
distributed evenly throughout the month. For example:
checks_per_month: 4→ Check every ~7.5 dayschecks_per_month: 12→ Check every ~2.5 dayschecks_per_month: 30→ Check daily
Webhook notifications: Each verification result is sent to the configured webhook URL with an HMAC-SHA256 signature for security. The webhook payload includes the full proximity verification result.
Idempotency: Only one active schedule per (customer_id, declared_address) combination is allowed. Creating a duplicate returns the existing schedule.
Worker: Background job runs every 15 minutes to process due schedules.
Request
Responses
- 200
- 400
- 401
- 403
- 409
Schedule created successfully
Validation error (invalid checks_per_month, malformed webhook URL)
Missing or invalid API key
Banking Suite (collections tracking, portfolio risk, re-verification scheduling, the audit-log endpoint) is provisioned per institution, not self-serve — an account gets access via an admin-issued grant, not simply by holding an API key. Also returned when the account has an IP allowlist configured and the request's source IP isn't on it.
Active schedule already exists for this customer/address