# General Info

**Special Note:**
  - Keeta Open Delivery API is based on **Open Delivery v1.5.0**. For basic understanding, please refer to <a href="https://abrasel-nacional.github.io/docs/" target="_blank">Open Delivery API</a>.
  - For some of the APIs, **Keeta has made some adjustments based on business scenarios**. Therefore, when Software Service integrates with Keeta, please refer to the APIs definitions in this document. 
  </br>**The major changes include:**
    > - Authentication: **The credentials have been changed from the merchant level to the software level, and the token as well.** However, software services cannot access the merchant data without the merchant's authorization first.
    > - Signature: **Keeta requires the Software Service to include a signature in the header of every API request.** This is to enhance security and prevent the risk of data leakage due to token exposure (such as man-in-the-middle attacks).Please refer to the <a href="./Signature-Calculation"> detailed documentation for the specific signing requirements.</a>
    > - Merchant Menu: Keeta supports menu push (software services push via POST /merchantUpdate interface) and pull (Keeta pulls via GET /merchant interface); however, **Keeta currently only supports full menu updates (modular entry updates are not supported at this time)**. For details, please refer to the description of the corresponding Merchant endpoints in this document.
    > - Order: **Keeta supports querying order events of batch merchants in the polling endpoint**, since the credential is in the software level.
    > - Fields: **Keeta has made some adjustments to the fields in each endpoint, including the number of fields, whether the fields are required, etc.** Please refer to the definitions in this document.
    > - Refund Process: When requesting a total/partial refund after order completion, a negotiation will be initiated between the **Customer** and the **Merchant**. This allows the **Merchant** the opportunity to `ACCEPT` or `DENY` the Customer's request. For details, refer to **ORDERS** section. 
    > - User Privacy Data: To protect users' personal privacy, Keeta will return encrypted data in [order details](#operation/orderDetails). In scenarios involving **merchant self-delivery or third-party logistics (3PL)**, this data can be decrypted. If Software Services need to decrypt the data, they must make additional calls to the [data decryption endpoint](#operation/batchDecrypt). For details, please refer to the description in the **Order section** of this document.
  </br>

  - <b>We strongly recommend software services to integrate the menu API for data synchronization</b>, to avoid merchants maintaining menus in multiple places.
  - Keeta provides a self-service authorization feature in its <a href="https://merchant.mykeeta.com/" target="_blank" rel="noopener noreferrer"> merchant management system </a>. Merchants can log in to the system to independently authorize or revoke access for Software Services. Detailed instructions are available in <a href="../merchant-authorization"> the relevant documentation section </a>.

  - In addition, Keeta offers API endpoints that enable Software Services to automate merchant authorization and embed the workflow into their own SaaS software. For implementation details, please refer to <a href="../merchant-self-serve-authorization"> the relevant documentation section </a>.
  - You can 
    <a href="https://s3-fra01-eu.mykeeta.net/open-third-shop-mapping-template/ODA%20Test%20Collection.postman_collection.json.zip" target="_blank" rel="noopener noreferrer"> Download the Postman Collection </a>
    and add signature calculation script to the pre-request section in Postman to simplify integration and testing.

    **Important** :You need to replace the secret value in the Postman script with the one assigned to you by Keeta.
    <p><img src="./images/postman_replace_client_secret.jpg" /></p>

  - For some general instructions, can directly refer to Open Delivery Documents, and relevant links will be attached.