Developers

Developer terms

Version 2026-10

Reference translation. This English text is provided for reference only. The Mongolian version of the developer terms is the binding one; if the two differ, the Mongolian version applies. Read the Mongolian version.

Effective date: 2026-10-27. OpenShop.mn is operated by Buildry AI LLC (company register no. 7277609, 18th khoroo, Khan-Uul district, Ulaanbaatar).

1. General

  • These terms apply to developers who register apps on the OpenShop.mn platform (OpenShop) and access shop data through the OpenShop API. Developers also follow the OpenShop.mn terms of service; these terms add to and clarify them.
  • A developer is deemed to have accepted a version of these terms by clicking the accept button in the Developer section of app.openshop.mn. The accepted version and date are recorded.
  • An app means a third-party program that is installed in a shop with that shop's consent and reads or writes data through the OpenShop API.

2. The developer and responsibility

  • A developer who registers apps is an individual with an OpenShop account whose citizen details are verified through DAN, the government identity system. That citizen is responsible for the operation of every app they register.
  • One developer may register at most 5 apps.
  • The developer gives accurate information about the app, such as its name, description, contact email, privacy policy and support page addresses and the country where data is stored, and updates it when it changes.
  • App names and addresses (slugs) must not use brand names such as OpenShop, Wire, QPay, Buildry, Facebook or Google.

3. App review

  • A newly registered app is in draft. When the developer submits it for review and required information is missing, a list of the missing items is shown.
  • OpenShop reviews the app, makes one of the following decisions and tells the developer the reason: install it by link only in named test shops; publish it in the app directory; or return it to draft with an explanation.
  • An approved app is reviewed again before changing its name, logo, developer name or data storage country, before widening its requested permissions or webhook events, and before adding new hosts for redirect, webhook, install, privacy policy or support addresses.
  • OpenShop is under no obligation to approve an app and, in deciding, takes into account the interests of merchants and buyers.

4. Test mode

  • An app that has not passed review can be installed for testing only in shops the developer owns, in at most 3 shops per app. Such installs are marked in the shop console as unreviewed tests.
  • As soon as the developer stops being the owner of that shop, the test install's tokens and webhooks stop at once.

5. Permissions and access

  • An app may request only these permissions: read, write and delete products; read and write orders; read buyer details (customer:read). An app never receives permissions to manage staff, permissions or integrations, or to create payments.
  • The shop owner, or a person with permission to manage integrations, sees and approves each permission the app requests on the install page. The person installing cannot grant the app permissions they do not have. The app does not access data beyond the permissions approved.
  • Widening permissions requires review and the shop's renewed consent; narrowing them does not.
  • Access tokens are valid for 1 hour, and refresh tokens for 90 days of non-use, renewed on every refresh. Reusing an old refresh token revokes every token of that install.
  • The path for bulk-exporting orders is closed to apps.

6. Buyers' personal data

  • An app processes shop data on the merchant's behalf and only for purposes the merchant has approved. The developer follows the laws of Mongolia on personal data.
  • The customer:read permission gives access to the buyer's name, phone, address, registration number and taxpayer number on orders. This information is not used for any purpose other than providing the app's service, is not sold, is not passed to third parties and is not used for the developer's own marketing.
  • Webhook messages contain no personal data. When personal data is needed, the app fetches it through the API within its permissions.
  • The data storage country is declared accurately; it is shown to the shop on the install page.

7. Deleting data

  • When a shop disconnects the app, the app receives an app.uninstalled notice. The developer deletes the data received from that shop within 30 days of disconnection; information the law requires to be kept is excluded.
  • At the request of the merchant or OpenShop, the developer confirms whether that shop's data has been deleted.

8. Security

  • client_secret, webhook secrets and tokens are kept secret and never exposed in code repositories, logs or browsers. If a leak is suspected, they are changed immediately.
  • Redirect and webhook addresses use https. Every incoming webhook's signature and timestamp are checked before it is processed.
  • If data has leaked or unauthorised access has occurred, OpenShop is notified at support@openshop.mn within 72 hours of discovery.

9. Limits and API changes

  • Request limits apply to the API: currently 600 read and 120 write requests per minute for each install, and 6000 requests per minute in total across all installs of one app. Above the limit, a 429 response is returned and the Retry-After header must be followed.
  • Getting around the limits, splitting traffic across several accounts and collecting other shops' data are prohibited.
  • OpenShop may change the API and its limits. OpenShop aims to announce incompatible changes in advance on the developer page and through the API version header. OpenShop does not promise uninterrupted operation of the API.

10. Payments

  • OpenShop neither receives nor holds the money from purchases. An app cannot create or receive payments through the OpenShop API.
  • If the developer charges merchants for the app's service, the two parties agree on it directly; OpenShop is not a party to that agreement.

11. Prohibited conduct

  • Imitating OpenShop, a bank, a payment institution, a government body or any other brand by name, logo or description.
  • Misleading merchants to obtain permissions, or attempting to access permissions or data that were not granted.
  • Spreading harmful code, getting around platform security or creating excessive load.
  • Promoting or helping to sell products or services prohibited by the OpenShop.mn terms of service.

12. Suspension and disconnection

  • OpenShop suspends, with a recorded reason, an app that breaches these terms or puts merchants or buyers at risk. On suspension, every install's tokens and webhooks stop at once.
  • A shop may disconnect an app whenever it wants. On disconnection, the tokens are revoked and pending webhook deliveries are cancelled.
  • A draft app that was never approved and never installed is deleted by the developer.

13. Liability

  • The developer is liable for the app's operation, the data processed through it, and any damage caused to merchants, buyers or OpenShop by breaching these terms.
  • OpenShop is under no obligation to monitor an app's content or service. An app passing review does not mean OpenShop vouches for its quality.

14. Changes to these terms

  • OpenShop may update these terms. A new version is published on this page with its date.
  • Until the developer accepts the new version, they cannot register new apps or submit them for review; installed apps keep working.

15. Disputes and governing law

  • These terms are governed by the laws of Mongolia. The parties aim to settle disputes first by mutual agreement, and if no agreement is reached, the dispute is resolved by the courts of Mongolia.

16. Contact

  • Questions and notices are received at support@openshop.mn.
  • Operator: Buildry AI LLC, company register no. 7277609, 18th khoroo, Khan-Uul district, Ulaanbaatar.

How to build an app

OAuth, scopes, webhooks and limits, on the Developers page.

Developers page