Skip to content
Back to Blog
APIDeveloper guide

Your First CirclesCheck Screening API Request

CirclesCheck|Updated

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

Create an evaluation account

Start with the free evaluation and generate an API key in your dashboard. Keep the key on your server. Creating an account does not begin a paid subscription.

Send the documented payload

The screening request uses fullName and a supported type of individual or business. Use Authorization: Bearer YOUR_API_KEY and the currently documented API base URL.

The public API reference contains the request example, accepted fields, and response shape. Use that maintained reference instead of mixing samples from different versions.

Read the envelope and status

Inspect the returned screening reference and status. Match records are inside result.matches. Check that the expected result structure exists before interpreting the check as completed. An unavailable service or a failed screening is not a clean result.

Route findings to review

Record the screening ID, compare the source evidence, and retain the reviewer decision. Test authentication failures, malformed responses, and retry handling in an evaluation environment before production.

Estimate ongoing usage

Add the scans generated by recurring customer monitoring to your initial onboarding screenings. The pricing page lists current monthly allowances. Paid subscriptions are reviewed and confirmed in checkout.

Ready to evaluate your screening workflow?

Evaluate customer screening and review with your own requirements.

Evaluate free