Comviva

Introduction/overview

Architecture and considerations

Authentication and authorization

Context, cache and signatures

Overview of available APIs

Tracing and debugging

Development assets

High level stages of customer sales (/support) journey

Customer identification

Location serviceability

Product display

Product qualification

Product selection

Promotion qualification

Order characteristics capture

Order validation and submission

Getting Started

Commerce Journey

Production

Sandbox

<p class="slate-p" placeholder="Type / for widgets">BlueMarble is a headless platform that provides APIs that can be consumed in channel front-ends to provide sales and sales support journeys to agents and customers. I<span style="color:rgb(0, 0, 0)" class="slate-color">t supports sales use cases for telecommunications and utility operators </span>in both assisted and unassisted sales channels. </p><p class="slate-p" placeholder="Type / for widgets">The available APIs provide functionality for various domains. They are available as a RESTful API with an OAS 3 schema or as GraphQL APIs. 
The APIs require authentication through a bearer token first which needs to be obtained preceeding any API interaction. Bearer tokens are obtained by authenticating.</p><p class="slate-p" placeholder="Type / for widgets">Most flows are variants of the following archetype; the catalogue APIs expose sellable products and qualification logic to determine which products and promotions can be sold to a customer in a given context. Possibly products related to a customer&apos;s existing assets are used in the transaction to change them in addition to the catalog products. A persistent shopping cart API is provided which stores product selection with pricing and a checkout (order capture) API facilitates capturing the required information to complete an order. A product ordering API for fulfilling an order. All of these APIs can be used for sales and sales support scenarios during the full customer life cycle, starting with acquisition, retention, in-life to move and termination scenarios. These APIs, where applicable, are aligned with and certified against <a href="https://www.tmforum.org/oda/open-apis/table" target="_self">TMForum open API standards</a>.</p><p class="slate-p" placeholder="Type / for widgets"></p><div  data-type="info" style="background-color:#eef1ff;color:#4a59af"><div ><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p" placeholder="Type / for widgets"><span style="color:rgb(0, 0, 0)" class="slate-color">Note: the examples in our developer portal assume your environment has our demo reference data loaded. </span></p></div></div><p class="slate-p" placeholder="Type / for widgets"></p>

BlueMarble is a headless platform that provides APIs that can be consumed in channel front-ends to provide sales and sales support journeys to agents and customers. I

t supports sales use cases for telecommunications and utility operators 

in both assisted and unassisted sales channels. 

The available APIs provide functionality for various domains. They are available as a RESTful API with an OAS 3 schema or as GraphQL APIs. 
The APIs require authentication through a bearer token first which needs to be obtained preceeding any API interaction. Bearer tokens are obtained by authenticating.

Most flows are variants of the following archetype; the catalogue APIs expose sellable products and qualification logic to determine which products and promotions can be sold to a customer in a given context. Possibly products related to a customer's existing assets are used in the transaction to change them in addition to the catalog products. A persistent shopping cart API is provided which stores product selection with pricing and a checkout (order capture) API facilitates capturing the required information to complete an order. A product ordering API for fulfilling an order. All of these APIs can be used for sales and sales support scenarios during the full customer life cycle, starting with acquisition, retention, in-life to move and termination scenarios. These APIs, where applicable, are aligned with and certified against 

