canonical: https://jentic.com/apis/dowjones.com/dowjones

# Dowjones Screening and Monitoring API

The Screening and Monitoring API screens people and organizations against Dow Jones sanctions, watchlist, and adverse-media risk data. It organizes each check into a case, records the associations being screened, and returns the matches found so a compliance analyst can review each hit and record feedback. Bulk association endpoints let you submit many entities in one transaction and poll its status, and a European host is offered alongside the primary one for data-residency needs.

## For AI agents

Screen individuals and organizations against Dow Jones sanctions, watchlist, and adverse-media data, organize screening into cases, and review potential matches with analyst feedback.

## Scope

Does not handle identity document verification, transaction monitoring, or credit scoring. Use for sanctions, watchlist, and adverse-media screening only.

## Capabilities

- Screen a person or organization against Dow Jones risk data by opening a screening case
- Attach the entities under review to a case as associations
- Retrieve the potential matches returned for a case and inspect each hit
- Record analyst feedback on a single match or a batch of matches
- Submit many associations in one bulk transaction and poll the transaction status
- Track screening cases through review and remove cases that are no longer needed

## Use cases

### Agent-Driven Sanctions Screening

An AI compliance assistant can screen a new customer against Dow Jones risk data without a person opening the console. The agent opens a screening case for the entity, reads back the matches, and flags any sanctions or adverse-media hits for a human reviewer, keeping onboarding moving while a person makes the final decision on each hit.

Example prompt: Open a screening case for a new business customer, retrieve the matches, and summarize any sanctions or watchlist hits for human review

### Ongoing Watchlist Monitoring

Compliance teams re-screen existing customers on a schedule to catch newly sanctioned entities. Using stored cases and their associations, a job re-runs screening for each monitored entity and surfaces fresh matches, so a newly added sanctions listing is caught without re-entering customer details, and analysts only look at cases with new hits.

Example prompt: For each monitored case, retrieve new matches and record feedback resolving the hits that clear review

### Bulk Onboarding Screening

When importing a batch of new counterparties, a case is created with all associated entities in a single bulk transaction. The API returns a transaction id to poll, so a large onboarding file is screened in one submission rather than one call per name, and the caller tracks completion before pulling the matches for review.

Example prompt: Submit a bulk-associations case for a list of counterparties and poll the transaction status until screening completes

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/risk-entity-screening-cases` | Open a new screening case |
| GET | `/risk-entity-screening-cases/{case_id}` | Retrieve a case by ID |
| GET | `/risk-entity-screening-cases/{case_id}/matches` | Find matches for a case |
| PATCH | `/risk-entity-screening-cases/{case_id}/matches/{match_id}` | Add feedback to a match |
| POST | `/risk-entity-screening-cases/{case_id}/bulk-associations` | Create a batch of associations for a case |
| GET | `/risk-entity-screening-transactions/{transaction_id}` | Get the status of a transaction |

## Key resources

- **Screening cases** — Open, retrieve, list, and remove the cases that hold each screening request and its results
- **Associations** — The individual persons or organizations attached to a case and screened for risk
- **Matches** — Potential hits returned for a case, with endpoints to record analyst feedback per match or in bulk
- **Transactions** — Bulk association submissions whose processing status can be polled by id

## Why Jentic

- **Setup:** Wiring the Screening and Monitoring API by hand means learning its bearer auth, choosing the primary or European host for data residency, and polling bulk transactions for completion. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls the screening operations.
- **Permission scoping:** Dow Jones puts the case id in the URL path (`/risk-entity-screening-cases/{case_id}`), so a rule can pin your agent to one case and the screening and match-read operations you pick. You decide which operations are in scope, so case deletion and association decorrelation stay out unless you add them.
- **Credential handling:** Your Dow Jones bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'screen a customer against sanctions' or 'get matches for a case', and Jentic returns the matching Dow Jones operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **ComplyAdvantage** — Real-time AML screening and monitoring against sanctions and adverse media.
- **OpenSanctions** — Open dataset of sanctions and politically exposed persons for entity matching.
- **Onfido** — Identity document and biometric verification for customer onboarding.

## FAQ

### What authentication does the Screening and Monitoring API use?

The Screening and Monitoring API authenticates with a bearer token sent in the Authorization header, per its OpenAPI spec. When you call it through Jentic, that token is held by your own self-hosted instance and injected at execution time, so it never lands in the agent's prompt or logs.

### Can I screen an organization and review its matches with the Screening and Monitoring API?

Yes. Open a screening case for the organization, attach it as an association, then read the matches endpoint for that case to see the sanctions, watchlist, and adverse-media hits. You can record feedback on each match individually or update a batch of matches at once.

### What are the rate limits for the Screening and Monitoring API?

The OpenAPI spec for the Screening and Monitoring API does not define rate limits. Check Dow Jones Developer Platform documentation for the current limits before running high-volume screening jobs.

### Is there a Screening and Monitoring API MCP server?

You don't need an MCP server to give your agent the Screening and Monitoring API. Jentic connects it directly from the API Directory: import it, store the bearer token once, and your agent calls the screening operations it needs without another server's tool definitions loaded into its context.

### Can I limit what my agent is allowed to do with the Screening and Monitoring API?

Yes. Write a rule that allows only the case-open and match-read operations for one case id path, so the agent can screen and read results but cannot delete cases or decorrelate associations, and every call it makes is logged. You choose which operations are in scope, so destructive ones are left out unless you add them.

### How do I run a sanctions screening with the Screening and Monitoring API through Jentic?

Search Jentic with an intent like 'screen an entity against sanctions', and it returns the case-open operation with its input schema so the agent submits the entity and reads back the matches. To run it on your own infrastructure, install Jentic One from its GitHub repo.