A Product represents an item that can be sold to customers. Products can be sold via contracts (ContractProduct entity), added to bookings (BookingProduct entity), or purchased directly (CoworkerProduct entity).Products support both one-off sales and recurring charges. Recurring charges can be set to daily, weekly, monthly, or yearly frequencies, or charged every time a contract is invoiced. For invoice-linked recurring charges, prefer using ContractProduct to associate the sale directly with a specific contract rather than relying on the customer’s MainContract.Use AvailableAs to control whether a product can be sold as a one-off purchase, a recurring charge, or both. The SystemProductType field categorises the product (e.g. day pass, credit bundle, booking product, stationery, or other).Products can optionally track stock levels, be restricted to specific pricing plans (tariffs), and be limited to members or contacts only.
This endpoint requires OAuth2 authentication. Include a valid bearer token in the Authorization header.
The authenticated user must be a full unrestricted administrator or have the Product-List role.
The list of Product records matching the query. See the Get one Product endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each Product. The following fields are not included in the Records[] response: DisplayOrder, AvailableAs, OnlyForContacts, OnlyForMembers, InvoiceCoworker.To get all fields, fetch the full record using the Get one Product endpoint.Important for updates: When updating a record via PUT, always retrieve the full record with a GET request first, apply your changes to that complete data, and then send the updated record. Do not use data from a listing response as the base for a PUT request, as missing fields may be unintentionally cleared.