A TariffBookingCredit represents an amount of credit linked to a plan (Tariff). When a customer’s contract on that plan renews, the credit is automatically released as a CoworkerBookingCredit on the customer’s account.Credit can be configured for two primary uses:
Bookings — set CaneBeUsedForBookings to allow the credit to pay for bookings. Use ElegibleResourceTypes to restrict the credit to specific resource types; if left empty the credit is valid for all resource types.
Events — set CaneBeUsedForEvents to allow the credit to pay for event sign-ups. Use EventCategories to restrict to specific event categories; if left empty the credit is valid for all events.
Setting IsUniversalCredit enables the credit for products, time passes, and other charges. Use ElegibleProducts, ElegiblePasses, and AppliesToCharges to restrict which products or passes the credit is valid for. If all restriction lists are empty the universal credit applies to all products, passes and charges.Use ServiceRenewalTime to control how often the credit is renewed (e.g. weekly, monthly).
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 TariffBookingCredit-List role.
Filter by whether this is a universal credit applicable to products, time passes and other charges. Restrict with ElegibleProducts, ElegiblePasses and AppliesToCharges; if all are empty the credit applies to all products, passes and charges.
The list of TariffBookingCredit records matching the query. See the Get one TariffBookingCredit endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each TariffBookingCredit. The following fields are not included in the Records[] response: CaneBeUsedForBookings, CaneBeUsedForEvents, IsUniversalCredit, AppliesToCharges.To get all fields, fetch the full record using the Get one TariffBookingCredit 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.