API Terms.

These API Terms (“API Terms”) govern access to and use of Fabrixa’s APIs, webhooks, integrations, and related developer materials (collectively, the “API”). These API Terms form part of Fabrixa’s Terms of Service (the “Terms”). If there is a conflict, the following order applies: (1) any signed Master Agreement, (2) any SLA (if any), (3) these API Terms, (4) the Terms and other Policies. Capitalised terms not defined here have the meaning given in the Terms.

1. Eligibility & scope

1.1 Business use only. The API is provided solely for business customers to place and manage Orders for Fabrixa Products and to receive operational updates related to fulfilment.

1.2 No consumer use. The API is not offered for consumer use or personal projects.

2. API documentation

2.1 Documentation. Fabrixa may publish API documentation (“API Docs”) describing endpoints, payloads, authentication methods, and operational guidance.

2.2 Docs can change. The API Docs may change over time. They are operational instructions and do not create service guarantees or legal obligations beyond these API Terms, the Terms, and any SLA.

2.3 Compliance with current docs. Customer agrees to integrate and operate in accordance with the then-current API Docs.

3. Access, keys & security

3.1 Credentials. Fabrixa will provide API credentials (keys/tokens). Customer must keep credentials secure and confidential.

3.2 Responsibility for use. All activity performed using Customer credentials is deemed authorised by Customer. Customer is responsible for all calls and actions made using its keys unless it proves unauthorised use not attributable to Customer’s negligence and notifies Fabrixa promptly.

3.3 Security measures. Customer must implement reasonable security controls, including:

• (a) secure storage of keys (no hardcoding in public repos),
• (b) role-based access / least privilege,
• (c) timely rotation on suspected compromise,
• (d) encryption in transit (TLS) for all API interactions.

3.4 Compromise notice. Customer must notify Fabrixa without undue delay if credentials are compromised or suspected to be compromised.

4. Permitted use

4.1 Permitted purpose. Customer may use the API only to:

• (a) create and manage Orders for Fabrixa Products,
• (b) retrieve operational information made available by Fabrixa (e.g., order status, shipment status),
• (c) receive webhooks/notifications where enabled.

4.2 Internal business use. Customer may only use the API for its own internal business operations (including servicing its own End Customers), not for resale of raw API access to third parties as a standalone service, unless expressly agreed in writing.

5. Restrictions

Customer must not:

5.1 Abuse or overload the API, including attempting to bypass protective measures or rate limits.

5.2 Reverse engineer, scrape, or attempt to derive the underlying systems, routing logic, or fulfilment network.

5.3 Directly or indirectly use the API to build, train, or power a competing fulfilment/orchestration service.

5.4 Circumvent white-label protections by attempting to identify or contact fulfilment partners/locations through API data or other means.

5.5 Share API credentials with unauthorised parties or allow third parties to access the API under Customer’s credentials (except authorised integrators bound by confidentiality and security obligations at least as strict as these API Terms).

6. Order submission & duplicate prevention

6.1 Orders via API. Orders submitted via the API are Orders under the Terms and applicable Policies.

6.2 Data accuracy. Customer is responsible for all data submitted (addresses, variants, sizes, product selections, and content references).

6.3 Duplicate prevention. Customer will implement reasonable safeguards to prevent unintended duplicate Orders (including idempotency or equivalent mechanisms where supported) and will promptly cooperate with Fabrixa to resolve duplicate Order incidents.

6.4 Errors and retries. Customer is responsible for implementing reasonable retry/backoff logic where appropriate and for handling API errors in a way that does not create duplicate Orders.

7. Webhooks & customer endpoints

7.1 Endpoint responsibility. Where Customer uses webhooks or callback endpoints, Customer is responsible for maintaining the availability, performance, and security of such endpoint(s) and for acknowledging receipt in a timely manner.

7.2 Delivery reliability. Webhook delivery may be delayed, retried, or fail due to factors outside Fabrixa’s control (including Customer endpoint issues). Fabrixa is not responsible for missed or delayed updates caused by Customer endpoint unavailability or misconfiguration.

7.3 Operational reliance. Status updates are informational and may be subject to delays. Customer remains responsible for communications and decisions toward End Customers.

8. Availability, changes & maintenance

8.1 As available. The API is provided on an “as available” basis unless an SLA states otherwise.

8.2 Changes. Fabrixa may modify, suspend, or discontinue the API (or parts of it) and may update the API Docs at any time. Where feasible, Fabrixa will use reasonable efforts to provide notice of material/breaking changes.

8.3 Protective measures. Fabrixa may implement protective measures (including throttling, rate limits, feature restrictions, or temporary suspension) to protect security and platform stability.

9. Data protection & privacy

9.1 Lawful basis. Customer warrants it has a lawful basis to share End Customer data with Fabrixa for fulfilment.

9.2 DPA. Where applicable, the parties will enter into a Data Processing Addendum (DPA), which governs processing of personal data shared via the API.

9.3 Logs. Fabrixa may maintain technical logs for security, traceability, billing, debugging, and abuse prevention.

10. Confidentiality

10.1 Confidential information. API credentials, non-public API Docs, schemas, and non-public operational/commercial information (including routing principles and fulfilment network details) are confidential.

10.2 Protection. Customer must protect such information and not disclose it except to authorised integrators bound by confidentiality and security obligations at least as strict as these API Terms.

11. Fees

11.1 Fees. Fabrixa may charge fees for API access or usage as set out in Customer’s commercial terms, price list, or Master Agreement.

11.2 Suspension for non-payment. Fabrixa may suspend API access for non-payment or if Customer’s payment method/wallet is insufficient, consistent with the Terms.

12. Suspension & termination

12.1 Suspension. Fabrixa may suspend API access immediately if:

• (a) security is at risk or credentials are compromised,
• (b) Customer misuses or abuses the API,
• (c) Customer breaches these API Terms or the Terms,
• (d) required payments are overdue.

12.2 Termination. Either party may terminate API access on 30 days written notice unless otherwise agreed. Upon termination, Fabrixa will revoke credentials. Open Orders remain governed by the Terms and applicable Policies.

13. Disclaimers

13.1 No warranties. Except as expressly set out in an SLA, the API is provided “as is” and “as available”.

13.2 No guarantee. Fabrixa does not guarantee the API will be uninterrupted, error-free, or compatible with Customer systems.

14. Limitation of liability

API-related liability is subject to the limitation of liability in the Terms and/or any Master Agreement, unless prohibited by applicable law.

15. Contact

Developer / API support: contact our team.

Security reports: contact our team.