Rubysoft
EN
EN NL

API terms

Terms for use of Rubysoft APIs

Rubysoft B.V.

Exa 12

6902 KH Zevenaar

The Netherlands

Dutch Chamber of Commerce (KvK): 30169161

VAT ID: NL810606136B01

Website: www.rubysoft.eu

Email: support@rubysoft.eu

Document Control

Property Value
Document Api Terms
Organization Rubysoft B.V.
Version 2.0
Status Final
Language English (US)
Scope APIs and API access made available by Rubysoft
Effective date Date of publication

1. Purpose and applicability

  1. These API Terms apply when Rubysoft B.V. grants a Customer or third party access to a Rubysoft Application Programming Interface (API).

  2. They supplement Rubysoft's General Terms of Delivery and License and Acceptable Use Policy.

  3. Specific functionality, access rights, technical limits, fees, and permitted purposes may be specified in a quotation, agreement, or Documentation. Specific written API arrangements prevail in the event of a conflict.

  4. Making an API available does not obligate Rubysoft to offer the same API, functionality, or technical architecture permanently.

2. API access

  1. Access is granted only to persons or organizations authorized by Rubysoft. Rubysoft may use API keys, tokens, accounts, certificates, or other authentication mechanisms.

  2. The Customer must keep credentials confidential and take reasonable measures against unauthorized use.

  3. Credentials may be shared with a third party only where necessary for permitted use and where that party is subject to appropriate confidentiality and security obligations.

  4. Loss, unauthorized disclosure, or suspected misuse must be reported to Rubysoft without undue delay.

3. Permitted use

  1. An API may be used only for the purpose for which Rubysoft granted access and in accordance with these Terms, applicable Documentation, technical instructions, and law.

  2. The Customer is responsible for software, integrations, and processes it develops or has developed using the API.

  3. API use does not transfer ownership of the API, underlying Software, Documentation, data structures, or other Rubysoft intellectual property.

  4. Where an API provides access to Customer data, the Customer remains responsible for the lawfulness of use and further processing.

4. Prohibited use

  1. Users may not circumvent API security, access restrictions, License conditions, rate limits, or other technical restrictions; unnecessarily burden or disrupt Rubysoft systems; or seek access to unauthorized data, functionality, or systems.

  2. API access may not be resold, offered as a standalone third-party service, or commercially exploited outside the agreed use without Rubysoft's prior written consent.

  3. The API may not be systematically analyzed or used to develop a competing product or functional reproduction of Rubysoft Software.

  4. Rubysoft's Acceptable Use Policy applies in full.

5. API keys and security

  1. The Customer must store API keys, tokens, and other authentication data securely and must not place them in public source code, public repositories, unsecured configuration files, or other locations accessible to unauthorized persons.

  2. Access to credentials must be limited to persons and systems that need them for the agreed purpose.

  3. Rubysoft may revoke, replace, or temporarily block credentials where there is a security risk, suspected misuse, or legal obligation, and will inform the Customer in advance or as soon as reasonably possible afterward.

6. Technical limits and capacity

  1. Rubysoft may apply limits to request volumes, data volumes, concurrent connections, file sizes, or other technical parameters. Limits may differ by API, product, License, or agreement.

  2. The Customer may not circumvent limits through multiple accounts, keys, connections, or other methods.

  3. If normal agreed use structurally requires greater capacity, the parties may agree additional arrangements.

  4. Rubysoft may temporarily impose additional restrictions where necessary to protect security, stability, or availability.

7. Availability

  1. Rubysoft aims to provide reliable API availability but does not guarantee uninterrupted or error-free operation unless a Service Level Agreement expressly provides otherwise.

  2. Maintenance, security measures, technical failures, supplier changes, and other circumstances may temporarily affect availability.

  3. Planned maintenance expected to materially affect a production API will be announced in advance where reasonably possible.

  4. Where appropriate, the Customer should design its integration to handle temporary unavailability, timeouts, and error responses.

8. Changes and versioning

  1. Rubysoft may change APIs to improve functionality, address security risks, reduce technical debt, support standards, or comply with law.

  2. Rubysoft aims to announce material breaking changes in advance and, where reasonably possible, provide a transition period. Security issues, misuse, or urgent legal obligations may require shorter notice.

  3. Rubysoft may support multiple API versions and may discontinue older versions. The Customer is responsible for timely adaptation to announced new or changed versions.

9. Documentation

  1. Rubysoft may provide technical Documentation, examples, schemas, and instructions. The Customer must use the API in accordance with current Documentation.

  2. Examples and sample code are provided for assistance and are not warranted to be suitable without modification for the Customer's specific application.

  3. Rubysoft may update Documentation when the API or recommended technical practices change.

