Public API Changelog - (Preview)
This document provides a preview of the Public API updates planned for June 2026. The core focus of this release is the introduction of External Score Ingestion, allowing organizations to push their own scoring data into the Prewave platform.
📊 External Scores (Planned)
Base path: /public/v1/scores/externals
This upcoming capability allows you to manage external scores for supplier sites using a unified path for both bulk updates and history retrieval.
Method | Path | Planned Functionality |
|
| Bulk Write: Create or update external scores for multiple supplier sites in one request. |
|
| History: Retrieve the external score history for exactly one supplier site via query parameters. |
Export to Sheets
❓ Understanding "Partial Success" (HTTP 200)
When using the bulk POST method, receiving an HTTP 200 status code indicates the request was accepted, but it does not guarantee every score was successfully saved.
You must inspect the response body for:
success: The overall outcome signal.errors[]: An array detailing specific issues, including theentryIndexand areason(e.g.,TARGET_NOT_FOUNDorUNKNOWN_EVENT_TYPE).
📝 Bulk Create / Update Details
The POST request body requires a data array. Each entry must contain a supplier identifier and a scores array including:
eventTypeKey: A stable key representing the event type (values are tenant-specific).scoreValue: An integer ranging from 1–100.comment: An optional string for context (e.g., "Q2 self-assessment").
🔭 Discovering Event Type Keys
Valid eventTypeKey values depend on your specific organization. Prewave is currently developing clearer discovery options within the Public API to help integrators list all allowed keys for their tenant.
🔗 Shared Identifier Rules
Consistent with other v2 endpoints, external score operations rely on standardized identifier fields.
Bulk POST: Reports per-entry errors if a row cannot be uniquely matched to a site.
History GET: The query parameters must resolve to exactly one site, or the API will return a 404 or equivalent error.
💬 Support
These features are currently in preview and the contract may change before general availability.
Email: [email protected]
Knowledge Base: help.prewave.com
CSM: Contact your Customer Success Manager for enablement details