The individual price list is available in the API as a sub-record of the price list group. However, it behaves differently from regular records — it's a computed view, not stored records, which determines what you can and can't do with it.
Filtering
You cannot filter by the price list tree. An alternative is to filter by price level or product group:
GET /c/{firma}/cenikova-skupina/4/individualni-cenik/(cenHlad==10).xml
GET /c/{firma}/cenikova-skupina/4/individualni-cenik/(skupZboz==13).xml
Both fields are valid — a non-existent field would result in a Vlastnost '…' neexistuje error.
Level of detail for price levels
You can list the properties of a price level using nested notation, but nothing will be returned:
GET /c/{firma}/…/individualni-cenik.xml?detail=custom:cenHlad(id,kod) → <cenHlad></cenHlad>
This is because the individual price list does not carry the ID information from the price levels record — it only works with the code. If you need more than what detail=summary returns, use detail=full and retrieve the additional data with a separate query on the cenova-uroven record.
ℹ️ Individual price list records have id equal to -1 and a composite identifier in the idString field (for example 1-0-0-0-0). This means these are not standalone records that could be addressed or written to — the record is read-only.