• Encoding of the forward slash “/” character in the API

  Why can't we use the forward slash "/" character in product and client codes in the API? Short answer: The "/" character is reserved to denote hierarchies in the URL so it can be used only for that purpose. Detailed answer: When consulting endpoints in the API web, like for a client: If the client code has any spaces or other symbols, it must be encoded as UTF-8, where a client code such as: MY CLIENTFew readers

• SAP Business One B1 Integration

  Introduction This document uses the word SAP to refer to SAP Business One. Handy offers our clients an integration between SAP and Handy. This integration synchronizes sales at Handy (presales) as sales quotations in SAP. Additionally, it synchronizes clients, products, prices, and warehouse stock from SAP to Handy. This document elaborates on the scope of this integration. If you're interested, please get in touch with us via chat to receive a quote for the service. In some cases,Few readers

• URL to obtain product prices and inventory remotely

  Integrate your pricing structure through Handy's web service.  It is possible to integrate a custom pricing logic connected to your company’s management system (ERP) in real time for the following purposes Instantly calculate each client's price at that moment Verify inventory stock in real time In this integration, each time a product is added to an order, your web service will be queried in real-time to return the correct price and inventory to the user. The request happens very quFew readers

• How to read closed-route data through the API

  You might need to know when a route is closed and which sales were carried out in that route. Here, we'll explain how to do this: Step 1. Get the routes Make a GET request to this endpoint using these parameters: With this request, you'll receive the closed routes within the dates you specify. As an answer, you'll get a JSON with all of the route's information, as well asFew readers

• API data dictionary

  Orders (SalesOrder)Few readers

• URL to see client details in the app

  Handy can integrate your client's personalized information inside the app, feeding from external systems, like from your ERP. Some of our clients use this integration strategy to show things like: Overdue invoices Balances and credits Order history Sold and unsold products This allows you to display a web view (HTML) within the mobile app, which is loaded in real time from a URL you specify. The URL must be a service that you develop and that, by receiving the customer code as a paraFew readers

• Search order by ID

  The order search by ID feature allows you to search using the Handy ID, but it also filters by the external ID, which is used when you have an integration in place. The external ID may represent your order’s ID in the company’s ERP system. This makes it easier to filter orders without having to switch between systems.Few readers