Retrieve Latest Score Results

Retrieve a paginated list of the most recent score results for the authenticated user.

This endpoint returns score data generated by the user's configured export job from the most recent successful execution. Results include:

• Target information (ID, name, supplier identifiers)
• Perspective details (ID, name)
• Calculated scores and risk levels
• Action priority when enabled for the export account in the database, using the same Supply Chain Analysis matrix logic as GET/POST /v2/analysis/matrix-targets/{targetId}?perspectiveId=...
• Score components and subcomponents (if enabled in configuration)
• Calculation timestamps

Data Source:

• Results are automatically generated based on the user's export configuration and run interval
• This endpoint returns data from the last successful execution only
• Results are paginated for efficient data retrieval
• If no export job has been configured or no results are available, an empty page is returned

Response: Returns a paginated list of score entries. Each entry includes target information (ID, name, supplier identifiers), perspective details, calculated scores, risk levels, action priority when available, and optionally score components/subcomponents if enabled in configuration. See the response schema for complete field definitions.

Pagination:

• Results are paginated for efficient data retrieval
• Use query parameters to control pagination:
  • page: Page number (0-indexed, default: 0)
  • size: Number of items per page (default: 20)
• Results are ordered by calculation timestamp (most recent first)

Important: Target ID Stability

✅ This endpoint always returns correct target IDs

The targetId field in each score entry represents the current, correct Prewave Target ID. If a target merge or consolidation occurred after a score was calculated, the system automatically updates the stored target ID to reflect the current, merged target. You can rely on the targetId values returned by this endpoint as the authoritative source for current target identifiers.

⚠️ However, target IDs may change over time due to target merges or data consolidation. When this happens:

• The target's edge numbers, edge data, and collection memberships are automatically moved to a new target
• This endpoint automatically updates score entries to reference the new targetId after a merge occurs
• To find the current targetId for a supplier independently, use GET /public/v2/suppliers/sites and match by supplier identifiers from the supplierIds field

Target ID Stability:

• Once a supplier has been screened (indicated by screened: true when retrieving supplier details via GET /public/v2/suppliers/sites/find-by-identifier?prewaveId={targetId}), the chance of targetId changing becomes very low
• Target ID changes can still occur for screened suppliers, but this is rare
• Unscreened suppliers (screened: false) have a higher likelihood of ID changes during data consolidation

How This Affects Score Results:

• Score entries are initially associated with the targetId that existed at the time the score was calculated
• If a target merge occurs after score calculation, this endpoint automatically updates the stored targetId to the current, merged target ID
• All score entries returned by this endpoint always reference the current, correct targetId
• The edgeNumbers field in each score entry provides additional stable identifiers (like SAP IDs, Coupa IDs) for mapping to your internal systems

💡 Tip for Integrations:

• Use the edgeNumbers field as a stable identifier for mapping scores to your internal systems (e.g., SAP IDs, Coupa IDs)
• For regular synchronization, use GET /public/v2/suppliers/sites to always have the latest targetId values mapped to your supplier identifiers
• When matching scores to suppliers, prefer matching by supplier identifiers rather than targetId for better reliability
• For screened suppliers (screened: true), the targetId is more stable, but periodic synchronization is still recommended
• For unscreened suppliers, more frequent synchronization is advisable

Note: Fields with null values (riskLevel, actionPriority, groups, components, subComponents) are omitted from the JSON response. This is standard JSON serialization behavior.

Required Permission: ACCESS_ENTERPRISE_EXPORT_API