FAQ / Troubleshooting

A 400 error usually means you're missing required parameters or using an unsupported content type. Make sure you:

• Include either username or userId in your request
• Use POST method (not GET)
• Set Content-Type: application/json header if sending JSON
• Check that your JSON is valid

This means the username doesn't exist on Roblox, or the user has been deleted/banned. Double-check the username spelling and capitalization. Usernames are case-sensitive.

The API fetches groups from Roblox's API, which may have rate limits or pagination. Very active users with hundreds of groups might not have all groups returned in a single request. This is a limitation of Roblox's API, not this service.

Optional fields only appear if:

• You explicitly requested them (e.g., includeAvatar: true)
• The data is available from Roblox's API
• The user has that information (e.g., presence only shows if user is online/in-game)

This API proxies requests to Roblox's API, which has its own rate limits. We recommend:

• No more than 10-20 requests per minute per IP
• Implement exponential backoff if you hit rate limits
• Cache responses when possible (user data doesn't change frequently)
• Use batch requests or webhooks if you need to monitor many users

See the Rate Limits & Best Practices page for more details.

If you receive a rate limit error (usually HTTP 429), you should:

• Wait before retrying (exponential backoff: 1s, 2s, 4s, 8s...)
• Reduce your request frequency
• Check the response headers for Retry-After if available
• Consider caching responses to avoid redundant requests

CORS (Cross-Origin Resource Sharing) errors occur when making requests from a browser to a different domain. The API should handle CORS automatically, but if you're still experiencing issues:

• Make sure you're using POST method (not GET)
• Include proper headers: Content-Type: application/json
• If using fetch, don't forget to handle the response: res.json()
• For server-side applications, CORS shouldn't be an issue

Yes! The API supports CORS and can be called from any client that can make HTTP POST requests. Browser extensions, mobile apps, and server-side applications are all supported.

Yes, this API is completely free and open source. However, please use it responsibly and respect rate limits to ensure it remains available for everyone.

The API fetches data directly from Roblox's official APIs, so the data is as accurate as what Roblox provides. However, there may be slight delays (a few seconds to minutes) for very recent changes like username updates or group membership changes.

Yes, but keep in mind:

• This is a community-maintained service (not officially supported by Roblox)
• Implement proper error handling and fallbacks
• Cache responses when possible to reduce load
• Monitor the status page for outages

Please open an issue on the GitHub repository. Include:

• Description of the issue
• Steps to reproduce
• Expected vs actual behavior
• Your request payload (without sensitive data)