<p class="slate-p" placeholder="Type / for widgets">BlueMarble Commerce APIs are designed to be consumed from front-ends leveraging a mix of RESTful, RPC, and GraphQL style APIs. Bluemarble Catalog, Order Management, and Billing services are designed to be reliable, scalable, and flexible system-to-system integrations leveraging the robustness of RESTful APIs. </p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets">While the BlueMarble Commerce APIs can be consumed directly from a browser, using for example a Single Page Application or Progressive Web App style client, we recommend developing at least a Backend For a Frontend (BFF) layer between your browser-based code and BlueMarble to perform token termination. As BlueMarble leverages the OAuth2  and OIDC standards, it&apos;s recommended to use a confidential client and terminate bearer tokens. </p><p class="slate-p" placeholder="Type / for widgets"></p><div  data-type="warning" style="background-color:#FFF8E1;color:#f0b800"><div ><svg width="18" height="16" viewBox="0 0 18 16" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M0.916637 15.5009C0.791637 15.5009 0.683998 15.4732 0.59372 15.4176C0.503443 15.362 0.430526 15.2857 0.37497 15.1884C0.319415 15.0912 0.288165 14.9905 0.28122 14.8864C0.274276 14.7822 0.305526 14.6745 0.37497 14.5634L8.4583 0.605103C8.52775 0.493991 8.60761 0.41413 8.69789 0.365519C8.78816 0.316908 8.88886 0.292603 8.99997 0.292603C9.11108 0.292603 9.21178 0.316908 9.30205 0.365519C9.39233 0.41413 9.47219 0.493991 9.54164 0.605103L17.625 14.5634C17.6944 14.6745 17.7257 14.7822 17.7187 14.8864C17.7118 14.9905 17.6805 15.0912 17.625 15.1884C17.5694 15.2857 17.4965 15.362 17.4062 15.4176C17.3159 15.4732 17.2083 15.5009 17.0833 15.5009H0.916637ZM1.99997 14.2509H16L8.99997 2.1676L1.99997 14.2509ZM9.0833 13.0634C9.26386 13.0634 9.41316 13.0044 9.53122 12.8864C9.64928 12.7683 9.7083 12.619 9.7083 12.4384C9.7083 12.2579 9.64928 12.1086 9.53122 11.9905C9.41316 11.8725 9.26386 11.8134 9.0833 11.8134C8.90275 11.8134 8.75344 11.8725 8.63539 11.9905C8.51733 12.1086 8.4583 12.2579 8.4583 12.4384C8.4583 12.619 8.51733 12.7683 8.63539 12.8864C8.75344 13.0044 8.90275 13.0634 9.0833 13.0634ZM9.0833 10.7509C9.26386 10.7509 9.41316 10.6919 9.53122 10.5739C9.64928 10.4558 9.7083 10.3065 9.7083 10.1259V6.70927C9.7083 6.52871 9.64928 6.37941 9.53122 6.26135C9.41316 6.1433 9.26386 6.08427 9.0833 6.08427C8.90275 6.08427 8.75344 6.1433 8.63539 6.26135C8.51733 6.37941 8.4583 6.52871 8.4583 6.70927V10.1259C8.4583 10.3065 8.51733 10.4558 8.63539 10.5739C8.75344 10.6919 8.90275 10.7509 9.0833 10.7509Z" fill="#F1C21B"></path></svg></div><div ><p class="slate-p" placeholder="Type / for widgets"><span style="color:rgb(0, 0, 0)" class="slate-color">If you choose to consume BlueMarble APIs directly from a browser using e.g. a public OAuth / OIDC client, keep in mind to configure the appropriate CORS headers and take </span>appropriate<span style="color:rgb(0, 0, 0)" class="slate-color"> measures against XSS and CSRF.</span></p></div></div><div  data-type="info" style="background-color:#eef1ff;color:#4a59af"><div ><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p" placeholder="Type / for widgets"><span style="color:rgb(0, 0, 0)" class="slate-color">BlueMarble will be part of a larger telecommunications or utility architecture abstracting various underlying systems relevant to the sales and sales support journeys it provides. The scope of this portal is limited to building on top of that platform, not its integration.  </span></p></div></div><p class="slate-p" placeholder="Type / for widgets"></p>

BlueMarble Commerce APIs are designed to be consumed from front-ends leveraging a mix of RESTful, RPC, and GraphQL style APIs. Bluemarble Catalog, Order Management, and Billing services are designed to be reliable, scalable, and flexible system-to-system integrations leveraging the robustness of RESTful APIs. 

While the BlueMarble Commerce APIs can be consumed directly from a browser, using for example a Single Page Application or Progressive Web App style client, we recommend developing at least a Backend For a Frontend (BFF) layer between your browser-based code and BlueMarble to perform token termination. As BlueMarble leverages the OAuth2  and OIDC standards, it's recommended to use a confidential client and terminate bearer tokens. 

To implement secure authentication and authorization mechanisms across all BlueMarble services, we need a simple, efficient, and standardised approach. To keep authorization as straightforward as possible, we use JWT (JSON Web Tokens). With JWT, each service only needs to validate the token included in the request. A single centralized service is responsible for generating tokens via an authentication endpoint. Once the user authenticates, the token is sent to the client, which must include this token in every subsequent request. If the token expires, it is also the client’s responsibility to refresh it.

Calls to any BlueMarble API are executed in the context of a subject. The actor behind the subject must authenticate to obtain a bearer token. This token returned in JWT format, can be validated using a provided JSON Web Token Key Set (JWKS). The bearer token will contain claims about the subject.

