Shipmuch
Sign InSign Up
Sign Up
Sign In

API & Developer Usage Policy

Last Updated: May 2026

1. Introduction

This API & Developer Usage Policy (“Policy”) governs access to and use of:

  • Shipmuch APIs;
  • deployment endpoints;
  • automation systems;
  • webhooks;
  • SDKs;
  • developer tooling;
  • command-line interfaces;
  • and related developer services (collectively, the “Developer Services”).

Shipmuch is operated by TORIS Technologies (Pty) Ltd (“Shipmuch”, “we”, “us”, or “our”).

This Policy forms part of the Shipmuch Terms of Service and Acceptable Use Policy.

2. Purpose

The purpose of this Policy is to:

  • maintain platform stability;
  • protect infrastructure reliability;
  • prevent abuse of Developer Services;
  • support fair usage;
  • and ensure operational security.

3. Authorized Usage

Customers may use the Developer Services solely for:

  • legitimate deployment automation;
  • infrastructure management;
  • application operations;
  • integration development;
  • and approved operational workflows.

Use of Developer Services must comply with:

  • applicable laws;
  • the Terms of Service;
  • the Acceptable Use Policy;
  • and this Policy.

4. API Authentication

Customers are responsible for:

  • securing API credentials;
  • protecting tokens and secrets;
  • rotating compromised credentials;
  • and restricting unauthorized access.

API credentials may not be:

  • shared publicly;
  • embedded insecurely;
  • or exposed in client-side environments unless explicitly supported.

5. Rate Limits & Fair Usage

Shipmuch may implement:

  • request limits;
  • concurrency limits;
  • deployment queue restrictions;
  • webhook delivery limits;
  • and operational throttling mechanisms.

Customers may not:

  • intentionally bypass rate limits;
  • overload infrastructure;
  • generate abusive traffic;
  • or interfere with platform stability.

Shipmuch reserves the right to modify rate limits at any time.

6. Prohibited Activities

Customers may not use Developer Services to:

  • scrape platform data;
  • reverse engineer internal systems;
  • abuse deployment pipelines;
  • interfere with infrastructure operations;
  • perform denial-of-service attacks;
  • generate excessive automated traffic;
  • bypass authentication systems;
  • or exploit platform vulnerabilities.

7. Webhooks & Automation

Customers using webhooks or automation systems are responsible for:

  • validating webhook security;
  • protecting secrets;
  • handling retries safely;
  • and managing automation workflows responsibly.

Shipmuch is not responsible for:

  • failed webhook deliveries;
  • customer automation errors;
  • or downstream operational failures.

8. Infrastructure Impact

Shipmuch may:

  • throttle requests;
  • suspend integrations;
  • queue deployments;
  • or temporarily restrict Developer Services where operational stability or infrastructure integrity is at risk.

9. API Availability

Developer Services may experience:

  • maintenance interruptions;
  • infrastructure failures;
  • degraded performance;
  • or operational changes.

Shipmuch does not guarantee:

  • uninterrupted API availability;
  • backward compatibility;
  • or permanent endpoint stability.

10. Versioning & Deprecation

Shipmuch may:

  • modify APIs;
  • introduce new versions;
  • deprecate endpoints;
  • or discontinue functionality.

Where practical, reasonable notice may be provided before major breaking changes.

Customers remain responsible for maintaining compatibility with supported API versions.

11. Monitoring & Logging

Shipmuch may monitor Developer Services for:

  • abuse detection;
  • operational performance;
  • infrastructure reliability;
  • fraud prevention;
  • and security investigations.

Monitoring may include:

  • request metadata;
  • API usage patterns;
  • deployment telemetry;
  • and operational diagnostics.

12. Third-Party Integrations

Developer Services may integrate with:

  • GitHub;
  • cloud providers;
  • DNS providers;
  • registries;
  • CI/CD systems;
  • and third-party operational tooling.

Shipmuch is not responsible for failures originating from third-party services.

13. Intellectual Property

Shipmuch retains ownership of:

  • APIs;
  • documentation;
  • SDKs;
  • operational tooling;
  • platform systems;
  • and related intellectual property.

This Policy does not grant ownership rights to Developer Services.

14. Suspension & Enforcement

Shipmuch may suspend or terminate access to Developer Services for:

  • abuse;
  • operational risk;
  • security threats;
  • violations of this Policy;
  • excessive usage;
  • or unlawful activity.

Enforcement actions may occur without prior notice where necessary to protect infrastructure.

15. Beta Developer Features

Certain Developer Services may be:

  • beta;
  • preview;
  • experimental;
  • or early-access features.

Such features:

  • may change without notice;
  • may be unstable;
  • and may not be suitable for production use.

16. Limitation of Liability

Shipmuch shall not be liable for:

  • failed API requests;
  • automation failures;
  • deployment interruptions;
  • integration issues;
  • webhook delivery failures;
  • or operational disruptions arising from Developer Services usage.

Customers remain responsible for:

  • validating workflows;
  • implementing retries;
  • and maintaining operational safeguards.

17. Changes to This Policy

Shipmuch may update this Policy periodically to reflect:

  • infrastructure evolution;
  • API changes;
  • operational requirements;
  • or security improvements.

Updated versions will be published with revised effective dates.

18. Contact Information

Developer Support: support@shipmuch.com

Security: security@shipmuch.com

Legal: legal@shipmuch.com

Operator: TORIS Technologies (Pty) Ltd Verwoerdpark Alberton Gauteng South Africa

19. Governing Law

This Policy is governed by the laws of the Republic of South Africa.