Subscription API Changes:
New: For POST and PUT requests for Subscriptions, when “charge_start_date” and “charge_end_date” values for Subscription Plans are provided as null, the values for these fields will also be returned as null in the response body.
For GET requests for Subscriptions, “charge_start_date” and “charge_end_date” values for Subscription Plans are null in the response body if the dates align with the contract term of the subscription.
Note: Date values for Charge Start Date and Charge End Date will continue to be displayed in the Subscription Charge detail modal in the Ordway user interface. If the charge start/end dates are the “Same as Subscription”, the date values will reflect the contract term start and end dates.
Old: For POST and PUT requests for Subscriptions, when “charge_start_date” and “charge_end_date” values for Subscription Plans are provided as null, the value for “charge_start_date” matches the value for “current_term_start_date” and the value for “charge_end_date” matches the value for “current_term_end_date” in the response body.
For GET requests for Subscriptions, “charge_start_date” and “charge_end_date” values for Subscription Plans match the values of “current_term_start_date” and “current_term_end_date” in the response body if the dates align with the contract term of the subscription.
New Response Body (truncated):
{
"plans": [
{
"product_id": "P-00001",
"product_name": "Sample Product",
"plan_id": "PLN-00001",
"plan_name": "Bronze Plan",
"charge_id": "CHG-00001",
"charge_name": "Setup Fee",
"list_price": "100000",
"quantity": 1,
"included_units": 0,
"discount": 0,
"effective_price": "100000",
"type": "One time",
"billing_period": "",
"renewal_increment_percent": 0,
"charge_start_date": “”
"charge_end_date": ""
}
]
}
Comments
0 comments
Please sign in to leave a comment.