Our journey may start with an anonymous actor, such as a customer who has not logged in yet or a prospect without an account or identity. While we may not initially know the subject's exact identity, they may onboard and become a known subject during the journey. Therefore, BlueMarble requires the creation of a bearer token even for anonymous actors.

Obtaining a bearer token can be done in multiple ways. bluemarble relies on an OpenID Connect (OIDC) compliant identity provider. There are various grants in OIDC that can be used to obtain the required bearer token. Some of the prominent ones are described below:

The resource owner password grant type is used when the client does not have a login UI and access to a web browser is not possible.

As shown in the high-level sequence diagram below, a client application directly interacts with the identity provider and, upon successful authentication, obtains the user's access and refresh token. If the access token expires, the client application uses the refresh token to obtain a new access token. This access token is then passed by the client to the BlueMarble APIs as a bearer token. The API validates the access token and provides the requested resource information to the client.

BlueMarble uses Keycloak as a reference IDP and the following details pertain to that. 

The authorization code grant flow involves exchanging an authorization code for a token. This flow is suitable only for confidential applications, such as regular web applications, because it requires secure handling of the application's authentication methods. The BlueMarble UI applications use the authorization code grant flow to authenticate users and obtain relevant tokens.

As shown in the high-level sequence diagram below, a user requests a resource. The client application checks if the user is logged in. If the user is not logged in, the flow begins with an authorization request, which redirects to the IDP/authorization server. Here, the user logs in using their credentials and approves a consent page, if required. After successfully logging in, the IDP sends the authorization code to the specified redirect URI. Using this code, the client application sends a token request to the IDP/authorization server, including the authorization code, client ID, and client secret, to receive an access token, refresh token, and ID token.

The authorization code request flow generally involves invoking the following URL in the IDP

This URL for IDP will redirect you to the login page for IDP. After successful login, IDP will redirect you back to the defined 

Now, with the authorization code received from the previous step, the client application can make a request to IDP, including the code, client ID, and client secret, to obtain the access token, refresh token, and ID token.

Here is the curl command format for getting the access token and ID token:

The access token among other things contains the following entries. Please note there are also custom claims that BlueMarble injects in an access token which are used by the system. These roles and custom claims have to be configured in the IDP/IAM before hand, so that it can be part of the access token for a given user.

The code snippet below shows, at a high level, how the claims are provided in the access token (both standard JWT and custom claims)

The client_id is generated when you configure your OpenId Connect app in the IDP

client_id

The client_secret is generated when you configure your OpenId Connect app in the IDP

client_secret

username

password

grant_type

scope

This content type is used to send a list of name/value pairs to the server.

Content-Type

access_token

expires_in

refresh_expires_in

Refresh token used to get a new access token

refresh_token

Token type "Bearer" indicates any party in possession of the token can use the token

token_type

Token that contains the identity of an authenticated user

id_token

This is the time before which the JWT must not be used

not-before-policy

State of session, a part of the OpenID Connect Session Management specification

session_state

