SanctiKey

Legal

API Terms of Use

SanctiKey, LLC · Last Updated: October 11, 2026 · Effective Date: October 11, 2026

1. Purpose and Scope

These API Terms of Use ("API Terms") govern programmatic access to the SanctiKey managed cryptographic infrastructure platform via its developer APIs (the "API"). These API Terms supplement and are incorporated into SanctiKey's Terms of Service. In the event of a conflict between these API Terms and the Terms of Service with respect to API access, these API Terms control.

By accessing or using the API, you agree to these API Terms. If you do not agree, you must not access or use the API.

API access is bundled with all active SanctiKey subscriptions. There is no separate API product tier.

2. API Credentials and Authentication

2.1 Credential Issuance

API credentials (API keys and access tokens) are created through your account's administrative controls, subject to the key policies your administrators define. Outside the Demo Environment, credentials are not issued automatically. All credentials are unique to your account and subscription.

2.2 Credential Security

You are solely responsible for:

  • Maintaining the confidentiality and security of all API credentials issued to your account
  • Ensuring API credentials are not stored in source code, version control repositories, client-side code, or any publicly accessible location
  • Rotating credentials immediately upon any suspected or confirmed exposure
  • All API calls made using your credentials, whether authorized by you or not

SanctiKey cannot be held liable for unauthorized API usage resulting from your failure to secure your credentials.

2.3 Credential Revocation

SanctiKey reserves the right to revoke API credentials immediately and without prior notice if SanctiKey determines the credentials are being used in violation of these API Terms, the Acceptable Use Policy, or the Terms of Service.

3. Rate Limits

3.1 Standard Rate Limit

All subscriptions are subject to a standard API rate limit of 100 requests per minute per account. This limit applies across all API endpoints collectively.

3.2 Operational Quota (Usage-Metered)

SanctiKey pricing is prepaid and linear, not tier-based. Your base subscription includes a bundled allotment of 100,000 operational API calls per month for the account; key slots do not add to it. Additional operational capacity is purchased in advance in blocks of 100,000 at the published per-block rate; there is no overage billing, no separate overage SKU, and no automatic tier upgrade.

You purchase and reduce every billed component of your subscription (keys, operation blocks, served regions, placed keys, and failover protection) only in the account portal. The SanctiKey console displays your current quantities and links to the account portal; it does not accept purchases or reductions.

SanctiKey confirms a reduction against your current use of that component before accepting it. A reduction below current use is refused; for example, you cannot reduce your key count below the number of keys you hold, including keys pending deletion, and you cannot release the one key slot and one operation block your base subscription includes. A refused reduction leaves your subscription unchanged, and SanctiKey notifies you by email and in the account portal of what is in use and what you must remove first. A reduction of operation blocks is also refused if the operation units remaining would fall below the units already used this month. An accepted reduction of key slots, operation blocks, or placed keys lowers the limit at once, and the unused remainder of the current period is credited pro rata on your next invoice. A removal of a served region or of failover protection is accepted at your request and ends on the 1st of the next month, when its billing and its capacity end together, with no refund or credit for the remainder of the current period; you can withdraw it at no cost before the 1st. An addition takes effect at once and is charged pro rata for the remainder of the current period. Billing periods follow the calendar month in Coordinated Universal Time (UTC). Every subscription renews on the 1st of the month, and your first invoice is prorated for the partial month in which you subscribe.

Administrative API calls (key creation, rotation configuration, policy management, and key listing) do not count against your operational allotment and are always free.

There is no cap on the number of key slots an account may hold. The account portal accepts at most 25 key slot additions in any rolling seven days; for a larger increase, email support@sanctikey.com, and once SanctiKey approves the request the limit is lifted for that increase. Current rates are published in SanctiKey's Pricing Schedule.

3.3 Rate Limit Enforcement

Requests exceeding the per-minute rate limit will receive an HTTP 429 (Too Many Requests) response. Your integration must implement appropriate retry logic with exponential backoff when receiving 429 responses. SanctiKey is not liable for data loss, operational failures, or downstream application errors resulting from rate limit enforcement.

3.4 Prepaid Allotment Exhaustion

All operational capacity is prepaid. SanctiKey does not bill automatically for usage beyond your bundled allotment. When your operational allotment for the billing period is exhausted, further operational API calls are declined with an HTTP 429 response until you purchase an additional block of 100,000 operational calls in the account portal at the published per-block rate; your bill can never exceed what you have already agreed to pay. The per-minute rate limit in Section 3.1 continues to apply independently. SanctiKey is not liable for data loss, operational failures, or downstream application errors resulting from allotment exhaustion enforcement.

