php-calling-endpointslisted

# Calling endpoints on an APIMatic PHP SDK Operations are methods on a **controller you get from the client** — you never construct one: ```php $controller = $client->get{Group}{Postfix}(); // e.g. getShipmentsController() — or getShipmentsApi() // whichever suffix this SDK uses $result = $controller->{operation}(/* … */); ``` The client memoizes each controller, so calling the accessor repeatedly is free. Controllers live in `src/{Postfix}s/` — the directory and namespace are the *pluralised* class postfix, which is named per SDK, so `src/Controllers/` when the postfix is `Controller`, `src/Apis/` when it is `Api` — and each extends a shared `Base{Postfix}` (`BaseController`, `BaseApi`, …). Find the folder with `ls src/`: it is the one that is not `Models`/`Http`/`Utils`/`Authentication`/ `Exceptions`/`Logging`/`Proxy`. **Read the accessor names from `src/{Client}.php`.** Operation names follow no fixed verb/resource pattern; take the real name from the source or from `doc/controllers/`. ## Two parameter conventions — check which one the method uses Neither form is the norm, and neither follows from the parameter count alone. An operation with **more than one** non-constant parameter is collapsed into a single `array $options` in SDKs built to collapse them, and in any SDK where that one endpoint collects its parameters, and stays positional otherwise; an operation declaring **one** parameter is positional either way. Bo