<p class="slate-p" placeholder="Type / for widgets">BlueMarble APIs can be used in either a stateless or stateful manner. The main element of state in BlueMarble is called context. A context can either be explicitly passed, following the &quot;tell, don&apos;t ask&quot; principle, or it can be inferred from a context cache/store. To use the context cache, a header specifying the context ID must be passed as follows:</p><table class="slate-table"><colgroup></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr"><th class="slate-th" colSpan="1" rowspan="1"><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Header</strong></p></th><th class="slate-th" colSpan="1" rowspan="1"><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Description</strong></p></th></tr><tr class="slate-tr"><td class="slate-td" colSpan="1" rowspan="1"><div class="slate-TableCellElement-content"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets"><code class="slate-code">context-id</code></p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td><td class="slate-td" colSpan="1" rowspan="1"><div class="slate-TableCellElement-content"><p class="slate-p" placeholder="Type / for widgets">Context information identifiable for each customer interaction session</p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr></tbody></table><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets">Following the <em class="slate-italic"><strong class="slate-bold">Tell Don&apos;t Ask</strong></em> principle puts the onus of passing the Context to the client application. </p><div style="text-align:left"> <img src="https://theneo-prod-public.s3.us-east-1.amazonaws.com/73f1ae6a-1cc6-494d-8ca1-47524228b1d2.jpg" alt="" style="aspect-ratio:600 / 350" width="600" height="350"/></div><p class="slate-p" placeholder="Type / for widgets">As shown in the diagram above, to fulfill a customer&apos;s request, the client application might invoke one or more services to obtain relevant information, which is then passed on to a different service as context data in that service&apos;s request payload.</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets">In some situations, the context information might grow too large to efficiently handle within the request payload. In such cases, employing a context store/cache becomes necessary.</p><div style="text-align:left"> <img src="https://theneo-prod-public.s3.us-east-1.amazonaws.com/7972a8ac-becc-4456-9423-97b6bfc21877.jpg" alt="" style="aspect-ratio:600 / 350" width="600" height="350"/></div><p class="slate-p" placeholder="Type / for widgets">As shown in the diagram above, to fulfill a customer&apos;s request, the client application might invoke one or more services to obtain relevant information. The client application includes a unique <code class="slate-code">context_id</code> header parameter, which services use to store data in the context store. Any service needing this context data can retrieve it from the context store using the <code class="slate-code">context_id</code>. The data within the context store is assigned a configurable time to live (TTL), meaning it persists for a brief period, such as a user&apos;s session.</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets">Context is often accompanied by an attribute called ProcessContext. Possible enumerations for ProcessContext are configurable in the back office and can be defined by you. They capture the user intent in a use-case. Common examples include &quot;to buy something new&quot; (acquisition), &quot;to stop something&quot; (termination), or &quot;to change something I own&quot; (in-life sales). Once use-case design is done for your project, you must map these use-cases to process contexts. These can then be used to define business rules and flows or process definitions in various parts of bluemarble.</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets">Various APIs in BlueMarble enforce rulesets, while other APIs provide data that serves as context for those rulesets. To ensure data integrity and to prove that rulesets have been executed through mechanisms like qualification, various APIs will require a signature as part of their input. These signatures are provided by relevant data and qualification APIs and must be passed by the client to the receiving API. While unqualified or unverified data is allowed to be used in flows, the relevant qualification and proof of integrity must be provided before handing over the resulting orders to the next system (e.g., bluemarble Order Management).</p>

BlueMarble APIs can be used in either a stateless or stateful manner. The main element of state in BlueMarble is called context. A context can either be explicitly passed, following the "tell, don't ask" principle, or it can be inferred from a context cache/store. To use the context cache, a header specifying the context ID must be passed as follows:

 principle puts the onus of passing the Context to the client application. 

As shown in the diagram above, to fulfill a customer's request, the client application might invoke one or more services to obtain relevant information, which is then passed on to a different service as context data in that service's request payload.

In some situations, the context information might grow too large to efficiently handle within the request payload. In such cases, employing a context store/cache becomes necessary.

As shown in the diagram above, to fulfill a customer's request, the client application might invoke one or more services to obtain relevant information. The client application includes a unique 

 header parameter, which services use to store data in the context store. Any service needing this context data can retrieve it from the context store using the 

. The data within the context store is assigned a configurable time to live (TTL), meaning it persists for a brief period, such as a user's session.

Context is often accompanied by an attribute called ProcessContext. Possible enumerations for ProcessContext are configurable in the back office and can be defined by you. They capture the user intent in a use-case. Common examples include "to buy something new" (acquisition), "to stop something" (termination), or "to change something I own" (in-life sales). Once use-case design is done for your project, you must map these use-cases to process contexts. These can then be used to define business rules and flows or process definitions in various parts of bluemarble.

Various APIs in BlueMarble enforce rulesets, while other APIs provide data that serves as context for those rulesets. To ensure data integrity and to prove that rulesets have been executed through mechanisms like qualification, various APIs will require a signature as part of their input. These signatures are provided by relevant data and qualification APIs and must be passed by the client to the receiving API. While unqualified or unverified data is allowed to be used in flows, the relevant qualification and proof of integrity must be provided before handing over the resulting orders to the next system (e.g., bluemarble Order Management).

Context information identifiable for each customer interaction session

context-id

The following BlueMarble APIs are available to compose flows for customer journeys. This document focuses on APIs used for customer journeys through (digital) unassisted channels and assisted channels. 

GraphQL allows a front-end to query relevant product catalog information. This API is preferred for front-end use over the below Catalogue APIs.

is a core commerce API used as the basis for all sales and sales support journeys. It persists the cart through all channels and allows the journey to be ported over channels. 