4. Client-Side Implementation Responsibility

4.1 Your Responsibility for Integration Quality

SanctiKey provides well-documented APIs and developer resources. You are solely responsible for:

  • The quality, correctness, and security of your API integration code, including testing it before deploying to production
  • Implementing appropriate error handling for all API responses including 4xx and 5xx status codes
  • Implementing retry logic with exponential backoff for transient failures; looping calls without backoff is a violation of these API Terms and may result in rate limit enforcement or account suspension
  • Correctly handling API responses including returned data key material (for example, plaintext data keys returned by envelope-encryption endpoints); mishandling returned data key material is outside SanctiKey’s control and liability. Managed private keys are non-extractable and are never returned by any endpoint
  • Keeping your integration up to date with API version changes per the deprecation policy in Section 6

4.2 No Liability for Client-Side Failures

SanctiKey is not liable for data loss, key loss, encryption failures, or application errors arising from:

  • Bugs or errors in your integration code
  • Incorrect handling of API responses or returned data key material
  • Failure to implement appropriate error handling or retry logic
  • Misuse of API endpoints contrary to the Documentation
  • Loss of returned data key material due to inadequate client-side storage practices

4.3 Production Readiness

Before deploying any SanctiKey API integration to production, you should:

  • Test all integration flows in a non-production environment of your own
  • Verify correct handling of all documented error codes
  • Confirm that returned data key material is stored securely and never logged or exposed in plaintext
  • Implement monitoring for API error rates and latency

5. Permitted and Prohibited API Use

5.1 Permitted Use

You may use the API solely for:

  • Programmatic access to cryptographic services within your Subscription Plan
  • Automating key management operations within your account
  • Building internal applications that consume SanctiKey’s cryptographic capabilities for your own business purposes
  • Integration with your own products and services in accordance with the Acceptable Use Policy

5.2 Prohibited API Use

In addition to the prohibitions in the Acceptable Use Policy, you may not use the API to:

  • Build a product or service that resells, repackages, or provides access to SanctiKey’s cryptographic capabilities to third parties without SanctiKey’s prior written consent
  • Circumvent, probe, or test rate limiting or quota enforcement mechanisms
  • Automate the creation of accounts or credentials in bulk
  • Access endpoints not documented in SanctiKey’s official API documentation
  • Attempt to extract, reconstruct, or reverse-engineer SanctiKey’s underlying cryptographic implementations through systematic API probing or analysis of API responses
  • Send requests at volumes or patterns designed to stress-test SanctiKey’s infrastructure without prior written authorization

6. API Versioning and Deprecation

6.1 Versioning

SanctiKey's API is versioned. The current API version is specified in the Documentation at docs.sanctikey.com. SanctiKey recommends always integrating against a specific API version rather than an unversioned endpoint.

6.2 Deprecation Notice

SanctiKey will provide at least 90 days' advance notice before deprecating or removing any API endpoint or capability that is in documented general availability. Notice will be provided via email to the account administrator and through the API documentation changelog.

6.3 Breaking Changes

SanctiKey will use commercially reasonable efforts to avoid introducing breaking changes to existing API versions. When breaking changes are necessary, they will be introduced in a new API version with the prior version maintained for the duration of the deprecation notice period.

6.4 Beta Endpoints

API endpoints designated as beta, preview, or experimental in the Documentation are subject to change or removal without notice and are not covered by the deprecation policy in this Section 6.

7. Monitoring and Enforcement

SanctiKey monitors API usage patterns to enforce rate limits, detect abuse, and protect platform integrity for all customers. Monitoring is performed at the metadata level; SanctiKey does not inspect or retain the content of API payloads.

Violations of these API Terms may result in rate limiting, credential revocation, account suspension, or termination in accordance with the Terms of Service and Acceptable Use Policy.

8. Amendments

SanctiKey may update these API Terms at any time. Material changes will be communicated by email and by updating the "Last Updated" date. Your continued use of the API after the effective date of any amendment constitutes acceptance.

9. Contact

SanctiKey, LLC
Developer Support: support@sanctikey.com
API Documentation: docs.sanctikey.com
Security: security@sanctikey.com

These API Terms of Use are effective as of the date listed above and supersede all prior versions.