Public API Changelog
This document contains the changelog and release notes for the Prewave Public API.
π January 2026 β Public API Updates
π Table of Contents
We're excited to announce significant improvements to the Prewave Public API. This release introduces a new Supplier Management v2 API that dramatically simplifies supplier onboarding and identifier management, alongside improved documentation across all endpoints.
What's in this release:
β¨ New Supplier Management v2 β Simplified supplier creation replacing the complex Sites-Upsert API
π Supplier Identifier Management β Link suppliers to your external systems (SAP, Coupa, D&B, etc.) using multiple identifier types
β οΈ Deprecations β Legacy v1 endpoints sunset scheduled for December 2026
β¨ What's New
π¦ Supplier Management API v2
The problem we solved: The legacy Sites-Upsert API (/public/v1/sites-upsert) required complex batch operations with FULL/DELTA load semantics, large nested payloads, and asynchronous request tracking. Many customers found it difficult to integrate and debug.
The new approach: The Supplier Management v2 API (/public/v2/suppliers/sites) replaces this complexity with simple, RESTful operations. Create suppliers with immediate feedback and track their processing status easily.
π― Key Benefits
Benefit | Description |
Simpler integration | Standard REST patternsβjust POST to create, GET to read, DELETE to remove |
Immediate feedback | Synchronous responses with clear HTTP status codes and validation errors |
Smaller payloads | 60-80% smaller response payloads with only essential fields |
Flexible identification | Find or deactivate suppliers using your own system IDs or Prewave IDs |
Better error handling | Errors returned immediately with actionable messages, not buried in async reports |
π Before & After Comparison
Before (Sites-Upsert v1): Complex batch with nested arrays, async processing, status polling
# Step 1: Submit a batch request with all suppliers curl -X POST "https://api.prewave.ai/public/v1/sites-upsert/full" \ -H "X-Auth-Token: YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "siteData": [ { "yourReference": { "id": "SUP-001", "source": "SAP" }, "name": "Acme Corp", "countryCode": "AT", "locality": "Vienna", "addressLine": "123 Main St" } ], "dryRun": false }' # Response: { "requestId": "550e8400-e29b-41d4-a716-446655440000" } # Step 2: Poll for status curl "https://api.prewave.ai/public/v1/sites-upsert/full/550e8400-e29b-41d4-a716-446655440000" \ -H "X-Auth-Token: YOUR_API_TOKEN"After (Supplier Management v2): Simple POST, immediate response with tracking
# Create a supplier β one call, immediate result curl -i -X POST "https://api.prewave.ai/public/v2/suppliers/sites" \ -H "X-Auth-Token: YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "name": "Acme Corp", "countryCode": "AT", "locality": "Vienna", "addressLine": "123 Main St", "supplierId": { "id": "SUP-001", "source": "SAP" } }'Response:
HTTP/1.1 202 Accepted Location: /public/v2/suppliers/sites/pending?uuid=550e8400-e29b-41d4-a716-446655440000 Content-Type: application/json { "uuid": "550e8400-e29b-41d4-a716-446655440000", "status": "PENDING", "pendingEndpoint": "GET /public/v2/suppliers/sites/pending" }π Note the Location header β It points to /public/v2/suppliers/sites/pending where you can track the creation status of your supplier.
β³ Tracking Supplier Creation Status
When you create a supplier, it enters a pending state while Prewave processes the request (matching, enrichment, screening).
Key points:
β±οΈ Processing time: Typically takes a few hours.
π While pending: The supplier appears in
GET /public/v2/suppliers/sites/pending. Use theuuidquery parameter to track a specific request:GET /public/v2/suppliers/sites/pending?uuid={UUID}.β Once created: The supplier is removed from
/pendingand appears inGET /public/v2/suppliers/sites.
Example: Check creation status
curl "https://api.prewave.ai/public/v2/suppliers/sites/pending?uuid=550e8400-e29b-41d4-a716-446655440000" \ -H "X-Auth-Token: YOUR_API_TOKEN"
π Supplier Identifier Management
What are Identifiers? Identifiers are external keys that link Prewave suppliers to records in your other systemsβSAP vendor numbers, Coupa customer IDs, D&B DUNS numbers, etc.
π Available v2 Endpoints
Method | Endpoint | Description |
|
| π List all suppliers with pagination |
|
| β Create a new supplier |
|
| ποΈ Deactivate a supplier by identifier (query params) |
|
| β Create a new identifier for a supplier |
|
| ποΈ Delete an identifier for a supplier |
|
| β³ Get pending suppliers (use |
|
| π Find suppliers by any identifier (ID or system ID) |
π‘ Common Use Cases
Find a supplier using your internal ID:
# "I have SAP vendor VENDOR-12345, what's the Prewave supplier?" curl "https://api.prewave.ai/public/v2/suppliers/sites/find-by-identifier?supplierId=VENDOR-12345&source=SAP" \ -H "X-Auth-Token: YOUR_API_TOKEN"
Add an additional identifier to an existing supplier:
curl -X POST "https://api.prewave.ai/public/v2/suppliers/sites/identifiers?prewaveId=102006215" \ -H "X-Auth-Token: YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "type": "SUPPLIER_ID", "id": "SUP-12345", "source": "SAP" }'Delete an identifier for a supplier:
curl -X DELETE "https://api.prewave.ai/public/v2/suppliers/sites/identifiers?prewaveId=102006215" \ -H "X-Auth-Token: YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "type": "SUPPLIER_ID", "id": "SUP-12345", "source": "SAP" }'Deactivate a supplier by your external ID:
curl -X DELETE "https://api.prewave.ai/public/v2/suppliers/sites?supplierId=VENDOR-12345&source=SAP" \ -H "X-Auth-Token: YOUR_API_TOKEN"
β οΈ Deprecations
ποΈ Migration deadline: December 31, 2026
The following endpoints are deprecated and will be removed at the end of December 2026. We strongly recommend migrating to v2 as soon as possible.
π‘ Sunset Header
All deprecated endpoints include a Sunset HTTP header (RFC 8594) indicating when the endpoint will be removed.
π Migration Guide
Suppliers β Management
Deprecated Endpoint | β‘οΈ Replacement | Notes |
|
| Paginated list of suppliers |
|
| Resolve identifier to details |
Suppliers β Sites Upsert
Deprecated Endpoint | β‘οΈ Replacement | Notes |
|
| Create suppliers individually |
|
| Create suppliers individually |
|
| Simplified pending tracking |
|
| β |
|
| List all active sites |
ποΈ Removed Endpoints
The following endpoints have been permanently removed:
Endpoint | Reason | Alternative |
| Legacy authentication | Use API tokens (see Authentication Guide) |
| Legacy target connection | Use Supplier Management v2 POST |
| Legacy target disconnection | Use Supplier Management v2 DELETE |
| Legacy batch system | Use |
| Legacy batch system | Use |
| Migration to collections | Use |
π Improved Documentation
We've reorganized the API documentation to make endpoints easier to find:
Category | What's included |
π Collections | Management, Network, Targets, Tier-N β Organize suppliers into collections |
π EUDR | Customers, Suppliers, Shared β EU Deforestation Regulation compliance |
π Suppliers | Sites (v2), Sites Upsert (β οΈ) |
π Scores | Enterprise Export, Target (β οΈ) β Risk scores and assessments |
π§ Other | Alerts, Exposure, Infotags, Roles Management |
π¬ Questions?
For questions or support with these changes:
π§ Email: [email protected]
π€ Your CSM: Reach out to your Customer Success Manager
π Help Center: help.prewave.com