The sales support journeys also use a shopping cart at its core. They allow for top-ups, up-/downgrade of subscriptions, resource/service swap scenarios, and terminations via the cart. 
Any mix of journeys can be combined in a single cart.

 is used to qualify products & validate a shopping cart. The main functionalities are:

takes shopping cart and context as input and provide the list of promotions (default and optional) which are eligible to be applied to cart. The core functionalities provided are:

 is used to convert shopping carts into orders for fulfilment. It is also used to track the status of these orders. 

The catalogue export can be used to load the catalogue into systems that allow for offer exploration. Common systems are CMS for e-shop/self-care, kiosk systems, co-browsing tablets or call centre systems. It can also be used to load the catalogue into fulfilment systems like ERP, POS, WHS, or partner systems. Individual catalogue 

provides real-time browsing and filtering capabilities in the customer journey. The core functionalities provided are:

The Category API provides capabilities of managing categories. Products, Resources, and Services can be part of one or more categories. These categories themselves can have a hierarchy. The category API is used for product grouping in sales journeys allowing for (layered) navigation offer exploration. The core functionalities provided are:

The Product Management (PSR) API provides capabilities to manage products, services, and resources. In sales journeys, they can be used to query detail offer composition data. The core functionalities provided are:

 is used to determine which additional data needs to be captured apart from the content in the shopping cart. It also support validation and integration with various support processes. Data to be captured can be customer specific (new account, existing account, linked accounts, completion of missing profile data) process specific (e.g. credit-check, port-in, move) or product specific.

The customer management API is used to create customers, search for customers, change customers and link customer accounts.

The installed base API returns the customer current installed base / product inventory as well as sell journey specific validations on allowed operations on the installed base (e.g. move, retain, change, up/down grade).

are used to recommend offerings quickly based on the history and real-time context of a customer. It is a real-time and personalised recommendation API.

The serviceability API is used to abstract SoR containing the service inventory for a given location. It's used to visualise the services and quality / quantity thereof on a location. The output can also be used as input for product and promotion qualification scenarios.

The address validation API is used to validate or auto-complete address in the sales journeys.

In a customer project, the preferred identity solution would be used to configure users and roles. The user management API is used additionally to integrate to the identity provider and support use cases like anonymous user flows, obtaining access tokens using a refresh token etc. Keycloak as an IDP is used for reference implementation.

