1. REST API Reference for Billing Care
  2. Tasks
  3. Accounts

Add a Bundle to an Account

post

/accounts/{id}/bundle

Adds a bundle to an existing service or account.

Request

Path Parameters
Supported Media Types
Request Body - application/xml ()
Root Schema : schema
Type: object
Show Source
Nested Schema : customizedChargeOffers
Type: array
The list of customized charge offers in the bundle.
Show Source
Nested Schema : customizedDiscountOffers
Type: array
The list of customized discount offers.
Show Source
Nested Schema : extension
Type: object
The extended attributes.
Nested Schema : Notes
Type: object
Show Source
Nested Schema : CustomizedChargeOffers
Type: object
The list of customized charge offers in the bundle.
Show Source
Nested Schema : ResourceRef
Type: object
Show Source
Nested Schema : EndingType
Type: object
Show Source
Nested Schema : StartingType
Type: object
Show Source
  • The starting type mode for a product. Can be one of the following:
    • immediately: The start date is set to today. This mode can be used with the purchaseStart, cycleStart, and usageStart parameters.
    • absolute: The start date is a calendar date. This mode can be used with the purchaseStart, cycleStart, and usageStart parameters.
    • relativeToPurchase: The start date is relative to the purchase date, such as a specified number of billing cycles, months, days, hours, minutes, or seconds after activation. This mode can be used with the cycleStart and usageStart parameters.
    • firstUsage: The start day is the day of the first recorded usage.
  • The date and time the cycle starts.
  • RelativeSettings
Nested Schema : overriddenCharges
Type: array
The overridden charges.
Show Source
Nested Schema : tieOfferRefs
Type: array
Show Source
Nested Schema : RelativeSettings
Type: object
Show Source
Nested Schema : overriddenCharges
Type: object
The overridden charges.
Show Source
Nested Schema : charges
Type: array
The charge details.
Show Source
Nested Schema : Charges
Type: object
The charge details.
Show Source
Nested Schema : charge
Type: array
The charges.
Show Source
Nested Schema : Charge
Type: object
The charges.
Show Source
Nested Schema : CustomizedDiscountOffers
Type: object
The list of customized discount offers.
Show Source
Nested Schema : overriddenCharges
Type: array
The overridden charges.
Show Source
Nested Schema : tieOfferRefs
Type: array
Show Source
Nested Schema : comments
Type: array
The list of comments associated with the note.
Show Source
Nested Schema : extension
Type: object
The extended attributes.
Nested Schema : Comments
Type: object
The list of comments associated with the note.
Show Source
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : customizedChargeOffers
Type: array
The list of customized charge offers in the bundle.
Show Source
Nested Schema : customizedDiscountOffers
Type: array
The list of customized discount offers.
Show Source
Nested Schema : extension
Type: object
The extended attributes.
Nested Schema : Notes
Type: object
Show Source
Nested Schema : CustomizedChargeOffers
Type: object
The list of customized charge offers in the bundle.
Show Source
Nested Schema : ResourceRef
Type: object
Show Source
Nested Schema : EndingType
Type: object
Show Source
Nested Schema : StartingType
Type: object
Show Source
  • The starting type mode for a product. Can be one of the following:
    • immediately: The start date is set to today. This mode can be used with the purchaseStart, cycleStart, and usageStart parameters.
    • absolute: The start date is a calendar date. This mode can be used with the purchaseStart, cycleStart, and usageStart parameters.
    • relativeToPurchase: The start date is relative to the purchase date, such as a specified number of billing cycles, months, days, hours, minutes, or seconds after activation. This mode can be used with the cycleStart and usageStart parameters.
    • firstUsage: The start day is the day of the first recorded usage.
  • The date and time the cycle starts.
  • RelativeSettings
Nested Schema : overriddenCharges
Type: array
The overridden charges.
Show Source
Nested Schema : tieOfferRefs
Type: array
Show Source
Nested Schema : RelativeSettings
Type: object
Show Source
Nested Schema : overriddenCharges
Type: object
The overridden charges.
Show Source
Nested Schema : charges
Type: array
The charge details.
Show Source
Nested Schema : Charges
Type: object
The charge details.
Show Source
Nested Schema : charge
Type: array
The charges.
Show Source
Nested Schema : Charge
Type: object
The charges.
Show Source
Nested Schema : CustomizedDiscountOffers
Type: object
The list of customized discount offers.
Show Source
Nested Schema : overriddenCharges
Type: array
The overridden charges.
Show Source
Nested Schema : tieOfferRefs
Type: array
Show Source
Nested Schema : comments
Type: array
The list of comments associated with the note.
Show Source
Nested Schema : extension
Type: object
The extended attributes.
Nested Schema : Comments
Type: object
The list of comments associated with the note.
Show Source
Back to Top

Response

204 Response

The bundle was added to the account successfully.

400 Response

The request isn't valid.

500 Response

An internal server error occurred.
Back to Top

Examples

Example 1: Adding a Bundle to an Account

This example shows how to add a bundle to a specified service by submitting a POST request on the REST resource using cURL. For more information about cURL, see "Use cURL".

cURL Command

curl -X POST 'http://hostname:port/bcws/webresources/v1.0/accounts/0.0.0.1+-service-email+265928/bundle' -H 'content-type: application/json' -d @addBundle.json

where:

  • hostname is the URL for the Billing Care REST server.
  • port is the port for the Billing Care REST server.
  • version is the version of the API you're using, such as v1.0.
  • addBundle.json is the JSON file that specifies the bundle to add.

You could provide an account ID in the path instead of a service ID to add a bundle at the account level.

Example of Request Body

This example shows the contents of the addBundle.json file sent as the request body. 

{
   "id": "0.0.0.1+-deal+171251",
   "name": "Deal with cycle forward product",
   "customizedChargeOffers": [
      {
         "name": "Product with cycle forward event",
         "description": "Product with cycle forward charge more than 1000",
         "baseChargeOfferRef": {
            "id": "0.0.0.1+-product+168179",
            "uri": null
         }
      }
   ],
   "customizedDiscountOffers": [],
   "effective": null
}

Example of Response Body

If successful, the response code 204 is returned with no response body.

Example 2: Overriding a Product During Purchase

This example shows how to purchase a bundle and override its monthly recurring charge by submitting a POST request on the REST resource using cURL. For more information about cURL, see "Use cURL".

cURL Command

curl -X POST 'http://hostname:port/bcws/webresources/v1.0/accounts/0.0.0.1+-service-email+265928/bundle' -H 'content-type: application/json' -d @addBundle.json

where:

  • hostname is the URL for the Billing Care REST server.
  • port is the port for the Billing Care REST server.
  • addBundle.json is the JSON file that specifies the bundle to add.

You could provide an account ID in the path instead of a service ID to add a bundle at the account level.

Example of Request Body

This example shows the contents of the addBundle.json file sent as the request body. PriceTagName is the name of the price tag associated with the override charge. 

{
   "id": "0.0.0.1+-deal+40683",
   "name": "Deal with cycle forward product",
   "customizedChargeOffers": [
      "overriddenCharges": [
         {
            "event": "/event/billing/product/fee/cycle/cycle_forward_monthly",
            "charges": [
               {
                  "startDate": "2025-11-25",
                  "charge": [
                     {
                        "type": "amount",
                        "amount": 25,
                        "priceTag": "PriceTagName"
                     }
                  ]
               }
            ]
         }
      ]
   ],
   "customizedDiscountOffers": [],
   "effective": null
}

Example of Response Body

If successful, the response code 204 is returned with no response body.

Back to Top