API Terms of Service
Last updated: October 2026
1. Acceptance of Terms
By accessing or using the SukkuAPI REST endpoints, you agree to be bound by these Terms of Service. If you disagree with any part of the terms, you may not access the service. SukkuAPI is an independent entity and is not affiliated with Mojang AB or Microsoft Corporation.
2. Data Ownership and Caching
Data provided by SukkuAPI is heavily processed and served through our proprietary caching engine to ensure optimal latency. We provide this data "as-is" without any warranties of absolute real-time accuracy, though our merge engine guarantees mathematical chronological consistency based on our internal records.
3. Required Headers (User-Agent)
To maintain the stability of our ecosystem and prevent unidentifiable scraping, all API requests MUST include a valid User-Agent header that clearly identifies your service, application, or Discord Bot.
User-Agent: MyDiscordBot/1.0 (contact@mydomain.com)
The use of generic, spoofed, or default library headers is strictly prohibited. Requests containing any of the following types of headers will be automatically rejected by our API Gateway:
- Spoofed Browser Headers: e.g.,
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/... - Default Python Libraries: e.g.,
python-requests/2.x.x,urllib/3.x. - Default JS/Node Libraries: e.g.,
axios/1.x.x,node-fetch.
Requests failing to provide identifiable headers may be subject to stricter rate limits or immediate blocking.
4. Abuse and Rate Limiting
Your API Key is tied to a specific quota and Rate Limit depending on your subscription tier. The following actions are strictly prohibited and will result in the immediate, irreversible revocation of your API Key without a refund:
- The use of automated proxy rotation, VPN pools, or Tor networks to bypass assigned IP-based or Key-based rate limits.
- Attempting to scrape the entirety of our database or performing web scraping/crawling on the SukkuAPI website pages.
- Using the provided player data to facilitate harassment, doxing, or malicious activities against Minecraft players.
5. Subscriptions and Billing
API access tiers are billed periodically. You are responsible for keeping your API Key secure. If your key is leaked and abused by a third party, your account will be held responsible for the generated traffic. You may regenerate your API Key at any time from your Developer Dashboard.
6. API Security & CORS Policy
As a developer, you are strictly responsible for securing the communication between your application and our API. Our API enforces strict security layers, including a strict CORS (Cross-Origin Resource Sharing) policy:
- Allowed Origins: Direct browser requests (CORS) are only permitted from officially authorized domains (e.g.,
https://www.sukku.devfor our official platform). - Backend-to-Backend Required: Any unauthorized domains attempting to call the API directly from a user's browser will be blocked by CORS policy. You must route all API calls through your own backend server.
- Client-Side Exposure: You must never expose your API Secret Key in client-side code (e.g., frontend JavaScript, mobile apps).
- Secure Transmission: All requests to the SukkuAPI must be made via HTTPS (TLS 1.2 or higher). Unencrypted HTTP requests are rejected.
7. Data Collection & Privacy
To maintain service integrity and prevent abuse, we collect and retain certain data when you interact with the SukkuAPI:
- Request Telemetry: We collect IP addresses, User-Agents, requested endpoints, and timestamps for every API call.
- Data Retention: Telemetry data is retained for up to 30 days for security audits, rate-limiting enforcement, and debugging.
- Privacy Guarantee: We do not sell this telemetry data to third parties. It is strictly used internally to monitor system health and protect against DDoS or scraping attacks.
8. Liability Limitations
SukkuAPI provides data strictly for entertainment and informational purposes. We do not guarantee 100% uptime unless specified in a custom Enterprise SLA. Under no circumstances shall SukkuAPI be liable for direct, indirect, or consequential damages resulting from API downtime, data inaccuracies, or unauthorized access to your account due to leaked keys.
9. Changes to Terms
We reserve the right to modify or replace these Terms at any time. We will provide at least 30 days notice prior to any new terms taking effect for active Plus Tier subscribers. What constitutes a material change will be determined at our sole discretion.