ContributionsMost RecentMost LikesSolutionsRe: use single request field for string as well as file Hi pb9034, Can you please clarify how I can help you and what you want to achieve? Having an example, description, or screenshots would be helpful. Re: UI issue in API Hub Portal on narrow windows. Hi ag-stoneeagle, Thank you for raising this concern with us! Indeed I was able to reproduce this issue. I'm going to share this concern with our product team to raise an issue for this. In the future, if you would like to be able to track the progress, you can create a case with our Support team - https://support.smartbear.com/api-hub/message/ Re: candlesticks 404 (Not Found) via proxy Hi itqandas, Thanks for reaching out. I’m not entirely sure how this issue is related to API Hub. Could you please provide more details about where you’re seeing the problem within API Hub? This will help me better understand the situation and assist you more effectively. In case you're using an external API, you can reach out to the provider to provide you with a possible authorization or authentication method. Re: LoadNinja with 10k plan doesn't support 10k users Hi ArunBabu, This looks like something that shoyuld be addressed by our Support team. Please create a ticket with a test number or details, so our Support team can identify the case and find the possible reason for failure. https://support.smartbear.com/loadninja/message/ Re: It does not seem like setting a header in a response as required makes any difference Understood. We will consider your example for discussion about further improvements to the editor and the visual representation of responses. We appreciate you bringing this to our attention, as it helps us better understand the needs of users using our product! Re: It does not seem like setting a header in a response as required makes any difference After consulting with our product team, we found that this use case may not have been considered in the past. We're aware that SwaggerUI might also act as a documentation tool for server developers. This seems like a good idea for a feature request. Thank you for bringing this to our attention. Re: It does not seem like setting a header in a response as required makes any difference Hi Henrik, yes, you're correct. The red asterix is displayed for headers in requests, as this field is required by the user of the API to fill in when sending a request. Re: It does not seem like setting a header in a response as required makes any difference Hello HenrikHL, Required fields are visually marked with a red asterisk (*) in the Query Parameters section to ensure users provide necessary inputs during requests. However, for headers, even though they can be defined as required (required: true), Swagger UI does not display a red asterisk or similar indicator for them. This is by design and not an issue with the tool. The required header will still be enforced during validation. Re: Try it out not working - Incorrect cURL with Swagger 2.0 Hello there! The URL is always generated with quotes, there's no way to change it. To add bearer token you can try to modify the securitySchemes section of your OpenAPI document to explicitly define Bearer authentication. You can find more details in OAS documentation below: https://swagger.io/docs/specification/v3_0/authentication/bearer-authentication/ Re: path template expressions is not matched with Parameter Object(s) In OpenAPI 3.1.0, you can still use pathItems under paths, but there are stricter validation rules regarding path parameters. The main change is that path parameters must be explicitly defined within the parameters section of components and referenced in operations, rather than inside pathItems. When you have parameters in the URL, you need to ensure that the path parameters are correctly defined within the pathItem itself or within each operation under the pathItem. The path parameters must be included in the parameters section of the pathItem or the specific operation (e.g., get, post, etc.).