Account8

AccountPlan6

Aggregation5

Auth1

BalanceChargeSchedule6

Balances8

BalanceTransactionSchedule6

Bill20

BillConfig2

BillGroupingKey5

BillJob5

Charge5

Commitments6

CompoundAggregation5

Contract6

Counter5

CounterAdjustments5

CounterPricing5

CreditReason5

Credits5

Currency5

CustomField2

DataExplorer20

DataExplorerV26

DebitReason5

Debits5

Events4

ExportAdHoc1

ExportDestination6

ExportJob2

ExportSchedule5

External Mapping8

ExternalMappings2

IntegrationConfigs12

IntegrationCredentials5

IntegrationDestinations22

IntegrationRuns7

IntegrationTransformations7

Invitations3

Line Item1

LookupTable5

LookupTableRevision6

LookupTableRevisionData13

Marketplace Integrations1

Measurements6

Meter5

MeterGroup5

Notifications6

OrganizationConfig2

OrgUsers6

PermissionPolicy13

Plan5

PlanGroup5

PlanGroupLink5

PlanTemplate5

Pricing5

Product5

ResourceGroup9

ScheduledEventConfigurations5

ServiceUser6

ServiceUserCredentials6

StatementDefinition5

StatementJob5

Support3

TransactionType5

User1

AccountPlan

Create AccountPlan

Changed on Oct 16, 2026

Create a new AccountPlan or AccountPlanGroup.

This endpoint creates a new AccountPlan or AccountPlanGroup for a specific Account in your Organization. The details of the new AccountPlan or AccountPlanGroup should be supplied in the request body.

Note: You cannot use this call to create both an AccountPlan and AccountPlanGroup for an Account at the same time. If you want to create both for an Account, you must submit two separate calls.

post/organizations/{orgId}/accountplans

Request

Base URL
https://api.m3ter.com
Auth
OAuth 2
Authorization codehttps://m3ter.auth.us-east-1.amazoncognito.com/oauth2/authorize, token URL https://m3ter.auth.us-east-1.amazoncognito.com/oauth2/token
Client credentialsToken URL /oauth/token
TypeScript
https://skmtc.dev/m3ter-com/apis/m3ter-api/docs/organizations/:orgId/accountplans/post.ts
A function with typed inputs. Its response is checked against the schema.

Path parameters

orgIdstring required

The unique identifier (UUID) for your Organization. The Organization represents your company as a direct customer of our service.

Request body

versioninteger

The version number of the entity:

Create entity: Not valid for initial insertion of new entity - do not use for Create. On initial Create, version is set at 1 and listed in the response.
Update Entity: On Update, version is required and must match the existing version because a check is performed to ensure sequential versioning is preserved. Version is incremented by 1 and listed in the response.

customFieldsobject

User defined fields enabling you to attach custom data. The value for a custom field can be either a string or a number.

If customFields can also be defined for this entity at the Organizational level, customField values defined at individual level override values of customFields with the same name defined at Organization level.

See Working with Custom Fields in the m3ter documentation for more information.

accountIdstring required

The unique identifier (UUID) for the Account.

planIdstring

The unique identifier (UUID) of the Plan to be attached to the Account to create an AccountPlan.

Note: Exclusive of the planGroupId request parameter - exactly one of planId or planGroupId must be used per call.

planGroupIdstring

The unique identifier (UUID) of the PlanGroup to be attached to the Account to create an AccountPlanGroup.

Note: Exclusive of the planId request parameter - exactly one of planId or planGroupId must be used per call.

startDatestring date-time required

The start date (in ISO-8601 format) for the AccountPlan or AccountPlanGroup becoming active for the Account.

endDatestring date-time

The end date (in ISO-8601 format) for when the AccountPlan or AccountPlanGroup ceases to be active for the Account. If not specified, the AccountPlan or AccountPlanGroup remains active indefinitely.

codestring

A unique short code for the AccountPlan or AccountPlanGroup.

billEpochstring date

Optional setting to define a billing cycle date, which acts as a reference for when in the applied billing frequency period bills are created:

