Portfolio monitoring batch discovery and retrieval enhancements in the Grid v2 REST API

We’ve introduced enhancements to the Grid v2 API to improve how you discover, retrieve, and process Portfolio Monitoring (PM) batches and non-Portfolio Monitoring batches. These updates provide clearer visibility into PM activity and consistent access to batch and alert details. 

Discover Portfolio Monitoring batches

A new batch listing endpoint in the Grid v2 API allows you to easily identify recently submitted batches and review high‑level status and counts.

Using the GET /v2/batch?submissionMethodTypes endpoint, you can now view:

• Batch ID
• Submission date
• Current batch status
• Number of inquiries
• Alert counts

You may retrieve either the most recent batches or batches within a specific date range, depending on your needs. Use responses to see batchId, alertCount, status, and submittedDate for each batch.

Retrieve full batch details

Once a batch is identified, you can retrieve the complete batch structure using the GET /v2/batch/{id} endpoint in the Grid v2 API. This endpoint now fully supports PM batches and returns a consistent JSON structure.

The response includes:

• Batch‑level metadata for status, submission type, and PM indicators.
• The full list of inquiries in the batch.
• Inquiry‑level status and review information.
• Portfolio Monitoring–specific attributes.

This behavior aligns responses for PM and existing non‑PM batches, ensuring a consistent experience across submission types. The response contains the full batch structure, including the gridInquiries array and PM metadata like portfolioMonitoring and submissionMethodType.

Retrieve alert details for PM inquiries

To retrieve inquiries that generated alerts, you can continue using the Grid v2 API alert details endpoint. Use the batch and inquiry IDs from batch details responses in the format alertId={pmBatchId}.{inquiryId} to access full alert details for each affected inquiry.

Implementation notes

For best performance, use these guidelines in the GET /v2/batch?submissionMethodTypes endpoint.

• Use case-sensitive submission method types: PM, Web, WS, System. Use NON_PM if you want Web, WS, and System in one request.
• Use either latest or from/to parameters. Do not send both in the same request.
• When using a date range, send both from and to in ISO 8601 format. Keep date ranges within 180 days.  
• If you receive a 400 message with TOO_MANY_RESULTS, narrow the date range or use latest instead.
• Include pageSize and pageNumber for pagination.

AI Review multi-threshold filtering

AI Review now supports multi‑threshold risk filtering, enabling AI Review-enabled firms to apply different thresholds to different categories of risk. This enhancement allows you to fine-tune screening behavior based on the relative importance of specific event types, rather than relying on a single, uniform threshold.

With this capability, you can classify event codes into High, Intermediate, or Low Risk groups, each with its own configurable threshold for persons and organizations. Firms can now balance filtering sensitivity with operational efficiency by using more conservative thresholds for matches associated with higher‑risk categories and filtering more aggressively on lower‑risk categories.

This enhancement provides:

• Greater alignment with firm‑specific risk appetites.
• Improved control over false positives without increasing missed risk.
• Flexible configuration without impacting existing implementations.

Unassigned event codes continue to follow the existing primary threshold, ensuring full backward compatibility and no change to current behavior unless the feature is explicitly configured. AI Review auditing and governance workflows remain unchanged.

Improved handling of date fields in the Grid v2 REST API

We’ve improved how date values (including date of birth) are returned in the Grid v2 API. Year‑only (1991), year‑and‑month (1991‑03), and full dates (1991‑03‑15) are returned in simpler, more readable formats with no appended time values. This removes the need for workarounds and eliminates confusion caused by defaults like 01-01 or 00:00:00. This behavior applies to Grid v2 API responses for firms that enable the newer notify configuration. A Moody’s team member can help you understand how this enhancement impacts your specific use cases and support you with any integration or configuration updates needed.