Purpose
Returns a single product from the Clopos catalog, along with related data specific to its type (variants, modifiers, recipe, timer settings, etc.). Use thewith parameters to fetch only the sub-resources you need.
HTTP Request
Path Parameters
string
required
The product ID (integer or UUID).
Query Parameters
string
Related data selector. Example:
taxes, unit, modifications, modificator_groups, recipe, packages, media, tags, setting. You can include multiple with parameters.
Supported with values may vary based on your backend version.
Request Example
Response
200 OK — Product found
404 Not Found — Product does not exist
Field Reference
See the full breakdown of theProduct object and nested structures such as modifications and modificator_groups on the List Products page.
Product Object
Notes
- If the
idparameter is in the wrong format, the backend returns a400error; validate it on the client side. - Since
withparameters are evaluated sequentially, avoid using the same key more than once. - Type-specific heavy relationships (for example, large
recipeormodificator_groups) can produce large responses; request only what you need. - Some fields may be empty or null depending on the product type; use the
typefield to drive conditional rendering on the client. - For TIMER products, the
setting.pricesarray represents additional fees applied after a certain duration. - For INGREDIENT products, the
packagesfield shows the package sizes used in stock entries; if not applicable, it is an empty array.