BEES Deliver

BEES Deliver Relays are APIs designed to receive information from external sources (ERP) to create and update all data required for the Deliver APP and the portal.

All information required by BEES Deliver can be sent using the relay. BEES Deliver also uses some information from BEES Customer.

BEES Deliver Relays

There are some relays on Bees Deliver:

• Vehicle

• Driver

• Tour

• Delivery Document

• Delivery Empties

• Delivery Payment

• Delivery Inventory

• Delivery Location

The main entity used is the Tour, composed of trips and visits to the clients (Accounts). The items being delivered are defined on the invoices.

Today only one Trip is supported.

All the relay accept a array of entities (limited do 1000). For a better performance the items should be sent in grouped.

Is also important to note that some updates need to be sent using Tours PATCH request (Tour Life cycle).

BEES Customer Information

The fowling information is needed from BEES Customer:

• Accounts. The POC information, name, location, contact info.

• Invoices Invoices that need to be delivered on a visit.

• Items Items (products) of the invoices

The fields that are required on these relays can be found here.

To access information about microservices authentication flow and requirements, please check the following link Authentication.

BEES Deliver Architecture

BEEs microservices are built in Java Spring boot archetype, the platform uses mongodb to store data and Rabbitmq as the tool to manage messages.

BEEs has data and business microservices. For each entity, the following steps are performed:

• Relay: receives data from the Zone in batches and send it to RabbitMQ.

• Consumer: reads message from RabbitMQ and send to API to be inserted or updated in database.

• API: process data receive (POST/PUT/DELETE) and retrieves data (GET).

  Required attributes in header

In general, all services endpoints require the following attributes in header:

Authorization: it is a basic authorization token

Country: the country code that refers the information to.

RequestTraceId: Unique value traceability of data and the possibility to check errors.