Migrates accounts which are associated to one price plan to another price plan

Migrates accounts which are associated to one price plan to another price plan

POST /migrations/price_plan

Migrates accounts which are associated to one price plan to another price plan

cURL

curl --request POST \
  --url https://api.togai.com/migrations/price_plan \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "sourceId": "pp.1zYnCiM9Bpg.lv25y",
  "sourceVersion": 1,
  "targetId": "pp.2zYnCiM9Bpg.bfeu2",
  "targetVersion": 2,
  "migrationMode": "IMMEDIATE"
}
'

201

{
  "success": true
}

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Payload to update organization setting

Request to migrate all account associations of a price plan to another price plan

sourceId · string · required

Id of source price plan

Maximum string length: 255

sourceVersion · integer<int32> · required

Version of the source price plan

targetId · string · required

Id of target price plan

Maximum string length: 255

targetVersion · integer<int32> · required

Version of the target price plan

migrationMode · enum<string> · required

Available options: IMMEDIATE, IMMEDIATE_IGNORE_OVERRIDE, NEXT_CYCLE, NEXT_CYCLE_IGNORE_OVERRIDE

retainStartOffsets · boolean

If this flag is true, current pricing cycle of the account on the date of association will continue rather than the configurations of the newly associated price plan. Pricing cycle overrides specified using pricePlanDetailsOverride will take precedence over the pricing cycle configurations of the new price plan that the account needs to migrate to. PricingCycleInterval of the existing plan and the new plan must be same for this to work. We'll return a 400 BadRequest otherwise. Examples:

• Ongoing plan (1st Oct to 30th Oct) - {dayOffset: 1, monthOffset: NIL} New association (15th Oct to 15th Nov) of different price plan with retainStartOffsets option true will use the same pricing cycle configuration {dayOffset: 1, monthOffset: NIL} rather than using the pricing cycle configuration of the new price plan that the account needs to migrate to.
• Ongoing plan (1st Oct to 30th Oct) - {dayOffset: 1, monthOffset: NIL} New association (1st Nov to 30th Nov) of different price plan with retainStartOffsets option true will throw a 400 BadRequest as no existing price plan configuration found on date of association

Response

201

application/json

OK

success · boolean · required

Example:

true