ComposioHQ/composio · error · ValidationError

proxy_execute: endpoint is required

Error message

proxy_execute: endpoint is required

What it means

Client-side guard in proxy_execute that fires when endpoint is falsy. Checked after toolkit, so a valid toolkit with a missing endpoint hits this one. No API call is made — the error is purely local validation matching the TS schema.

Source

Thrown at python/composio/core/models/session_context.py:56

    client: HttpClient,
    session_id: str,
    *,
    toolkit: str,
    endpoint: str,
    method: t.Literal["GET", "POST", "PUT", "DELETE", "PATCH"],
    body: t.Any = None,
    parameters: t.Optional[t.List[t.Dict[str, t.Any]]] = None,
) -> ToolRouterSessionProxyExecuteResponse:
    """Shared proxy execute implementation used by SessionContextImpl and ToolRouterSession.

    Projects the generated client's response model onto the SDK's own shape so
    the public return type does not move when the client is regenerated.
    """
    # Client-side validation (matches TS SessionProxyExecuteParamsSchema)
    if not toolkit:
        raise ValidationError("proxy_execute: toolkit is required")
    if not endpoint:
        raise ValidationError("proxy_execute: endpoint is required")
    if method not in _VALID_METHODS:
        raise ValidationError(
            f"proxy_execute: method must be one of {sorted(_VALID_METHODS)}, got {method!r}"
        )

    # Transform and validate parameters
    api_params: t.List[Parameter] = []
    if parameters:
        for i, p in enumerate(parameters):
            if not isinstance(p, dict) or "name" not in p or "value" not in p:
                raise ValidationError(
                    f"proxy_execute: parameters[{i}] must be a dict with 'name' and 'value' keys"
                )
            param_type = p.get("in", p.get("type", "header"))
            if param_type not in _VALID_PARAM_TYPES:
                raise ValidationError(
                    f"proxy_execute: parameters[{i}].type must be 'header' or 'query', "
                    f"got {param_type!r}"

View on GitHub (pinned to 64b1b85502)

Solutions

1. Supply a concrete endpoint path like '/user' or '/repos/{owner}/{repo}'
2. Validate the endpoint variable is non-empty before the call

Example fix

# before
session.proxy_execute(toolkit='github', endpoint=ep)  # ep == ''

# after
if not ep:
    raise ValueError('endpoint must be set')
session.proxy_execute(toolkit='github', endpoint=ep)

if not endpoint:
    raise ValueError('endpoint is required')

def has_endpoint(p: dict) -> bool:
    return bool(p.get('endpoint'))

When it happens

Trigger: Calling session.proxy_execute(toolkit='github') with endpoint=None or '' — commonly when the endpoint is interpolated from a variable or config that wasn't populated.

Common situations: Endpoint paths built from templates where the placeholder substitution produced an empty string.

Understand the failure class

Background: Missing required parameter errors: what 'X is required' and 'the required X param is missing' mean, and how to fix them — this error's family across 27 libraries.

Related errors

• proxy_execute: toolkit is required
• proxy_execute: method must be one of {sorted(_VALID_METHODS)
• proxy_execute: parameters[{i}] must be a dict with 'name' an
• proxy_execute: parameters[{i}].type must be 'header' or 'que
• Invalid proxy execute parameters

AI-assisted analysis of ComposioHQ/composio@64b1b85502 (2026-08-28). Data as JSON: /api/errors/8d0779b734739cb9. Report an issue: GitHub.