dotnet-calling-endpoints

Operations are async methods grouped under a controller property, called as client.{ApiGroup}.{Operation}(...), or directly on the client if ungrouped. Take the exact operation name and signature from the contract sheet rather than guessing from naming patterns.

Use named arguments, since list operations have many optional parameters in fixed positional order and leading nullable params often lack C# defaults. Named arguments are order-independent and let omitted optionals fall through to null or their defaults.

Return types vary per operation: an object nesting the resource, the resource directly, an IReadOnlyList array, an object nesting an array, or a non-generic Task for empty responses. Check each method's return type to know whether to unwrap or iterate.

Yes, every operation takes a CancellationToken as its last parameter, passed as ct:. Use the per-request cancellation pattern from the configuration-resilience guidance to bound individual calls with timeouts.

Non-2xx responses throw SdkException<TError> rather than being signalled by the return value. Wrap calls in try/catch per the error-handling guidance, or use the optional {Operation}Result variant returning ApiResult<TResponse, TError> when generated.