---
title: "Get meter trigger"
method: GET
path: "/metertriggers/{id}"
tags: ["Meter Triggers"]
---

# Get meter trigger

`GET /metertriggers/{id}`

## Path parameters

- `id` integer, required

## Query parameters

- `expand` string[]

## Response `200`

Successfully retrieved meterTrigger's information

- object
  - `meterTrigger` object, required
    - `id` integer, required — Global ID of the meter trigger
    - `meterId` integer, required — Global ID of the meter
    - `organizationId` integer, required — Global ID of the organization
    - `amount` number, required — Value used to trigger the condition
    - `condition` 'DECREMENTED_BY' | 'INCREMENTED_BY' | 'IS_EQUAL' | 'IS_GREATER' | 'IS_LESS' | 'INCREMENTED_BY_BASED_ON_LAST_READING' | 'DECREMENTED_BY_BASED_ON_LAST_READING', required — Condition of the trigger
    - `createdAt` string, date-time, required — Date at which the meter was created
    - `creatorId` integer, required — Global ID of the meter trigger's creator
    - `dataPoints` object, nullable, required
      - `numerator` integer — The number of data points out of "denominator" data points to trigger. E.g: 3 points out of 5 must be in a triggering state
      - `denominator` integer — The window of points where the condition gets checked
    - `deletedAt` string, date-time, nullable, required — Data at which the meter was delated
    - `description` string, nullable, required
    - `minDateForProcessing` string, date-time, nullable, required — Date that the trigger will start to be active
    - `name` string, required — Name of the trigger
    - `nextTriggerValue` number, nullable, required — Can be set to override the first trigger value
    - `period` integer, nullable, required — Window in seconds where the data points can be checked
    - `state` 'INACTIVE' | 'INSUFFICIENT_DATA' | 'PENDING' | 'STABLE' | 'TRIGGERED', required — State of the trigger
    - `updatedAt` string, date-time, required — Date at which the meter was updated
    - `workOrderTemplateId` integer, nullable, required — Global ID of the work order template used by the meter trigger
    - `workOrderTemplate` object, nullable — Work Order template used by the meter trigger (expand with query parameter)
      - `id` integer — Global ID of the work order template
      - `createdAt` string, date-time — Date & time at which the work order template was created
      - `creatorId` integer, nullable — ID of the user who created the work order
      - `deletedAt` string, date-time, nullable — Time at which the template was deleted
      - `organizationId` integer, nullable — ID of the organization
      - `procedureTemplateId` integer, nullable — ID of the procedure template used if in the library
      - `title` string — Title of the work order that will be generated. Use the meter trigger's name instead
      - `updatedAt` string, date-time, nullable — Time at which the template was updated
      - `data` object
        - `assetId` integer, nullable — Global ID of the asset assigned to the work order
        - `assigneeIds` number[] — Users IDs assigned to the template
        - `attachmentIds` number[], nullable — IDs of the attachments on the template
        - `description` string, nullable
        - `dueDate` object, nullable
          - `type` 'OFFSET'
          - `offset` number
        - `locationId` integer, nullable — Global ID of the location assigned to the work order
        - `partsUsed` object[], nullable
          - `id` integer — Global ID of the part
          - `name` string
          - `description` string, nullable
          - `area` string, nullable
          - `unitCost` integer, nullable — Cost in cents. For example, for $1.20, put 120.
          - `availableQuantity` integer — Quantity currently in stock
          - `minimumQuantity` integer — Minimum quantity before you should restock
          - `barcode` string, nullable — String encoded barcode
          - `quantityUsed` integer — Quantity used in the work order.
          - `copyOnRecurring` 'NoCopy' | 'Copy' | 'Default' — Indicates if the parts will be copied to the next work order in the chain (if applicable).
          - `locationId` number, nullable — Global ID of the location of the part
          - `extraFields` object — Work Order-scoped custom fields for this Part on this specific Work Order. These are distinct from Part-level custom fields (see `partExtraFields`).
        - `priority` 'NONE' | 'LOW' | 'MEDIUM' | 'HIGH'
        - `procedure` object, nullable
          - `title` string, required
          - `fields` object[], required
            - `id` number, required
            - `label` string, required
            - `type` 'NUMBER' | 'AMOUNT' | 'TEXT' | 'UNSUPPORTED' | 'HEADING' | 'FILE' | 'SIGNATURE' | 'MULTIPLE_CHOICE' | 'INSPECTION_CHECK' | 'YES_NO_NA' | 'CHECKBOX' | 'CHECKLIST' | 'METER' | 'DATE' | 'CYCLE_COUNT', required
            - `description` string, nullable
            - `choices` string[], nullable
            - `meterId` number, nullable
            - `isDateAndTime` boolean, nullable — Indicate if a DATE field also contains the time
            - `attachmentId` number, nullable
            - `attachments` object[] — List of attachments linked to the procedure row
              - …
            - `urls` object[]
              - …
        - `tagsIds` number[] — Categories IDs
        - `teamIds` number[] — Teams IDs
        - `thumbnailId` integer, nullable — ID of the attachment used as thumbnail
        - `title` string — Use the `title` field outside of the data object instead
        - `vendorIds` number[] — Vendor IDs

## Other responses

- `400` — Error with query
- `401` — Invalid token
- `404` — Could not find the specified meterTrigger or the user cannot access it.

---

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