Note about limits of swagger try out

RusJaI · Nov 8, 2024 · 47a7be6 · 47a7be6
1 parent fc383d2
commit 47a7be6
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/...-apis/invoke-apis-using-tools/invoke-an-api-using-the-integrated-api-console.md b/...-apis/invoke-apis-using-tools/invoke-an-api-using-the-integrated-api-console.md
@@ -60,6 +60,9 @@ Note the successful response for the API invocation.
 [![API response]({{base_path}}/assets/img/learn/api-response.png)]({{base_path}}/assets/img/learn/api-response.png)
 
 You have now successfully invoked an API using the Open API Console
+
+!!! Note
+    When using the Swagger UI's tryout feature to send large payloads, there's a risk that the interface may hang or not function properly. This is because the Swagger client isn't designed as a production-ready tool for handling substantial requests. For testing large payloads, it's advisable to use alternatives like Curl, or other custom clients. The Swagger tryout is intended mainly for simple testing workloads.
 
 ## Get a test key to invoke an API