Commerce platform: API Orchestration

About the client
Client is one of the leading Japanese e-commerce and Internet Company based in Japan. They run one of the largest B2B and B2C e-commerce platform which is one of the largest platforms globally in terms of sales.

Business problem
Client was looking to strengthen its market position in Japan by creating a single, global e-commerce platform to accelerate expansion into new geographic markets across various geographical regions. To achieve this, client was looking for a partner who could provide technology solutions, value-addition by providing consulting services, and effective testing with good quality, which would help it to launch a new marketplace in minimum time and with high quality.

The ultimate goal of the client was the following: 

  • Launching a new marketplace and  confirming the requirements in minimum time and with high quality
  • Releasing country specific malls in a short duration including all new features and enhancements

Business solution
Cybage completed the following:

  • Implemented and enhanced the Application Programming Interface (API) architecture by following best practices 
  • Utilized API development expertise with specialization in the e-commerce domain to ensure that high quality delivery was achieved within the timeframe
  • Analyzed and implemented various development tools and methodologies that could enhance quality, shorten the development time, and help the customer to get best and accurate results in least possible time
  • Enhanced project processes and implemented Scrum, which provided high visibility and improved productivity with other benefits of Agile methodology

Business functions
In the B2B and B2C business model, merchants located in different regions can come together to form an online virtual shopping mall. The main profit sources are fixed fees from merchants and fees based on each transaction and other services.

Business impact
The e-commerce platform hosted around more than 20 APIs which enabled merchants and shoppers to interact with each other. Some of these served the following functionalities: 

  • Order management
  • Campaigns and promotions
  • Catalog management
  • Inventory management
  • Cross-border


API Orchestration:
APIs in the e-commerce platform were categorically divided into the following two parts: 

  • REST APIs
  • Open API

The REST APIs provided Representational State Transfer (REST) interfaces for manipulating the concepts used by the overall project. Its function was mainly to provide a global interface for business services. It was primarily used by the marketplace and back-end systems. The Open API was an integrated Web Service API platform for merchants to exchange product, order, inventory, and other information programmatically. The service was not designed specifically only to few marketplaces but was applicable for all the marketplaces. The Marketplace Web services covered the following items to ensure that the data exchange was highly efficient and highly secured:

  • Authentication and authorization
  • Throttling
  • Web Service APIs
  • Documentation
  • Software Development Kit (SDK)
  • Production environment

The Open API was also used for migration to import and export data back and forth between different platforms and to-be migrated platforms (or marketplaces).


API strategy:
Client aimed to integrate both its platforms into one. This was to bridge the gap between internal and external marketplaces by creating a set of interfaces that standardized requests to and from internal and external marketplaces.

Tools and technologies:
Java, REST full Web services, Test Rail, Hibernate, JUnits or SOAP, MySQL, SVN, Git, Ruby, and BDD.