Skip to content

CirclesCheck · Recurring customer monitoring

Keep your customer list
connected to the next check.

Choose daily or weekly screening, inspect changed candidates, and keep the last completed check visible alongside work that needs attention.

Estimate your monitoring plan →Read the API contract
Actual CirclesCheck monitoring watchlist with fictional Alex Sample active at daily frequency and awaiting the first scan
Actual app interface with fictional data. This entry is configured at daily frequency and awaits its first scan; no completed monitoring result is shown.

The recurring workflow

A check, a change, a review.

  1. 01Add the customer

    Use the customer’s name, entity type, and available birth date and country. Choose daily or weekly frequency. An API entry can also link to an existing customer UUID in your organization.

  2. 02Check the scan status

    Review the date and outcome of the last successful screening. An active watchlist entry is a configuration state; confirm that a screening actually completed before treating the record as current.

  3. 03Review changed candidates

    A new candidate set or risk classification with returned matches creates a monitoring finding. Repeated unchanged candidate results do not create another finding. Compare the evidence and record your assessment.

  4. 04Keep the evidence

    Each successful scan saves a screening record. Retain the match review and export the report your team needs for follow-up.

See the saved screening evidence →

Choose a frequency your team can review.

Daily and weekly are supported scheduling choices. Review completed timestamps and source freshness when deciding whether a record meets your requirements; frequency alone does not establish current coverage.

Recurring checks require a paid subscription. Free evaluation provides one watchlist entry and its initial scan. Scheduled monitoring uses a live API key or an authenticated dashboard session.

When a scan cannot complete

A failed attempt keeps the previous successful result and date intact, while showing the latest attempt as failed. An exhausted monthly allowance is shown as quota-blocked. Follow up on these states before relying on the record.

Successful recurring scans consume screening allowance. Failed checks release their reservation. Published plans cap included usage; upgrading requires an explicit checkout.

Read error and usage handling →

Plan your monthly workload

Your list and frequency shape the allowance.

Estimate initial screening plus recurring scans. Add new onboarding, CSV checks, and other screening activity separately. The estimate models a workload; it does not promise scan timing or source availability.

Plan your monitoring

A portfolio. A frequency.
A clear monthly allowance.

Estimate the screening work for an existing customer list. Initial screening and recurring scans each count toward your monthly allowance.

Re-screening frequency
500

planned screenings in the first month

Initial screening
100
100 customers × 4 re-screening runs
400

Starter fits this workload.

$79.99/month. 1,000 screenings included. Other live API, manual, and batch screenings use the same allowance.

Evaluate, then review Starter →

Planning example: 4 weekly or 30 daily re-screening runs, plus one initial screen per customer. Actual usage varies with calendar length, added customers, and other checks. Free evaluation covers one watchlist entry and one initial scan; recurring monitoring requires a paid plan. Current availability and price are confirmed in billing before payment.

Connect the watchlist to your app.

This request adds the fictional Alex Sample at weekly frequency. Replace the placeholder with your live key. Adding a record schedules work; it does not return a completed screening.

Keep keys on your server and inspect the response. Use GET /api/v1/monitoring for scan status and GET /api/v1/monitoring/hits for findings.

Read the monitoring API contract →
curl https://api.circlescheck.com/api/v1/monitoring \
  -H 'Authorization: Bearer cc_live_your_api_key' \
  -H 'Content-Type: application/json' \
  -d '{
    "fullName": "Alex Sample",
    "entityType": "individual",
    "dateOfBirth": "1980-01-15",
    "country": "GB",
    "frequency": "weekly"
  }'

Bring your list and review requirements.

Evaluate the initial monitoring workflow, then select a paid allowance for recurring use. If you need help assessing the fit, share your customer count, frequency, sources, and review process.

Evaluate free →Discuss my monitoring workflow

Prepared by CirclesCheck · Updated . Product evaluation guidance; independent regulatory review is not claimed.