10. Data and data quality

  1. An API may receive, process, or expose data originating from Rubysoft, the Customer, or third parties.

  2. The Customer remains responsible for the accuracy and lawfulness of data submitted through an API.

  3. Rubysoft uses reasonable efforts to correctly process data supplied by its own systems, but the Customer remains responsible for appropriate checks before data is used for business-critical decisions, production, or ordering.

  4. A technical acknowledgement that an API request was received does not mean its content is substantively correct, complete, or fit for purpose.

11. Personal Data and privacy

  1. Where an API processes Personal Data, the parties must comply with applicable data protection law.

  2. Rubysoft's Privacy Policy applies where Rubysoft acts as Controller. Rubysoft's DPA may apply where Rubysoft processes Personal Data on behalf of a business Customer.

  3. The Customer must not process more Personal Data through an API than necessary for the agreed purpose.

  4. API integrations should, where reasonably possible, apply data protection by design and by default and data minimization.

12. Logging and security information

  1. Rubysoft may log technical API usage information for security, diagnostics, capacity management, billing where applicable, and compliance monitoring.

  2. Logs may include request time, API version, technical access identifier, response codes, and data volume.

  3. Logging will be limited to what is reasonably necessary for those purposes. Customer business-data content is not used for marketing.

13. Intellectual property

  1. All intellectual property rights in the API, Software, Documentation, technical designs, and Rubysoft-developed data structures remain with Rubysoft or its licensors.

  2. The Customer receives only a limited right to use the API during the agreed period and for the agreed purpose.

  3. The Customer retains rights in its own software, project data, and materials. Feedback and improvement suggestions may be used by Rubysoft free of charge for product and service development.

14. Developers and third parties

  1. The Customer may engage an external developer to implement an API integration unless the Agreement provides otherwise.

  2. The Customer remains responsible to Rubysoft for API use by its developer or other third party and must ensure access is limited to what is necessary and subject to appropriate confidentiality and security obligations.

  3. Engaging a third party does not give that party an independent right to use the API.

15. API support

  1. The scope of API support is determined by the relevant agreement, product, or published support information.

  2. Regular API support may cover Documentation, authentication, error messages, and suspected API defects. Development, debugging, or maintenance of Customer or third-party software is not included by default.

  3. Rubysoft may offer additional technical assistance or consulting as an Additional Service. Rubysoft's Support Terms apply to the extent appropriate to API services.

16. Test and Beta APIs

  1. Rubysoft may provide test environments, sandbox APIs, preview functions, or Beta APIs.

  2. Such environments may differ from production and must not be used for business-critical processes unless expressly permitted.

  3. Rubysoft's Beta Program Terms also apply to Beta APIs. Rubysoft may change, reset, or terminate test data, test environments, or Beta APIs at any time.

17. Fees

  1. Separate fees may apply to API access.

  2. If charges depend on usage, volume, transactions, or other measurable units, the basis will be agreed in advance in the agreement, quotation, or pricing information.

  3. Rubysoft will not charge usage-based fees without an agreed pricing basis for the relevant API. Taxes and charges are governed by the General Terms.

18. Suspension and termination

  1. Rubysoft may temporarily suspend API access where necessary because of a serious security risk, demonstrable misuse, non-payment, disproportionate service disruption, or a legal obligation.

  2. Where reasonably possible, the Customer will first be given an opportunity to remedy the issue. Immediate suspension is permitted where delay creates a genuine risk to Rubysoft, other customers, data, or systems.

  3. When the underlying Agreement ends, API access also ends unless agreed otherwise. After termination, invalid API keys and credentials must no longer be used.

19. Liability and Customer integration

  1. The Customer is responsible for the design, testing, management, and operation of its own API integration.

  2. Rubysoft is not responsible for errors arising solely in Customer or third-party software, configurations, or processes.

  3. The Customer must appropriately test an integration before using it for business-critical production, ordering, or data exchange.

  4. Rubysoft's General Terms of Delivery and License govern liability to the extent permitted by mandatory law.

20. Sanctions and export restrictions

  1. API access may not be used or made available in violation of applicable sanctions, export-control, or trade laws.

  2. Rubysoft may refuse, restrict, or terminate access where continuation would reasonably violate such laws.

21. Changes to these Terms

  1. Rubysoft may amend these API Terms where its API services, technical architecture, security requirements, or applicable law require it.

  2. The current version will be made available through the website, Documentation, or electronically.

  3. For existing paid API services, Rubysoft will announce material changes affecting the agreed use in advance where reasonably possible.

22. Contact

  1. Technical questions and API access reports may be sent to support@rubysoft.eu or another channel designated for the relevant API.

  2. Rubysoft B.V. is located at Exa 12, 6902 KH Zevenaar, The Netherlands.

23. Citation title

  1. These terms may be cited as: API Terms Rubysoft B.V. – version 2.0.