Sounds like the app builder is only recognizing your API’s GET methods because they’re typically used for retrieving data, while POST methods require additional configuration such as defining request bodies, headers, or authentication before they appear as options—so you may need to explicitly set those in your API definition or connector setup. Think of it like The Spike Volleyball Story Characters, where each player has unique roles and abilities, but you only see their true potential once you configure their stats properly; in the same way, your POST methods will show up once the system knows how to handle their required inputs.

Hi there, in most app builders, when connecting to a WebAPI, the interface often auto-detects available methods but only displays GET methods by default unless the POST methods are explicitly defined with proper metadata (like in OpenAPI/Swagger) or enabled in the configuration; you might need to check your API definition to ensure POST endpoints are documented correctly, verify that the app builder supports POST calls in that section, and manually add them if needed—similar to how sim registration tm processes require both form submission (POST) and data retrieval (GET) steps to be fully functional.