A: REST Express is a Unity editor extension that converts Postman collections into Unity-ready API clients. It allows you to test API endpoints directly in the Unity Editor and generate clean, maintainable C# code.

A: REST Express supports Unity 2020.3 LTS and later versions. It's regularly tested with the latest LTS releases.

A: REST Express is available on the Unity Asset Store. Check our store page for pricing details.

A: Yes! REST Express generates both async and coroutine versions of your API methods. You can choose which style to use based on your needs.

A: Yes, REST Express fully supports file uploads through multipart/form-data requests. See our Examples for implementation details.

A: Absolutely! REST Express offers extensive customization options through:

• Custom templates
• Naming conventions
• Type generation rules
• Base classes See our Code Generation Guide for details.

A: REST Express supports various authentication methods:

• Bearer tokens
• API keys
• Custom headers
• OAuth flows Implement the IAuthProvider interface for custom authentication.

A: Yes, REST Express works with WebGL builds. However, consider:

• CORS policies (ensure your server includes appropriate CORS headers)
• SSL/HTTPS requirements
• Browser security restrictions

A: Yes, REST Express handles HTTPS connections and certificates. For development environments with self-signed certificates, use the provided certificate handler.

A: Best practices include:

1. Group related endpoints in folders
2. Use consistent naming conventions
3. Document request/response examples
4. Utilize variables for common values See Best Practices for detailed guidance.

A: Yes, REST Express supports Postman environment variables. They can be:

• Imported with collections
• Overridden locally
• Used in generated code

A: REST Express provides several error handling options:

1. Try-catch blocks with ApiException
2. Error callbacks in coroutines
3. Global error handlers See Error Handling examples.

A: Common reasons include:

1. Invalid JSON format
2. Unsupported Postman version
3. Missing required fields See Troubleshooting for solutions.

A: Check these common issues:

1. Missing dependencies
2. Incorrect Unity version
3. Invalid type references See Compilation Errors.

A: To report bugs:

1. Check existing issues
2. Provide reproduction steps
3. Include error messages
4. Share collection sample (if possible)

A: We regularly update REST Express with:

• Bug fixes
• New features
• Unity compatibility updates
• Performance improvements

A: Support options include:

1. Documentation
2. Issue tracker
3. Email support: [email protected]
4. Unity Asset Store comments

A: Yes! We welcome feature requests through:

1. GitHub issues
2. Email
3. Asset Store reviews

A: We recommend:

1. Group related endpoints
2. Use meaningful names
3. Document responses
4. Handle errors consistently See Best Practices for more.

A: Choose based on your needs:

• Async: Modern C# development, better error handling
• Coroutines: Unity-specific workflows, simpler integration

A: Best practices include:

1. Keep collections updated
2. Use version control
3. Document customizations
4. Follow naming conventions