<p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">bluemarble provides an end-to-end (E2E) tracing capability accessible via your Kibana UI. Messages logged by the services running inside the Kubernetes cluster are shipped to the EFK stack. To support end-to-end tracing and debugging, bluemarble APIs accept specific HTTP headers, which are detailed below.</p><table class="slate-table"><colgroup><col style="width:14.003819223424571%"/><col style="width:43.41183959261617%"/></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr"><th class="slate-th" colSpan="1" rowspan="1"><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Header</strong></p></th><th class="slate-th" colSpan="1" rowspan="1"><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Description</strong></p></th></tr><tr class="slate-tr"><td class="slate-td" colSpan="1" rowspan="1"><div class="slate-TableCellElement-content"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets"><code class="slate-code">X-Correlation-Id</code></p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td><td class="slate-td" colSpan="1" rowspan="1"><div class="slate-TableCellElement-content"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">Correlation-id to be passed by client / consumer component. Default - <code class="slate-code">crr-unknown </code>if not provided</p><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">These are typically journey identifier where API are orchestrated and stitched together</p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr><tr class="slate-tr"><td class="slate-td" colSpan="1" rowspan="1"><div class="slate-TableCellElement-content"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets"><code class="slate-code">X-Transaction-Id</code></p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td><td class="slate-td" colSpan="1" rowspan="1"><div class="slate-TableCellElement-content"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">Transaction id to be passed by client / consumer component. Default - <code class="slate-code">tx-unknown</code> if not provided</p><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">These are typically steps / transactions performed within the journey orchestration</p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr><tr class="slate-tr"><td class="slate-td" colSpan="1" rowspan="1"><div class="slate-TableCellElement-content"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets"><code class="slate-code">X-Source-Channel</code></p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td><td class="slate-td" colSpan="1" rowspan="1"><div class="slate-TableCellElement-content"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">Name of the source channel that sent the request to be passed by client / consumer component</p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr><tr class="slate-tr"><td class="slate-td"><div class="slate-TableCellElement-content"><p class="slate-p" placeholder="Type / for widgets"><code class="slate-code">X-Tenant-Id</code></p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td><td class="slate-td"><div class="slate-TableCellElement-content"><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">Tenant-id to be passed by client / consumer component or gateway. Default - <code class="slate-code">default-tenant</code> if not provided</p></div><div class="slate-TableCellElement-resizableWrapper" contenteditable="false"><div style="position:relative;user-select:auto;width:100%;height:100%;box-sizing:border-box;flex-shrink:0" ><div><div  style="position:absolute;user-select:none;width:10px;height:calc(100% + 12px);top:-12px;cursor:col-resize;right:-5px;z-index:20"></div></div></div><div class="slate-TableCellElement-handle"></div></div><div class="slate-TableCellElement-selectedCell" contenteditable="false"></div></td></tr></tbody></table><p class="slate-p" placeholder="Type / for widgets"></p><div  data-type="info" style="background-color:#eef1ff;color:#4a59af"><div ><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets">As there can be multiple transactions within an orchestration/journey, associations between correlation-id to transaction-id is <strong class="slate-bold">1:N</strong>.</p></div></div><h2 class="slate-h2">
Log Aggregation Strategy</h2><p class="slate-p" placeholder="Type / for widgets">Log aggregation is the process of collecting, standardizing, and consolidating log data from bluemarble microservices to streamline log analysis. The log aggregator mechanism actively reads the log data from each individual microservice&apos;s log, filters it, and writes the consolidated log data into a central log store.</p><p class="slate-p" placeholder="Type / for widgets"><span style="background-color:rgb(255, 255, 255);color:rgb(23, 43, 77);font-size:16px" class="slate-color"><span style="background-color:rgb(255, 255, 255);color:rgb(23, 43, 77);font-size:16px" class="slate-backgroundColor"></span></span></p><div style="text-align:left"> <img src="https://theneo-prod-public.s3.us-east-1.amazonaws.com/8afd8195-a510-4ffa-b160-e0c26f2c253f.jpg" alt="" style="aspect-ratio:950 / 350" width="950" height="350"/></div><div style="text-align:left"> <img src="blob:https://bmcomviva.atlassian.net/214b698f-0160-4a63-9d07-d7482224dff6#media-blob-url=true&amp;id=89d0bedd-79f3-4e0e-b8e6-827436474acf&amp;collection=contentId-4792681752&amp;contextId=4792681752&amp;width=1418&amp;height=634&amp;alt=" alt=""/></div><h3 class="slate-h3">Logging to stdout and stderr standard output streams</h3><p class="slate-p" placeholder="Type / for widgets">Logs collected from the Kubernetes cluster are generated by containerized applications. The best practice is to write application logs to the standard output (stdout) and standard error (stderr) streams. A Kubernetes node agent then collects these streams and writes them to a local file on the node.</p><p class="slate-p" placeholder="Type / for widgets"></p><h3 class="slate-h3">Fluentd</h3><p class="slate-p" placeholder="Type / for widgets">Fluentd is an open-source, cloud-native, lightweight log data collector that aggregates logs, parses them, and forwards them to Elasticsearch. Alternatives to Fluentd include Fluent Bit and Filebeat. In a customer project, any of these log collectors can be used.</p><p class="slate-p" placeholder="Type / for widgets"></p><h3 class="slate-h3">Elasticsearch &amp; Kibana</h3><p class="slate-p" placeholder="Type / for widgets">Elasticsearch serves as a decentralized, freely available search and analytics engine suitable for diverse data types, such as text, numbers, geospatial, structured, and unstructured data. Various sources, including logs and system metrics, feed raw data into Elasticsearch. Subsequently, this data undergoes parsing, normalization, and enrichment within the Elasticsearch environment. Utilizing Kibana, users can generate visualizations from this enriched data by writing queries.</p><p class="slate-p" placeholder="Type / for widgets"></p><h3 class="slate-h3">Kafka</h3><p class="slate-p" placeholder="Type / for widgets">In some customer projects, a completely different central log store or logging component may be used. To facilitate such deployment scenarios, bluemarble also provides a means to stream the aggregated logs to Kafka, from where they can be delivered to the relevant logging component.</p><p class="slate-p" placeholder="Type / for widgets"></p>

bluemarble provides an end-to-end (E2E) tracing capability accessible via your Kibana UI. Messages logged by the services running inside the Kubernetes cluster are shipped to the EFK stack. To support end-to-end tracing and debugging, bluemarble APIs accept specific HTTP headers, which are detailed below.

