API terms of use
Last updated: November 11, 2026
These API Terms of Use (“API Terms”) govern access to and use of the Saleya Integration API at api.saleya.app/v1, including its documentation, OpenAPI specification, Postman collection, webhooks and event feed (together, the “API”). They form part of the Terms of Service: the Terms of Service also apply to the API, and where the two differ on the API, these API Terms prevail. By creating an app or using an API token, you agree to these API Terms.
1. Who may use the API
The API is available to accounts whose plan includes it, as shown on the pricing page, including during a trial. The business that holds the account (“you”) creates apps in its store and issues their tokens. A developer, agency or software provider may use the API on your behalf (an “integrator”). You are responsible for how your tokens are used, and your integrators must follow these API Terms.
2. Apps, tokens and scopes
Each app has access to one store and acts there as a service account limited to the scopes granted to it. You must:
- Grant each app only the scopes it needs
- Keep tokens secret and never place them in browser or mobile app code, public repositories or messages
- Restrict tokens to the IP addresses of your servers where possible
- Rotate a token you suspect has leaked and revoke tokens you no longer use
- Report a compromised token to legal@saleya.app without delay
We may revoke a token that we have reason to believe is compromised or misused; we notify you when we do.
3. Rate limits and fair use
The API enforces the request limits described in its documentation and answers requests over a limit with status 429 and a Retry-After header. You must not:
- Work around the limits, for example by spreading requests across several apps or accounts
- Poll for data that has not changed where the change feeds or webhooks would serve
- Run load tests or security tests against the API without our prior written consent
For large volumes, use bulk operations. Limits may change; changes are announced in the API changelog.
4. Use of data obtained through the API
Data obtained through the API, including personal data of your customers, may be used only to serve your business. Your integrators must:
- Use the data only for the purposes for which you connected them
- Not sell the data or use it to build advertising profiles of your customers
- Protect the data with appropriate security measures
- Delete data they no longer need, and all of it when you revoke their access, unless the law requires them to keep it
- Comply with the data protection laws that apply to them
An app receives personal data of your customers only with the scopes that grant it, as stated in the documentation. Saleya’s own processing of that data is governed by the Data Processing Addendum. An integrator processes the data for you, not for Saleya; where the law requires an agreement between you and your integrator — a data processing agreement and, if the integrator processes the data outside Argentina, safeguards for the international transfer — you are responsible for having it.
5. Webhooks
Webhook endpoints must use HTTPS and verify the signature of every delivery before acting on it. Deliveries that fail are retried; an endpoint that keeps failing is disabled after the period stated in the documentation, and we notify the store owner by email.
6. Testing
Use a separate development store on your account to build and test integrations. Requests made in a live store are real operations: orders, stock changes and refunds take effect exactly as they would in the store panel.
7. Prohibited uses
You and your integrators must not use the API to:
- Access data of a store that has not authorized the app
- Probe for or exploit vulnerabilities; report them to legal@saleya.app instead
- Interfere with the operation of the Service or with other customers
- Misrepresent who is making requests or why
- Violate the law or the Terms of Service
8. Versioning and changes
Within /v1 we do not remove or rename endpoints, fields, parameters or headers, change the type or format of a field, add required input or tighten input limits, change an error type or its HTTP status, or require a new scope for an existing endpoint. We may add endpoints, optional parameters, response fields, enumeration values in responses, error types and event types at any time; your integration must ignore what it does not recognize.
A breaking change is released as a new version next to /v1, and /v1 remains available for at least 12 months after the new version is released. Changes are announced in the API changelog and its feed. A change required to fix a security vulnerability or to comply with the law may take effect sooner; we announce it in the changelog as early as we can.
9. Availability and support
The API is provided on the same availability terms as the rest of the Service. Support for the API is available at support@saleya.app.
10. Suspension and termination
We may suspend or revoke an app or its tokens if it violates these API Terms, endangers the security of the Service or of other customers, or overloads the Service. Where possible, we notify you first. If your plan no longer includes the API, requests are rejected until it does again; your apps and their settings are kept.
11. Intellectual property
The API, its documentation and the Saleya brand belong to Saleya. You may use the documentation, the OpenAPI specification and the Postman collection to build and operate integrations with Saleya, including generating client code from the specification; that code is yours. You may say that your product works with Saleya, but not that Saleya endorses it, without our written consent.
12. Disclaimer and liability
The API is provided “as is” and “as available”. The disclaimer and the limitation of liability in the Terms of Service apply to the API. You are responsible for the operations that your integrations perform in your store.
13. Changes to these API Terms
We may update these API Terms. If a change is material, we notify account owners by email before it takes effect and update the “Last updated” date.
14. Contact
For questions regarding these API Terms: Mikhaylova Elizaveta, CUIT 27-96484417-3, Argentina — legal@saleya.app.