Screening API
A screening API for sanctions and denied-party lists.
Screen names against sanctions and denied-party lists from your own systems, check OFAC 50% ownership in the records SecurePoint holds, and keep an audit-ready record of each screening. SecurePoint activates API access for each organization.
Screening Core from $299/mo, with add-ons for OFAC 50% ownership (+$399/mo) and evidence and adjudication (+$299/mo).
- Activated for each organization
- SecurePoint turns on API access and issues your spusa_ API key. There is no self-serve sign-up.
- A standalone product
- No SecurePoint Visitor, Education, Trade or Regulated Access plan is required.
- Ownership recorded, not decided
- OFAC 50% ownership results are recorded without changing the screening decision by default.
Three packages, priced per month.
Screening Core is the base package. OFAC 50% ownership and evidence and adjudication are add-ons to it.
Screening Core
Checks against sanctions and denied-party lists with fuzzy name matching.
From $299/mo
Includes
- OFAC SDN/SSI, BIS, UK, UN, EU, FBI, INTERPOL
- Fuzzy name matching and risk scoring, with an AI-written summary by default
- ITAR/EAR relevance flags on every result
- Embargoed country detection
- 10-year audit log retention. ID image retention is configurable by policy and plan.
OFAC 50% / Ownership Intelligence
Multi-hop ownership traversal for the OFAC 50% Rule over the ownership records SecurePoint holds.
+$399/mo add-on
Includes
- Up to 10-hop ownership graph traversal
- OFAC 50% aggregate ownership through blocked owners
- Sanctioned owners and ownership paths returned for review
- Opaque jurisdiction red flags (BVI, Cayman, Panama...)
- Minority-stake sensitive-sector warnings
Evidence & Adjudication
Documented disposition decisions and screening evidence your team keeps for reviews.
+$299/mo add-on
Includes
- Adjudication queue and disposition endpoints (CLEARED / ESCALATED / DENIED)
- Actor attribution on every recorded decision
- Screening evidence PDF export
- Append-only, hash-chained audit log retained for 10 years
Calls past a plan's monthly volume are refused with HTTP 429 until usage resets the next month. By default an AI provider named on the Subprocessors page also writes a summary of each screened name for the reviewer.
One call, one stored result.
POST a name to /api/v1/prescreen with your spusa_ key. The response carries a screening ID, and a GET by that ID returns the stored result later.
Integration example
Your key identifies your organization, so a call never names one. When a possible match needs review, the name goes to your compliance team's review queue and the status reads pending.
curl -X POST https://app.securepointusa.com/api/v1/prescreen \
-H "Authorization: Bearer $SPUSA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"subject": "Acme International LLC",
"country": "RU",
"enable_ai": true
}'Response
{
"success": true,
"data": {
"screening_id": "a1b2c3d4-...",
"risk_level": "CAUTION",
"risk_score": 62,
"adjudication_status": "pending",
"adjudication_required": true,
"matches": 2,
"itar_relevant": false,
"ear_relevant": true,
"ownership_check": {
"mode": "shadow",
"total_ownership_pct": 35.5,
"should_block": false,
"sanctioned_owners": ["SANCTIONED PARENT CORP"]
}
}
}Screen a name, step by step.
Once SecurePoint turns on the Screening API for your organization and issues your key: POST the name, read the screening ID, risk level and score, possible matches and whether review is required, then GET the stored result by that ID.
Read the transcript
Step 1. SecurePoint turns on the Screening API for your organization and issues your API key.
Step 2. POST the name to prescreen as the subject, with your key in the Authorization header. The key identifies your organization, so you don't send one.
Step 3. Read the result: a screening ID, a risk level and score, the number of possible matches, and whether review is required.
When review is required, the name goes to your compliance team's review queue, and the status reads pending.
Step 4. Keep the screening ID. Later, GET the screening by that ID to read the stored result.
Screen visitors at check-in. Keep the decisions on record.
The lists it screens against.
Each list refreshes on its own schedule, daily for OFAC's SDN list. SAM Exclusions, LEIE, and DDTC Debarments are off by default and are turned on per organization.
- OFAC SDN
- OFAC SSI
- BIS Entity List
- BIS MEU
- BIS Denied Persons
- UK Sanctions List
- UN Security Council
- EU FSF
- FBI Most Wanted
- INTERPOL Red Notices
- OpenSanctions
- SAM Exclusions
- LEIE
- DDTC Debarments
- UFLPA
How OFAC 50% ownership is counted.
Under OFAC's 50% Rule, an entity owned 50% or more by blocked persons is blocked even when no list names it. The ownership add-on walks the ownership records SecurePoint holds, up to 10 hops, to find those entities; coverage is limited to the entities those records include.
- 1
Sanctioned Parent Corp is on the SDN list.
It is a blocked person, and so is any entity it owns 50% or more of.
- 2
It owns 80% of Holding Company A.
So Holding Company A is blocked too. It is registered in the Cayman Islands, which the API flags as an opaque jurisdiction.
- 3
Holding Company A owns 65% of Target Subsidiary LLC.
Holding Company A is itself blocked, so its full 65% stake counts and the target is blocked. That is not because 80% × 65% = 52%, but because OFAC FAQ 401 counts the intermediary's entire stake.
By default the ownership result is recorded with the screening and does not change its decision.
Related pages
Talk to us about API access.
No visitor management system required. SecurePoint sets up access and your API key for each organization.
Frequently asked questions
- What is the SecurePoint Screening API?
- A programmatic REST API that screens entity names against global sanctions and denied-party lists, runs ownership traversal for the OFAC 50% Rule (recorded without changing the decision by default), and provides audit-ready adjudication workflows. SecurePoint activates API-key access for each organization, with rate limiting and usage tracking.
- How does 50% ownership traversal work?
- The API walks corporate ownership relationships from the OpenSanctions and Wikidata ownership records SecurePoint holds (up to 10 hops; coverage is limited to the entities those records include). For OFAC, it attributes ownership through blocked intermediaries on a threshold basis under FAQ 401, not by multiplying hop percentages. Entities 50% or more owned by blocked persons are flagged for review. OFAC's 50% Rule is in force today. The BIS Affiliates Rule is suspended through January 10, 2027 and is scheduled to take effect January 11, 2027 absent further BIS action (BIS final rule, FR 2025-19846, extended by FR 2026-22793, staying the interim final rule at 90 FR 47201). While the stay holds it is not operative under the EAR. SecurePoint screens names against the BIS Entity List, MEU List and Denied Persons List on every date. A strong possible match is blocked pending review, and a weaker one can be held for documented human review. A reviewer then confirms or rules out the match, and a denial is a separate recorded compliance decision. It does not yet calculate Affiliates Rule ownership, and it does not start blocking automatically when a scheduled date arrives.
- Do I need a visitor management system to use the Screening API?
- No. The Screening API is a standalone product. It does not require SecurePoint Visitor, Education, Trade, or Regulated Access. It is designed for developers, compliance teams, and SaaS integrators who need programmatic sanctions screening.