API and Developer Terms
Last updated November 21, 2026
These API and Developer Terms ("Developer Terms") apply when you use the Wafle application programming interface, webhooks, the AI assistant (Model Context Protocol, or "MCP") integration and related documentation (together, the "APIs"). They supplement the Terms of Service between you and Alto Horizonte Warehouse 33, LLC ("Wafle"). If the two conflict about the APIs, these Developer Terms control.
1. License
Subject to these Developer Terms, Wafle grants you a limited, non-exclusive, non-transferable, revocable license to use the APIs and the documentation at /docs to build integrations for your own stores or, with authorization from the merchant, for stores you manage on a merchant's behalf. You may not use the APIs for any other purpose, or to build a service that competes with Wafle.
2. Keys, tokens and security
APIs are accessed with credentials such as API keys and OAuth tokens. Treat them like passwords: keep them secret, do not embed them in public code or client-side applications, do not share them, and rotate them if you believe they were exposed. You are responsible for all activity performed with your credentials. Credentials are limited to the store, permissions and scopes they are issued for, and you may not attempt to access data or functions outside those limits. Tell us promptly if you discover a security vulnerability or a credential compromise.
3. Rate limits and fair use
We may limit the number of requests you can make and may change limits to protect the Services. Do not circumvent limits, use multiple keys to evade them or send traffic that could degrade the Services for others. When you receive a rate limit response, wait for the indicated interval before retrying. We may throttle or suspend credentials that cause excessive load or abuse.
4. Acceptable use of the APIs
You must comply with the Acceptable Use Policy and applicable law. In addition, you may not:
- use the APIs to collect, store or process data beyond what your integration needs, or use data obtained through the APIs for any purpose the merchant has not authorized;
- sell, license or disclose data obtained through the APIs to third parties, except to the merchant who owns it or as the merchant instructs;
- misrepresent your integration, or imply that Wafle sponsors or endorses it without our written permission;
- probe or test the security of the APIs without our written permission;
- use the APIs to send unsolicited messages or to perform actions the merchant has not authorized.
5. Merchant and customer data
Data you access through the APIs belongs to the merchant, and merchants' customers' personal data is governed by applicable privacy law. You must handle it securely, use it only to provide your integration to the merchant, honor the merchant's instructions and deletion requests, and delete it when it is no longer needed or when the merchant stops using your integration. If you process personal data on behalf of merchants, you are responsible for meeting the requirements of applicable data protection laws.
6. AI assistants and MCP
The MCP integration lets an AI assistant take actions in a store with the permissions of the credential it uses. You are responsible for the assistant's actions and for reviewing them where they affect prices, orders, customers, spending or published content. Choose the narrowest permissions that fit the task. Do not use an assistant, or instruct it, in a way that would violate these terms or the law. Output generated by AI features may be inaccurate, so review it before relying on it.
7. Availability
We aim to keep the APIs available, but we do not guarantee uninterrupted access. We may perform maintenance and may limit or suspend access when needed to protect the Services.
8. Changes and deprecation
We may update the APIs and documentation. We will make reasonable efforts to give advance notice of changes that break existing integrations, for example in the developer changelog, and to keep a deprecated version available for a reasonable period. We may change or remove features immediately when needed for security, legal or abuse-prevention reasons.
9. Third-party apps
If you make your integration available to other merchants, you are responsible for its terms, its support, its security and its compliance with law. Wafle does not review integrations and is not responsible for them.
10. Ownership and feedback
Wafle and its licensors retain all rights in the APIs and the documentation. You retain the rights in your integration, excluding the APIs and Wafle materials. If you give us feedback or suggestions, we may use them without restriction or obligation to you.
11. Suspension and termination
We may suspend or terminate your access to the APIs at any time if you violate these Developer Terms or the Terms of Service, if your use poses risk to the Services or others, or if we stop offering the APIs. You may stop using the APIs at any time. On termination you must stop using the APIs and delete the documentation and any data you are not permitted to keep.
12. Disclaimers, liability and law
The APIs are provided "as is" and "as available," and the disclaimers, limitations of liability and indemnification in the Terms of Service apply to your use of them. the laws of the State of Delaware, without regard to its conflict-of-laws principles governs these Developer Terms, and disputes will be brought in the state and federal courts located in the State of Delaware, as set out in the Terms of Service.
13. Support
For help building an integration, use the developer documentation and contact support.
Get help with my store
Setup, products, payments, domains, orders and anything else about running your store.
Open the formReport abuse
Report a store or content that violates our Acceptable Use Policy, such as fraud, malware or illegal goods.
Open the form