BokaMera.API.Host

UpdateVossSubscriptionScheduledChange

**Requires Authentication**
Requires any of the roles:	bookingsupplier-administrator-write, superadmin

The following routes are available for this service:
PUT	/voss/subscriptions/{SubscriptionId}/scheduledChanges/{Id}	Update voss subscription scheduled change	Update a pending subscription scheduled change in the VOSS System. Already executed scheduled changes cannot be updated.

**UpdateVossSubscriptionScheduledChange** Parameters:
Name	Parameter	Data Type	Required	Description
SubscriptionId	path	Guid	Yes	The subscription id
Id	path	Guid	Yes	The subscription scheduled change id
Type	body	TypeEnum	Yes	Controls when the scheduled change will be executed: <br />AtSubscriptionBillingPeriodEnd - after the currently latest subscription billing period ends <br />AtBindingPeriodEnd - after the currently latest subscription binding period ends
VersionId	body	Guid?	No	Optional package version id; if omitted the current version of the subscription package is used
PackageId	body	Guid?	No	The id of a package which will be active after the scheduled change is executed; if provided the tier id and plan id have to be provided as well
TierId	body	Guid?	No	The id of a tier which will be active after the scheduled change is executed; can be omitted if PlanId is provided instead
PlanId	body	Guid?	No	The id of a plan which will be active after the scheduled change is executed; can be omitted if TierId is provided instead
PeriodIterationCount	body	int?	No	How many periods (counting from the latest period) must pass before the scheduled change is executed; if omitted the change is executed on the latest period end

**TypeEnum** Enum:
AtSubscriptionBillingPeriodEnd
AtBindingPeriodEnd

**SubscriptionScheduledChangeResult** Parameters:
Name	Parameter	Data Type	Required
Type	form	TypeEnum	No
Status	form	StatusEnum	No
Id	form	Guid	No
Package	form	SubscriptionScheduledChangePackageResult	Yes
Tier	form	SubscriptionScheduledChangeTierResult	Yes
Plan	form	SubscriptionScheduledChangePlanResult	Yes
ScheduledDate	form	DateTime	No
SalesInformation	form	SubscriptionScheduledChangeSalesInformationResult	Yes

**StatusEnum** Enum:
Active
Terminated

**SubscriptionScheduledChangePackageResult** Parameters:
Name	Parameter	Data Type	Required
Id	form	Guid	No
VersionId	form	Guid	No
Name	form	string	Yes

**SubscriptionScheduledChangeTierResult** Parameters:
Name	Parameter	Data Type	Required	Description
Id	form	Guid	No
Name	form	string	Yes

**SubscriptionScheduledChangePlanResult** Parameters:
Name	Parameter	Data Type	Required	Description
Id	form	Guid	No
Name	form	string	Yes

**SubscriptionScheduledChangeSalesInformationResult** Parameters:
Name	Parameter	Data Type	Required	Description
SalesPersonId	form	string	Yes
SalesDepartmentId	form	string	Yes

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

PUT /voss/subscriptions/{SubscriptionId}/scheduledChanges/{Id} HTTP/1.1 
Host: testapi.bokamera.se 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"Type":"AtSubscriptionBillingPeriodEnd","VersionId":"00000000-0000-0000-0000-000000000000","PackageId":"00000000-0000-0000-0000-000000000000","TierId":"00000000-0000-0000-0000-000000000000","PlanId":"00000000-0000-0000-0000-000000000000","PeriodIterationCount":0}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"type":"AtSubscriptionBillingPeriodEnd","status":"Pending"}