Value Proposition

The notification subscription API is a critical piece of the LaaS product: it allows the partner to registre the callback endpoint where they will receive all notifications of changes occurring in the BPLS systems regarding their journey in progress.

A complementary service allows the retrieval of past notifications.

Key Features

The main operation allows the partner to register the callback endpoint where they want to receive the notifications. This endpoint must conform to the provided specification (see the technical documentation for details).

Only one callback endpoint may be registered for a given partner: any new registration will overwrite the previous endpoint registered.

Within the current LaaS journey, status change notifications are sent on the following events (for each phase of the journey):

• QUOTATION
  • In the future, all status changes on the quotation (expired, cancelled, updated...) will eventually be reported
• PROPOSAL
  • Decision reached
  • In the future, all status changes on the proposal will eventually be reported
• PREPARED CONTRACT
  • In the future, all status changes on the prepared contract will eventually be reported (including, expired, cancelled...)
• SIGNATURE (to be detailed)
  • Initiated
  • In error (with details,  on identity check and on signature)
  • Expired
  • In progress (with reports on every change)
  • Complete
• CONTRACT
  • Activated

Prerequisites

The registration of a callback endpoint requires a partner identifier: please contact your BPLS representative to get the value that you should use.

In any case, the BPLS security framework requires a configuration to allow the use of a new endpoint: please contact your BPLS representative whenever you request a change.

Use Cases

The partner must implement and register a callback endpoint to receive critical updates on the customer journey.

The partner may use the notification retrieval service whenever an incident has occurred in their system where they may have lost some past notifications. Please note that, in case of an error response on the partner endpoint or its unavailability, BPLS implements an automatic replay mechanism to ensure all notifications are properly sent and processed.