Skip to content
Light
English

ApiMp - 02/28/2025

This article presents a list of new features, improvements and corrections available in ApiMp.

News / Improvements:

User GET

  • Situation: the registration of users/sellers needs to be done via Demander Web. However, the TO-FOR of IDs/codes between ERP-Demander was generating a lot of work for the ERPs.
  • Solution: an API was created to list users/sellers with their codes and IDs for the ERP to save and perform the FROM-TO automatically (based on the name).

Creation of ApiMp Configuration

  • Situation: to ensure that the partner/ERP user can control the generation of the token, activation and deactivation of the integration and other information, it is necessary to create a screen to configure the integration.
  • Solution: the ApiMp Configuration screen was created.

Help texts on the ApiMp configuration screen

  • Situation: on the ApiMp configuration screen in Demander Web, there was a lack of information to help the user find other screens with shortcuts and even tips.
  • Solution: information was added at the top of the screen to help with navigation.

Seller discount/additional per order item

  • Situation: some ERPs would like to work with the seller’s discount/addition at the order item level.
  • Solution: the return of the seller’s discount/additional price was implemented at the order item level.

Return from order carrier

  • Situation: some ERPs would like to work with the order carrier on the GET return, to read it in their system.
  • Solution: the carrier ID tag was implemented when returning orders.

Order status POST

  • Situation: some ERPs would like to work with the status of their internal system within Demander, not needing to register manually.
  • Solution: the POST API was implemented to register order statuses automatically. The status update is done in another API.

Order status update POST

  • Situation: some ERPs would like to update the order status according to information from their internal system.
  • Solution: the POST API was implemented to update the order status in Demander, to generate more information for the seller.

Billing POST

  • Situation: some ERPs control order billing, when updating the status in Demander.
  • Solution: An API was created to update the order status and define whether it was invoiced or not.

Fixes:

Customer registered with Demander without code

  • Situation: when a customer is registered with Demander, by default it has code 0, so the ERP can process the code and return it. However, some ERPs do not perform this treatment and need to receive the customer code/ID from ApiMp.
  • Solution: the customer’s code was added to the customer’s return, the same as the customer’s ID in Demander.

Batch customer registrations generating error

  • Situation: when several customers are registered in sequence, a performance error was generated.
  • Solution: Treatment was carried out to no longer generate the error and process the various clients correctly.

Financial title client not updating

  • Situation: when a financial title already inserted in Demander was changed in the ERP, with a new client, this information was not updated in Demander.
  • Solution: an update was made to find the title and then change the client.

Users always coming back with the true “deleted”

  • Situation: in all GET requests from users, the excluded parameter was always returned as true.
  • Solution: the behavior to return according to the ‘active’ field in the seller/user registration has been corrected.

Customer returning with the incorrect type

  • Situation: when requesting GET from customers, some records of the individual type were returning with the fixed type parameter as ‘J’, which was incorrect.
  • Solution: was corrected to return according to what was entered.

Accept zero price- Situation: on Demander, products with a zero price are not listed as sales possibilities in the order. In this way, treatment was carried out in the API to not accept this type of behavior with the price of the product. However, some ERPs would like to reset prices to deactivate products in lists.

  • Solution: A treatment was carried out to accept zero prices and continue with the behavior of not listing them in the order.

Also check out the news on Demander’s other platforms: