Update a Data Export Schedule for the given UUID. Each Schedule can be configured for exporting only one of either Usage or Operational data:
Operational Data Exports.
operationalDataTypes parameter to specify the entities whose operational data you want to include in the export each time the Export Schedule runs.Usage Data Exports.
dimensionFilters parameter to filter the usage data returned for export by adding specific values of non-numeric Dimension data fields on included Meters. Only the data collected for the values you’ve added for the selected Dimension fields will be included in the export.aggregations to apply aggregation methods the usage data returned for export. This restricts the range of usage data returned for export to only the data collected by aggregated fields on selected Meters. Nothing is returned for any non-aggregated fields on Meters. The usage data for Meter fields is returned as the values resulting from applying the selected aggregation method. See the Aggregations for Queries - Options and Consequences for more details.aggregations to the usage returned for export, you can then use the groups parameter to group the data by Account, Dimension, or Time.m3ter supports machine to machine authentication using the clientCredentials OAuth2 flow.
The authorizationCode flow controls access for human users via the m3ter Console application.
UUID of the organization
The UUID of the Schedule to update.
Request representing an operational schedule configuration.
The name of the Data Export Schedule.
1Unique short code of the Data Export Schedule.
1 - 80USAGE, OPERATIONAL A list of the entities whose operational data is included in the data export.
1BILLS, COMMITMENTS, ACCOUNTS, BALANCES, CONTRACTS, ACCOUNT_PLANS, AGGREGATIONS, PLANS, PRICING, PRICING_BANDS, BILL_LINE_ITEMS, METERS, PRODUCTS, COMPOUND_AGGREGATIONS, PLAN_GROUPS, PLAN_GROUP_LINKS, PLAN_TEMPLATES, BALANCE_TRANSACTIONS, TRANSACTION_TYPES, CHARGES The version number of the entity:
The Export Destination ids.
Note: When creating or updating an Export Schedule, you can:
The type of interval used for when Data Exports are run for the Schedule. Possible values are: HOURLY or DAILY or MINUTE.
Used in conjunction with the period parameter to define the frequency of Data Exports in hours, days, or minutes.
Defines the Schedule frequency for the Data Export to run in Hours, Days, or Minutes. Used in conjunction with the scheduleType parameter:
x >= 1Offset indicating starting point of the export
x >= 1CSV, JSONL Returns the updated Export Schedule
Response representing an operational data export configuration.
The id of the schedule.
The version number:
The name of the Data Export Schedule.
Unique short code of the Data Export Schedule.
USAGE, OPERATIONAL The Export Destination ids.
The type of interval used for when Data Exports are run for the Schedule.
HOUR, DAY, MINUTE, AD_HOC Defines the Schedule frequency for the Data Export to run in Hours, Days, or Minutes. Used in conjunction with the scheduleType parameter.
Offset indicating starting point of the export within the configured scheduleType. For DAY, offset is in hours. For HOUR, offset is in minutes. Offset is not valid for MINUTE.
A cron expression (https://en.wikipedia.org/wiki/Cron) describing the frequency of the expression. Executions cannot be more frequent than every 15 minutes.
CSV, JSONL The DateTime when the Data Export Schedule was created.
The DateTime when the Schedule was last modified.
The id of the user who created this Schedule.
The id of the user who last modified this Data Export Schedule.
A list of the entities whose operational data is included in the data export.
BILLS, COMMITMENTS, ACCOUNTS, BALANCES, CONTRACTS, ACCOUNT_PLANS, AGGREGATIONS, PLANS, PRICING, PRICING_BANDS, BILL_LINE_ITEMS, METERS, PRODUCTS, COMPOUND_AGGREGATIONS, PLAN_GROUPS, PLAN_GROUP_LINKS, PLAN_TEMPLATES, BALANCE_TRANSACTIONS, TRANSACTION_TYPES, CHARGES