openapi: 3.0.1 info: title: m3ter Account Debits API description: "If you are using Postman, you can:\n- Use the **Download** button above to download the m3ter Open API spec JSON file and then import this file as the **m3ter API Collection** into your Workspace. See [Importing the m3ter Open API](https://www.m3ter.com/docs/guides/m3ter-apis/getting-started-with-api-calls#importing-the-m3ter-open-api) in our main user Documentation for details.\n- Copy this link: [m3ter-Template API Collection](https://www.datocms-assets.com/78893/1672846767-m3ter-template-api-collection-postman_collection.json) and use it to import the **m3ter-Template API Collection** into your Workspace. See [Importing the m3ter Template API Collection](https://www.m3ter.com/docs/guides/m3ter-apis/getting-started-with-api-calls#importing-the-m3ter-template-api-collection) in our main user Documentation for details.\n\n---\n\n# Introduction\nThe m3ter platform supports two HTTP-based REST APIs returning JSON encoded responses:\n- The **Ingest API**, which you can use for submitting raw data measurements. *(See the [Submit Measurements](https://www.m3ter.com/docs/api#tag/Measurements/operation/SubmitMeasurements) endpoint in this API Reference.)*\n- The **Config API**, which you can use for configuration and management. *(All other endpoints in this API Reference.)* \n\n## Authentication and Authorization\nOur APIs use an industry-standard authorization protocol known as the OAuth 2.0 specification.\n\nOAuth2 supports several grant types, each designed for a specific use case. m3ter uses the following two grant types:\n - **Authorization Code**: Used for human login access via the m3ter Console.\n - **Client Credentials**: Used for machine-to-machine communication and API access.\n\nComplete the following flow for API access:\n\n1. **Create a Service User and add Permissions**: Log in to the m3ter Console, go to **Settings**, **Access** then **Service Users** tab, and create a Service User. To enable API calls, grant the user **Administrator** permissions. \n \n2. **Generate Access Keys**: In the Console, open the *Overview* page for the Service User by clicking on the name. Generate an **Access Key id** and **Api Secret**. Make sure you copy the **Api Secret** because it is only visible at the time of creation. \n\nSee [Service Authentication](https://www.m3ter.com/docs/guides/authenticating-with-the-platform/service-authentication) for detailed instructions and an example.\n\n3. **Obtain a Bearer Token using Basic Auth**: We implement the OAuth 2.0 Client Credentials Grant authentication flow for Service User Authentication. Submit a request to the m3ter OAuth Client Credentials authentication flow, using your concatenated **Access Key id** and **Api Secret** to obtain a Bearer Token for your Service User. *See examples below.* \n \n4. **Bearer Token Usage**: Use the HTTP 'Authorization' header with the bearer token to authorise all subsequent API requests. \n\n> Warning: The Bearer Token is valid for 18,000 seconds or 5 hours. When the token has expired, you must obtain a new one.\n\nBelow are two examples for obtaining a Bearer Token using Basic Auth: the first in cURL and the second as a Python script. \n\n### cURL Example\n1. Open your terminal or command prompt. \n2. Use the following `cURL` command to obtain a Bearer Token:\n\n```bash\ncurl -X POST https://api.m3ter.com/oauth/token \\\n -H 'Content-Type: application/x-www-form-urlencoded' \\\n -u your_access_key_id:your_api_secret \\\n -d 'grant_type=client_credentials'\n```\n\nReplace `your_access_key_id` and `your_api_secret` with your actual **Access Key id** and **Api Secret**.\n\n3. Run the command, and if successful, it will return a JSON response containing the Bearer Token. The response will look like this:\n\n```json\n{\n \"access_token\": \"your_bearer_token\",\n \"token_type\": \"Bearer\",\n \"expires_in\": 18000\n}\n```\n\nYou can then use the Bearer Token *(the value of `\"access_token\"`)* for subsequent API calls to m3ter.\n\n### Python Example\n1. Install the `requests` library if you haven't already:\n\n```bash\npip install requests\n```\n\n2. Use the following Python script to obtain a Bearer Token:\n\n```python\nimport requests\nimport base64\n\n# Replace these with your Access Key id and Api Secret\naccess_key_id = 'your_access_key_id'\napi_secret = 'your_api_secret'\n\n# Encode the Access Key id and Api Secret in base64 format\ncredentials = base64.b64encode(f'{access_key_id}:{api_secret}'.encode('utf-8')).decode('utf-8')\n\n# Set the m3ter token endpoint URL\ntoken_url = 'https://api.m3ter.com/oauth/token'\n\n# Set the headers for the request\nheaders = {\n 'Authorization': f'Basic {credentials}',\n 'Content-Type': 'application/x-www-form-urlencoded'\n}\n\n# Set the payload for the request\npayload = {\n 'grant_type': 'client_credentials'\n}\n\n# Send the request to obtain the Bearer Token\nresponse = requests.post(token_url, headers=headers, data=payload)\n\n# Check if the request was successful\nif response.status_code == 200:\n # Extract the Bearer Token from the response\n bearer_token = response.json()['access_token']\n print(f'Bearer Token: {bearer_token}')\nelse:\n print(f'Error: {response.status_code} - {response.text}')\n```\n\nReplace `your_access_key_id` and `your_api_secret` with your actual **Access Key id** and **Api Secret**. \n\n3. Run the script, and if successful, it will print the Bearer Token. You can then use this Bearer Token for subsequent API calls to m3ter.\n\n## Submitting Personally Identifiable Information (PII)\n**IMPORTANT!** Under the [Data Processing Agreement](https://www.m3ter.com/docs/legal/dpa), the only fields permissible for use in submitting any of your end-customer PII data in m3ter are the ``name``, ``address``, and ``emailAddress`` fields on the **Account** entity - see the details for [Create Account](https://www.m3ter.com/docs/api#operation/PostAccount). See also section 4.2 of the [Terms of Service](https://www.m3ter.com/docs/legal/terms-of-service).\n\n## Rate and Payload Limits\n### Config API Request Rate Limits\nSee [Config API Limits](https://www.m3ter.com/docs/guides/m3ter-apis/config-api-limits).\n\n### Data Explorer API Request Rate Limits\nSee [Data Explorer Request Rate Limits](https://www.m3ter.com/docs/guides/m3ter-apis/config-api-limits#date-explorer-request-rate-limits).\n\n### Ingest API Request Rate and Payload Limits\nSee [Ingest API Limits](https://www.m3ter.com/docs/guides/m3ter-apis/ingest-api-limits) for more information.\n\n## Pagination\n**List Endpoints**\nAPI endpoints that have a List resources request support cursor-based pagination - for example, the `List Accounts` request. These List calls support pagination by taking the two parameters `pageSize` and `nextToken`. \n\nThe response of a List API call is a single page list. If the `nextToken` parameter is not supplied, the first page returned contains the newest objects chronologically. Specify a `nextToken` to retrieve the page of older objects that occur immediately after the last object on the previous page.\n\nUse `pageSize` to limit the list results per page, typically this allows up to a maximum of 100 or 200 per page.\n\n**Search Endpoints**\nAPI endpoints that have a Search resources request support cursor-based pagination - for example, the `Search Accounts` request. These Search calls support pagination by taking the two parameters `pageSize` and `fromDocument`.\n\nThe response of a Search API call is a single page list. If the `fromDocument` parameter is not supplied, the first page returned contains the newest objects chronologically. Specify a `fromDocument` to retrieve the page of older objects that occur immediately after the last object on the previous page.\n\nUse `pageSize` to limit the list results per page, typically this allows up to a maximum of 100 or 200 per page. Default is 10.\n\n## API Quick Start\nSee [Getting Started with API Calls](https://www.m3ter.com/docs/guides/m3ter-apis/getting-started-with-api-calls) for detailed guidance on how to use our API to:\n* Create a Service User and add permissions.\n* Generate access keys for the Service User.\n* Use basic authentication to obtain a Bearer Token.\n\nFor further guidance, also see [Creating and Configuring Service Users](https://www.m3ter.com/docs/guides/organization-and-access-management/managing-users/creating-and-configuring-service-users).\n\n## Other Languages\nIf you want to work with the m3ter REST APIs using other languages such as:\n* Python\n* JavaScript\n* C++\n\nPlease see the [Developer Tools](https://www.m3ter.com/docs/guides/developer-tools) topic in our main documentation for information about available SDKs.\n\n\n# Authentication\n" version: '1.0' x-logo: url: https://console.m3ter.com/m3ter-logo-black.svg servers: - url: https://api.m3ter.com security: - OAuth2: [] tags: - name: Debits description: 'Endpoints for Debit line item related operations such as creation, update, list and delete. These are line items on Bills that are specifically related to Debits. You use the Debit Reasons created for your Organization when you create Debit line items for Bills. See the [DebitReason](https://www.m3ter.com/docs/api#tag/DebitReason) section for calls you can use to create and manage Debit Reasons for your Organization. ' paths: /organizations/{orgId}/bills/{billId}/debitlineitems/{id}: get: tags: - Debits summary: Retrieve Debit Line Item description: Retrieve the Debit line item with the given UUID. operationId: GetDebitLineItem parameters: - name: orgId in: path description: UUID of the Organization. The Organization represents your company as a direct customer of the m3ter service. required: true style: simple explode: false schema: type: string deprecated: true x-stainless-deprecation-message: the org id should be set at the client level instead - name: billId in: path description: UUID of the bill. required: true style: simple explode: false schema: type: string - name: id in: path description: The UUID of the debit line item to retrieve. required: true style: simple explode: false schema: type: string responses: '200': description: Returns the debit line item content: application/json: schema: $ref: '#/components/schemas/DebitLineItemResponse' 4XX: $ref: '#/components/responses/Error' 5XX: $ref: '#/components/responses/Error' put: tags: - Debits summary: Update Debit Line Item description: Update the Debit line item with the given UUID. operationId: PutDebitLineItem parameters: - name: orgId in: path description: UUID of the Organization. The Organization represents your company as a direct customer of the m3ter service. required: true style: simple explode: false schema: type: string deprecated: true x-stainless-deprecation-message: the org id should be set at the client level instead - name: billId in: path description: UUID of the bill. required: true style: simple explode: false schema: type: string - name: id in: path description: The UUID of the debit line item to update. required: true style: simple explode: false schema: type: string requestBody: description: '' content: application/json: schema: $ref: '#/components/schemas/DebitLineItemRequest' required: true responses: '200': description: Returns the updated debit line item content: application/json: schema: $ref: '#/components/schemas/DebitLineItemResponse' 4XX: $ref: '#/components/responses/Error' 5XX: $ref: '#/components/responses/Error' delete: tags: - Debits summary: Delete Debit Line Item description: Delete the Debit line item with the given UUID. operationId: DeleteDebitLineItem parameters: - name: orgId in: path description: UUID of the Organization. The Organization represents your company as a direct customer of the m3ter service. required: true style: simple explode: false schema: type: string deprecated: true x-stainless-deprecation-message: the org id should be set at the client level instead - name: billId in: path description: UUID of the bill. required: true style: simple explode: false schema: type: string - name: id in: path description: UUID of the debit line item. required: true style: simple explode: false schema: type: string responses: '200': description: Returns the deleted debit line item content: application/json: schema: $ref: '#/components/schemas/DebitLineItemResponse' 4XX: $ref: '#/components/responses/Error' 5XX: $ref: '#/components/responses/Error' /organizations/{orgId}/bills/{billId}/debitlineitems: get: tags: - Debits summary: List Debit Line Items description: List the Debit line items for the given bill. operationId: ListDebitLineItems parameters: - name: orgId in: path description: UUID of the Organization. The Organization represents your company as a direct customer of the m3ter service. required: true style: simple explode: false schema: type: string deprecated: true x-stainless-deprecation-message: the org id should be set at the client level instead - name: billId in: path description: UUID of the bill. required: true style: simple explode: false schema: type: string - name: pageSize in: query description: Number of line items to retrieve per page. required: false allowEmptyValue: true style: form explode: true schema: maximum: 100 minimum: 1 type: integer format: int32 - name: nextToken in: query description: '`nextToken` for multi page retrievals.' required: false allowEmptyValue: true style: form explode: true schema: type: string responses: '200': description: Returns a list of debit line items content: application/json: schema: $ref: '#/components/schemas/PaginatedDebitLineItemResponseData' 4XX: $ref: '#/components/responses/Error' 5XX: $ref: '#/components/responses/Error' post: tags: - Debits summary: Create Debit Line Item description: "Create a new Debit line item for the given bill.\n \nWhen creating Debit line items for Bills, use the Debit Reasons created for your Organization. See [DebitReason](https://www.m3ter.com/docs/api#tag/DebitReason)." operationId: PostDebitLineItem parameters: - name: orgId in: path description: 'UUID of the Organization. The Organization represents your company as a direct customer of the m3ter service. ' required: true style: simple explode: false schema: type: string deprecated: true x-stainless-deprecation-message: the org id should be set at the client level instead - name: billId in: path description: UUID of the bill. required: true style: simple explode: false schema: type: string requestBody: description: '' content: application/json: schema: $ref: '#/components/schemas/DebitLineItemRequest' required: true responses: '200': description: Returns the new debit line item content: application/json: schema: $ref: '#/components/schemas/DebitLineItemResponse' 4XX: $ref: '#/components/responses/Error' 5XX: $ref: '#/components/responses/Error' components: schemas: MemoLineItemRequest: type: object description: '' allOf: - $ref: '#/components/schemas/AbstractRequest' - required: - accountingProductId - amount - description - productId - referencedBillId - referencedLineItemId - servicePeriodEndDate - servicePeriodStartDate properties: reasonId: type: string description: The UUID of the line item reason. lineItemType: description: '' $ref: '#/components/schemas/LineItemType' amountToApplyOnBill: type: number description: '' productId: type: string description: The UUID of the Product. accountingProductId: type: string description: '' description: minLength: 1 type: string description: The description for the line item. amount: minimum: 0 exclusiveMinimum: true type: number description: The amount for the line item. referencedBillId: type: string description: 'The UUID of the bill for the line item. ' referencedLineItemId: type: string description: The UUID of the line item. servicePeriodStartDate: type: string description: The service period start date in ISO-8601 format. *(inclusive of the starting date)*. format: date-time servicePeriodEndDate: type: string description: The service period end date in ISO-8601 format.*(exclusive of the ending date)*. format: date-time AbstractBillLineItemResponse: type: object description: '' allOf: - $ref: '#/components/schemas/AbstractResponse' - properties: lineItemType: description: '' $ref: '#/components/schemas/LineItemType' productId: type: string description: '' description: type: string description: '' servicePeriodStartDate: type: string description: '' format: date-time servicePeriodEndDate: type: string description: '' format: date-time referencedBillId: type: string description: '' referencedLineItemId: type: string description: '' dtCreated: type: string description: The DateTime when the line item was created. format: date-time x-stainless-skip: - terraform dtLastModified: type: string description: The DateTime when the line item was last modified. format: date-time x-stainless-skip: - terraform createdBy: type: string description: The ID of the user who created this line item. x-stainless-skip: - terraform lastModifiedBy: type: string description: The ID of the user who last modified this line item. x-stainless-skip: - terraform AbstractResponse: required: - id type: object properties: id: type: string description: 'The UUID of the entity. ' version: type: integer description: '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.' format: int64 x-stainless-terraform-configurability: computed x-stainless-terraform-always-send: true description: '' DebitLineItemRequest: type: object description: '' allOf: - $ref: '#/components/schemas/MemoLineItemRequest' - $ref: '#/components/schemas/AbstractRequest' - properties: amountToApplyOnBill: type: number description: '' debitReasonId: type: string description: The ID of the Debit Reason given for this debit line item. PaginatedDebitLineItemResponseData: type: object properties: data: type: array description: '' items: $ref: '#/components/schemas/DebitLineItemResponse' nextToken: type: string description: '' description: '' DebitLineItemResponse: type: object description: '' allOf: - $ref: '#/components/schemas/AbstractBillLineItemResponse' - $ref: '#/components/schemas/AbstractResponse' - properties: amount: type: number description: '' debitReasonId: type: string description: The UUID of the debit reason for this debit line item. AbstractRequest: type: object properties: version: type: integer description: '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.' format: int64 x-stainless-terraform-configurability: computed x-stainless-terraform-always-send: true description: '' LineItemType: type: string description: See [Bill Line Item Types](https://www.m3ter.com/docs/guides/running-viewing-and-managing-bills/bill-line-item-types) for more information. enum: - STANDING_CHARGE - USAGE - COUNTER_RUNNING_TOTAL_CHARGE - COUNTER_ADJUSTMENT_DEBIT - COUNTER_ADJUSTMENT_CREDIT - USAGE_CREDIT - MINIMUM_SPEND - MINIMUM_SPEND_REFUND - CREDIT_DEDUCTION - MANUAL_ADJUSTMENT - CREDIT_MEMO - DEBIT_MEMO - COMMITMENT_CONSUMED - COMMITMENT_FEE - OVERAGE_SURCHARGE - OVERAGE_USAGE - BALANCE_CONSUMED - BALANCE_FEE - AD_HOC responses: Error: description: Error message content: application/json: schema: type: object properties: message: type: string securitySchemes: OAuth2: type: oauth2 description: "m3ter supports machine to machine authentication using the `clientCredentials` OAuth2 flow.\n\nThe `authorizationCode` flow controls access for human users via the m3ter Console application. \n" flows: clientCredentials: tokenUrl: /oauth/token scopes: m3ter-resources/m3ter-scope: m3ter resources measurements:upload: Upload measurements measurements:fileUpload: Upload file measurements:retrieve: Retrieve measurements authorizationCode: authorizationUrl: https://m3ter.auth.us-east-1.amazoncognito.com/oauth2/authorize tokenUrl: https://m3ter.auth.us-east-1.amazoncognito.com/oauth2/token scopes: m3ter-resources/m3ter-scope: m3ter resources openid: OpenID email: email measurements:upload: Upload measurements measurements:fileUpload: Upload file measurements:retrieve: Retrieve measurements