Create Meter
Changed onCreate a new Meter.
When you create a Meter, you can define two types of field for usage data collection and ingest into the platform:
- dataFields to collect raw usage data measures - numeric quantitative data values or non-numeric point data values.
- derivedFields to derive usage data measures that are the result of applying a calculation to dataFields, customFields, or system Timestamp fields.
You can also:
- Create customFields for a Meter, which allows you to attach custom data to the Meter as name/value pairs.
- Create Global Meters, which are not tied to a specific Product and allow you collect to usage data that will form the basis of usage-based pricing across more than one of your Products.
IMPORTANT! - use of PII: The use of any of your end-customers' Personally Identifiable Information (PII) in m3ter is restricted to a few fields on the Account entity. Please ensure that any fields you configure for Meters, such as Data Fields or Derived Fields, do not contain any end-customer PII data. See the Introduction section above for more details.
See also:
Request
- Base URLhttps://api.m3ter.com
- AuthOAuth 2Authorization codehttps://m3ter.auth.us-east-1.amazoncognito.com/oauth2/authorize, token URL https://m3ter.auth.us-east-1.amazoncognito.com/oauth2/tokenClient credentialsToken URL /oauth/token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
UUID of the organization. The Organization represents your company as a direct customer of the m3ter service.
Request body
Response
Return the created Meter
Changes
- breaking
added
subschema #1subschema #2to the/////request propertyallOflist - breaking
the
////request property type changed from no type toobject - breaking
the
request property type changed from no type toobject - breaking
the
///request property type changed from no type toobject - breaking
the
////response's property type changed from no type toobjectfor status - breaking
the
response's property type changed from no type toobjectfor status - breaking
the
///response's property type changed from no type toobjectfor status
- breaking
- breaking
the response property
////////became optional for the status - breaking
the response property
////became optional for the status - warning
the
////request property's maxLength was set to5000
- breaking