Asystio
Back to Legal Center
Official

API Terms of Use

Last updated: March 1, 2026Official

1. API Keys and Authentication

  • API access requires a unique API key assigned to your account. Treat it as confidential - do not expose it in client-side code or public repositories. If compromised, rotate it immediately via the Asystio dashboard or contact support.
  • All API calls must include the key (e.g., Authorization: Bearer <API_KEY>).
  • Create separate keys for different applications with minimal required permissions (principle of least privilege).

2. Versioning and Stability

  • The API is versioned (v1, v2, etc.). We maintain backward compatibility within each major version.
  • Deprecated versions receive at least 6 months of continued support with migration guidance.
  • Only documented endpoints and behaviors are supported - undocumented features may change without notice.

3. Rate Limits and Fair Use

  • Default limits: 60 requests/minute and 2,500 requests/hour per key. Higher-tier plans may have elevated limits.
  • Exceeding limits returns HTTP 429 (Too Many Requests). Repeated violations may result in temporary key suspension.
  • Do not circumvent limits using multiple keys, IP rotation, or other techniques. Contact us if you need higher limits.
  • Resource-intensive operations (large report generation, bulk imports) should be spread over time to avoid system overload.

4. Data Ownership and Integration

  • Data sent through the API remains your property. Asystio processes it to generate responses and does not claim rights to your input.
  • API outputs may be used within your application per your subscription agreement. Users are responsible for verifying AI-generated content before publication.
  • We retain API call metadata (timestamps, endpoints, response codes) for monitoring and billing. Request/response content may be temporarily cached for debugging per our Privacy Policy.

5. Security Requirements

  • All API connections must use HTTPS (TLS 1.2+).
  • Rotate API keys periodically and store them server-side only.
  • Implement proper error handling with exponential backoff for retries.
  • Ensure your integration does not enable injection attacks against our API. The Acceptable Use Policy applies equally to API usage.

6. Changes and Notifications

Breaking changes are communicated at least 30 days in advance via email and our developer changelog. Subscribe to our developer newsletter or RSS feed for updates.

7. Liability Limitations

The API is provided 'as-is'. While we strive for reliability, we do not guarantee error-free or uninterrupted operation. Our liability is limited per the main Terms of Service. Integrators should test thoroughly and implement fallback mechanisms (e.g., caching) for availability issues.

8. Partner Program

Developers building third-party plugins or integrations using the Asystio API should join our partner program for official support, branding guidelines, and compliance verification. Unauthorized integrations that violate these terms may be blocked.

9. General

These API Terms supplement the main Terms of Service. Unaddressed matters are governed by the Terms of Service (applicable law, dispute resolution). Asystio reserves the right to suspend or block API keys that violate these terms or the Acceptable Use Policy.