MEWSY POLICIES
API Usage Policy
Use outfit data responsibly and keep access fair.
Last updated
Keys and Permissions
Each account may have one unrevoked API key. It receives the account’s assigned scopes, with all default scopes enabled unless an administrator restricts them. Request missing scopes through the dashboard. Admin changes apply to subsequent requests, and replacing a key does not reset restrictions.
Keep credentials on your server, never in browser bundles, public repositories, or Roblox LocalScripts. Do not sell or publicly share your key. Revoke it if exposed.
Subscription Access
API requests require an active developer subscription and enabled API access. Keys have no automatic expiry. An inactive subscription returns HTTP 402 with a renewal URL; it does not delete the key. Billing-confirmed renewal restores access to an unrevoked key with its existing permissions.
Usage Limits
The developer plan allows 100,000 request units per UTC calendar month and 120 per minute, shared by your account’s API and dashboard requests. Bulk requests accept up to 50 codes. The quota calendar is separate from your billing cycle; replacing a key does not reset it.
Admitted requests may consume units even if an outfit is missing or later processing fails. Follow the documentation for endpoint costs, HTTP 429 responses, Retry-After instructions, and backoff. Do not evade quotas, flood requests, or bypass access controls.
Outfit Data and Exports
Data comes from the official mewsy game. Respect visibility and moderation states; do not try to retrieve restricted or deleted outfits. Stop serving cached content when you learn it has been restricted. Data access does not grant ownership of items or permission to misuse player information.
Free in-game exports to Studio are separate from the API plan. Pair with the /studio command, keep pairing codes private, and follow export cooldowns. Only export content you are authorized to use.
Enforcement and Support
We may throttle requests, change scopes, revoke keys, or suspend access to address abuse and security concerns. Contact [email protected] if you believe a restriction is mistaken. Report vulnerabilities privately without accessing other users’ data. Availability and data freshness are not guaranteed; review results before relying on them.
Need a hand?
[email protected] · Discord support ↗
Keep private account and payment details out of public channels.