For example, if you attach a Plan to an Account where the Plan is configured for monthly billing frequency and you've defined the period the Plan will apply to the Account to be from January 1st, 2022 until January 1st, 2023. You then set a billEpoch date of February 15th, 2022. The first Bill will be created for the Account on February 15th, and subsequent Bills created on the 15th of the months following for the remainder of the billing period - March 15th, April 15th, and so on.
If not defined, then the billEpoch date set for the Account will be used instead.
The date is in ISO-8601 format.

contractIdstring

The unique identifier (UUID) for a Contract to which you want to add the Plan or Plan Group being attached to the Account.

childBillingMode'PARENT_SUMMARY' | 'PARENT_BREAKDOWN' | 'CHILD'

If the Account is either a Parent or a Child Account, this specifies the Account hierarchy billing mode. The mode determines how billing will be handled and shown on bills for charges due on the Parent Account, and charges due on Child Accounts:

Parent Breakdown - a separate bill line item per Account. Default setting.
Parent Summary - single bill line item for all Accounts.
Child - the Child Account is billed.

Response

Returns the created AccountPlan or AccountPlanGroup

idstring required

The UUID of the entity.

versioninteger

The version number:

Create: On initial Create to insert a new entity, the version is set at 1 in the response.
Update: On successful Update, the version is incremented by 1 in the response.

customFieldsobject

User defined fields enabling you to attach custom data. The value for a custom field can be either a string or a number.

If customFields can also be defined for this entity at the Organizational level,customField values defined at individual level override values of customFields with the same name defined at Organization level.

See Working with Custom Fields in the m3ter documentation for more information.

accountIdstring

The unique identifier (UUID) for the Account to which the AccountPlan or AccounPlanGroup is attached.

productIdstring

The unique identifier (UUID) for the Product associated with the AccountPlan.

Note: Not present in response for AccountPlanGroup - Plan Groups can contain multiple Plans belonging to different Products.

planIdstring

The unique identifier (UUID) of the Plan that has been attached to the Account to create the AccountPlan.

planGroupIdstring

The unique identifier (UUID) of the Plan Group that has been attached to the Account to create the AccountPlanGroup.

startDatestring date-time

The start date (in ISO-8601 format) for the when the AccountPlan or AccountPlanGroup starts to be active for the Account.

endDatestring date-time

codestring

The unique short code of the AccountPlan or AccountPlanGroup.

billEpochstring date

The initial date for creating the first bill against the Account for charges due under the AccountPlan or AccountPlanGroup. All subsequent bill creation dates are calculated from this date. If left empty, the first bill date definedfor the Account is used. The date is in ISO-8601 format.

contractIdstring

The unique identifier (UUID) for the Contract to which the Plan or Plan Group attached to the Account has been added.

childBillingMode'PARENT_SUMMARY' | 'PARENT_BREAKDOWN' | 'CHILD'

Parent Breakdown - a separate bill line item per Account. Default setting.
Parent Summary - single bill line item for all Accounts.
Child - the Child Account is billed.

dtCreatedstring date-time

The date and time (in ISO 8601 format) when the AccountPlan or AccountPlanGroup was first created.

dtLastModifiedstring date-time

The date and time (in ISO 8601 format) when the AccountPlan or AccountPlanGroup was last modified.

createdBystring

The unique identifier (UUID) for the user who created the AccountPlan or AccountPlanGroup.

lastModifiedBystring

The unique identifier (UUID) for the user who last modified the AccountPlan or AccountPlanGroup.

Changes

Oct 16, 202685c514abc692 Revision changes
- breaking
  added subschema #1 subschema #2 to the ///// request property allOf list
- breaking
  the //// request property type changed from no type to object
- breaking
  the request property type changed from no type to object
- breaking
  the //// response's property type changed from no type to object for status
- breaking
  the response's property type changed from no type to object for status
Aug 1, 20259f9e5f3dbde7 Revision changes
- breaking
  the response property //////// became optional for the status
- breaking
  the response property //// became optional for the status

Operation history (3 revisions)