Prewave API Integrations

Our APIs help Prewave and its customers realise the Seamlessly Integrated Scorecard Value story. Our APIs are a growing area of our business that we see a growing number of customers wanting.

This integration method is customer owned and Prewave supported. Customers require their own middleware set up to enable this method of integration.

Our APIs are bi directional, which means you can push supplier information to us and pull alerting and score data. By pushing supplier data to us through this method you can avoid manual work and by pulling data you can centralise your risk scoring in a method of your choosing. 

All of our APIs are documented here.

 

Here are some of the more common flows we see customers using and the Prewave API they use to do so. 

Object / Flow Name

Prewave API/Endpoint

Operation (Request)

Details

Supplier Read

Sites Upsert API (Full/Delta)

Read (GET)

Get the supplier information from the source system

Supplier Sync

Sites Upsert API (Full/Delta)

Update (POST)

FULL is used for more comprehensive adding of targets, suppliers and collection maintenance

DELTA is used for continuous adding and removing of suppliers.

Source Supplier Information

Sites Upsert API (Full/Delta)

Read / Update

Additional common information needed from customers: categories, spend/purchase, …

Centralisation of Risk Scoring

Targets API

GET

One of the more popular functionalities/scenarios for our customers is writing Prewave Scores to their desired system. There are multiple score related endpoints like the core scores and the score components, depends on user scenario what is needed.

Tier N

Network

 GET

Common Scenario used to get visibility of supply chain and the map of suppliers at different depths

Alerts

Feed or Disruptions

 GET

Common Scenario of getting data on alerts, like in the UI, for specific Targets