BundleLineInput

One checked service of a bundle, in the shape a standalone line is saved in.

The client builds the line as it does for a standalone service: dates, term, billing, quantity and totals. The server ties it to its bundle and converts the totals; it never moves the line's dates. A line that follows the bundle's start date must be sent with that date (and the end date it implies) whenever it moves.

  • Must be one of the bundle's configured services

  • Auto renewal flag

  • Billing end date

  • Billing start date

  • Custom billing frequency

  • Custom duration

  • Custom opt out date

  • Custom service duration

  • Discount amount

  • Equal payments billing frequency

  • Equal payments number of payments

  • Whether the line's start date follows the bundle's services start date. Omitted: true for a new line, unchanged for an existing one

  • The line's id when updating an existing line; omit for a new one

  • Is discount percentage flag

  • Free-text note on the service; null or blank removes it

  • What price_per_unit covers: 2 (one year) for a year; null or 1 (one month) for a month

  • Price per unit in the contract's local currency — negative on a discount or credit line

  • Quantity — fractional allowed, negative for a downsell

  • Scheduled payments for this line

    Properties: 4
  • Service end date

  • Service item name

  • Service item pricing ID

  • Service start date

  • Total amount — negative on a downsell line

  • Total amount in local currency — negative on a downsell line