Test an endpoint connection by making a sample request. Can be used in two modes: (1) Without an ID — all connection fields are required (creation flow). (2) With an ID — fetches the stored connection and applies any provided fields as overrides (update flow). See Endpoint Connections.
API key authorization. Pass your API key in the Authorization header as a Bearer token. Both new (gsk_*) and legacy (gsk-) API keys are accepted, e.g. Authorization: Bearer gsk_... or Authorization: Bearer gsk-....
Optional ID of an existing endpoint connection. When provided, stored connection data is used as base and remaining fields act as overrides.
"id_123"
The endpoint URL to test
"https://api.example.com"
HTTP method (GET, POST, etc.)
Authentication type (NONE, BEARER, API_KEY, BASIC)
Authentication token (for BEARER or API_KEY)
Username (for BASIC auth)
Password (for BASIC auth)
"securePass123!"
Custom headers as key-value pairs
Input template with Jinja2 placeholders
Request timeout in seconds