Log aggregation is the process of collecting, standardizing, and consolidating log data from bluemarble microservices to streamline log analysis. The log aggregator mechanism actively reads the log data from each individual microservice's log, filters it, and writes the consolidated log data into a central log store.

Logging to stdout and stderr standard output streams

Logs collected from the Kubernetes cluster are generated by containerized applications. The best practice is to write application logs to the standard output (stdout) and standard error (stderr) streams. A Kubernetes node agent then collects these streams and writes them to a local file on the node.

Fluentd is an open-source, cloud-native, lightweight log data collector that aggregates logs, parses them, and forwards them to Elasticsearch. Alternatives to Fluentd include Fluent Bit and Filebeat. In a customer project, any of these log collectors can be used.

Elasticsearch serves as a decentralized, freely available search and analytics engine suitable for diverse data types, such as text, numbers, geospatial, structured, and unstructured data. Various sources, including logs and system metrics, feed raw data into Elasticsearch. Subsequently, this data undergoes parsing, normalization, and enrichment within the Elasticsearch environment. Utilizing Kibana, users can generate visualizations from this enriched data by writing queries.

In some customer projects, a completely different central log store or logging component may be used. To facilitate such deployment scenarios, bluemarble also provides a means to stream the aggregated logs to Kafka, from where they can be delivered to the relevant logging component.

<p class="slate-p" placeholder="Type / for widgets">To accelerate the development of your front-end, there is a set of assets available that can be leveraged on top of the bluemarble APIs to bootstrap your project.</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets">We provide a Software Development Kit (SDK) implemented in TypeScript and available as an NPM package. The SDK will bootstrap your JavaScript-based project. It is well-suited for rapidly developing either a Single Page Application (SPA), Progressive Web Application (PWA), Backend for Frontend (BFF), or Function as a Service (FaaS) functions. The SDK provides strong types and handles some of the plumbing between APIs. </p><p class="slate-p" placeholder="Type / for widgets">As the bluemarble platform provides the flexibility to cater to journeys impacting various channels, actors, and segments, we have provided a set of open-source blueprint projects that implement channel applications for specific segments.</p><p class="slate-p" placeholder="Type / for widgets"></p><div  data-type="info" style="background-color:#eef1ff;color:#4a59af"><div ><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p slate-indent-0" style="margin-left:0px" placeholder="Type / for widgets"><a href="https://developers.bluemarble.comviva.com/clients-and-sdks/sample-code-and-tutorials/" target="_self">Link to Supported Libraries</a></p></div></div><ul class="slate-ul"><li class="slate-li"><div style="position:relative"><strong class="slate-bold">B2X Webshop</strong> catering to D2C - B2C, SOHO, and SME end-user use cases.</div></li><li class="slate-li"><div style="position:relative"><strong class="slate-bold">B2X Assisted Sales</strong> catering to sales agents serving D2C - B2C, SOHO, and SME use cases.</div></li><li class="slate-li"><div style="position:relative"><strong class="slate-bold">B2B Self-care</strong> catering to SME and LE administrators.</div></li></ul><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets">These assets are provided on a best-effort basis to demonstrate and facilitate the understanding of our platform by example.</p><p class="slate-p" placeholder="Type / for widgets"></p>

To accelerate the development of your front-end, there is a set of assets available that can be leveraged on top of the bluemarble APIs to bootstrap your project.

We provide a Software Development Kit (SDK) implemented in TypeScript and available as an NPM package. The SDK will bootstrap your JavaScript-based project. It is well-suited for rapidly developing either a Single Page Application (SPA), Progressive Web Application (PWA), Backend for Frontend (BFF), or Function as a Service (FaaS) functions. The SDK provides strong types and handles some of the plumbing between APIs. 

As the bluemarble platform provides the flexibility to cater to journeys impacting various channels, actors, and segments, we have provided a set of open-source blueprint projects that implement channel applications for specific segments.

These assets are provided on a best-effort basis to demonstrate and facilitate the understanding of our platform by example.

<p class="slate-p" placeholder="Type / for widgets">A generic sales flow consists of various stages that are supported by various bluemarble APIs. bluemarble supplies various APIs which can be used as an abstraction layer towards backend complexity. Backends in the sequences are referred to as System of Record (SoR).</p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"></p>

A generic sales flow consists of various stages that are supported by various bluemarble APIs. bluemarble supplies various APIs which can be used as an abstraction layer towards backend complexity. Backends in the sequences are referred to as System of Record (SoR).

Sections