---
title: "Submit Measurements"
method: POST
path: "/organizations/{orgId}/measurements"
tags: ["Measurements"]
---

# Submit Measurements

`POST /organizations/{orgId}/measurements`

Submit a measurement or multiple measurements to the m3ter platform. The maximum size of the payload needs to be less than 512,000 bytes.

**NOTES:**
* **Non-existent Accounts.** The `account` request parameter is required. However, if you want to submit a usage data measurement for an Account which does not yet exist in your Organization, you can use an `account` code for a non-existent Account. A new skeleton Account will be automatically created. The usage data measurement is accepted and ingested as data belonging to the new auto-created Account. At a later date, you can edit the Account's Code,??Name, and??e-mail address. For more details, see [Submitting Usage Data for Non-Existent Accounts](https://www.m3ter.com/docs/guides/billing-and-usage-data/submitting-usage-data/submitting-usage-data-for-non-existent-accounts) in our main documentation.
* **Usage Data Adjustments.** If you need to make corrections for billing retrospectively against an Account, you can use date/time values in the past for the `ts` (timestamp) request parameter to submit positive or negative usage data amounts to correct and reconcile earlier billing anomalies. For more details, see [Submitting Usage Data Adjustments Using Timestamp](https://www.m3ter.com/docs/guides/billing-and-usage-data/submitting-usage-data/submitting-usage-data-adjustments-using-timestamp) in our main documentation.
* **Ingest Validation Failure Events.** After the intial submission of a usage data measurement to the Ingest API, a data enrichment stage is performed to check for any errors in the usage data measurement, such as a missing field. If an error is identified, this might result in the submission being rejected. In these cases, an *ingest validation failure* Event is generated, which you can review on the [Ingest Events](https://www.m3ter.com/docs/guides/billing-and-usage-data/submitting-usage-data/reviewing-and-resolving-ingest-events) page in the Console. See also the [Events](https://www.m3ter.com/docs/api#tag/Events) section in this API Reference.

**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 measurements you submit do not contain any end-customer PII data. See the [Introduction section](https://www.m3ter.com/docs/api#section/Introduction) above for more details.

## Path parameters

- `orgId` string, required

## Request body

- SubmitMeasurementsRequest
  - `measurements` MeasurementRequest[], required — Request containing the usage data measurements for submission.
    - `uid` string — Unique ID for this measurement.
    - `meter` string, required — Short code identifying the Meter the measurement is for.
    - `account` string, required — Code of the Account the measurement is for.
    - `ts` string, date-time, required — Timestamp for the measurement *(in ISO 8601 format)*.
    - `ets` string, date-time — End timestamp for the measurement *(in ISO 8601 format)*. *(Optional)*. Can be used in the case a usage event needs to have an explicit start and end rather than being instantaneous.
    - `who` object — 'who' values
    - `where` object — 'where' values
    - `what` object — 'what' values
    - `other` object — 'other' values
    - `metadata` object — 'metadata' values
    - `measure` object — 'measure' values
    - `cost` object — 'cost' values
    - `income` object — 'income' values

## Response `200`

Returns the result of the submission

- SubmitMeasurementsResponse
  - `result` string — `accepted` is returned when successful.

## Other responses

- `4XX` — Error message
- `5XX` — Error message

---

[API](https://skmtc.net/m3ter-com/apis/m3ter-api.md) · [All operations](https://skmtc.net/m3ter-com/apis/m3ter-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/m3ter-com/m3ter-api/revisions/ac93d1a9e6d9/schema)