# List profiles of a meter ## OpenAPI Specification ```yaml openapi: 3.0.1 info: title: '' description: '' version: 1.0.0 paths: /import/profiles/{customerUuid}/{meterIdentification}/profiles: get: summary: List profiles of a meter deprecated: false description: >- This action allows to list profiles of a single meter. Values are in the default unit of corresponding energy. The values can be [sorted](https://apidocs.enectiva.cz/introduction-1363538m0.md#sort-options), the default order is chronological. The number of returned records is by default limited to 1000, see [Limit & pagination](https://apidocs.enectiva.cz/introduction-1363538m0.md#limit--pagination) for details. If more records satisfy your [temporal filter](https://apidocs.enectiva.cz/introduction-1363538m0.md#filters), you can either keep the filter and paginate over the result set using the `page` parameter, or narrow down the filter with each request. If you do not specify a `unit`, the values will be returned in the unit configured in Enectiva. You can request values in an alternative unit. The available units depend on the energy measured and match the units in the application. Supplying an invalid unit returns an error and lists the applicable units. The required scope is `profiles`. By default only active meters are accessible. To query only for profiles of a deactivated meter include param `deactivated=true`. operationId: List profiles of a meter tags: - Profiles from Enectiva - Profiles from Enectiva parameters: - name: customerUuid in: path description: '' required: true example: '{{customerUuid}}' schema: type: string - name: meterIdentification in: path description: >- See [meter identification](https://apidocs.enectiva.cz/introduction-1363538m0.md#meter-identification) required: true example: '{{meterIdentification}}' schema: type: string - name: filter in: query description: The filter conditions required: false schema: type: string - name: unit in: query description: The unit of the profiles required: false example: '' schema: type: string - name: sort in: query description: >- The sort options. Only `profiles.time` is supported at the moment. See [sort options](https://apidocs.enectiva.cz/introduction-1363538m0.md#sort-options) for details. required: false example: '' schema: type: string - name: limit in: query description: The number of records to return, default is 1000 required: false example: 0 schema: type: number - name: page in: query description: The page number, default is 1 required: false schema: type: number - name: deactivated in: query description: Switches scope to deactivated meters required: false schema: type: boolean responses: '200': description: '' content: application/json: schema: type: object properties: {} examples: '1': summary: With data value: data: - type: profiles id: '123' attributes: from: '2019-10-01T00:00:00Z' to: '2019-10-02T00:00:00Z' value: 15 unit: kWh - type: profiles id: '124' attributes: from: '2019-10-02T00:00:00Z' to: '2019-10-03T00:00:00Z' value: 18 unit: kWh '2': summary: Empty value: data: [] headers: {} x-apidog-name: Success '400': description: '' content: application/json: schema: type: object properties: {} examples: '3': summary: Unsupported sort option value: errors: - status: '400' title: Bad Request detail: >- Sort option `profiles.unsupported_field` is not supported '4': summary: Invalid filter condition value: errors: - status: '400' title: Bad Request detail: >- Filter condition `profiles.time>not_a_date_time` is invalid headers: {} x-apidog-name: Bad Request '401': description: '' content: application/json: schema: type: object properties: {} example: |- { "errors": [ { "detail": "The provided token has expired", "status": "401", "title": "Unauthorized" } ] headers: {} x-apidog-name: Unauthorized '403': description: '' content: application/json: schema: type: object properties: {} headers: {} x-apidog-name: Forbidden '404': description: '' content: application/json: schema: type: object properties: {} headers: {} x-apidog-name: Record Not Found '406': description: '' content: application/vnd.api+json: schema: title: '' type: object properties: errors: type: array items: type: object properties: {} x-apidog-orders: [] x-apidog-orders: - errors required: - errors headers: {} x-apidog-name: Not Acceptable '429': description: '' content: application/vnd.api+json: schema: title: '' type: object properties: errors: type: array items: type: object properties: {} x-apidog-orders: [] x-apidog-orders: - errors required: - errors headers: {} x-apidog-name: Too Many Requests '500': description: '' content: application/vnd.api+json: schema: title: '' type: object properties: errors: type: array items: type: object properties: {} x-apidog-orders: [] x-apidog-orders: - errors headers: {} x-apidog-name: Server Error security: - Access token: [] x-apidog: required: true schemeGroups: - id: n-tj2NS7Hfe-8NIa7Yorr schemeIds: - Access token use: id: n-tj2NS7Hfe-8NIa7Yorr x-apidog-folder: Profiles from Enectiva x-apidog-status: developing x-run-in-apidog: https://app.apidog.com/web/project/1003855/apis/api-37898539-run components: schemas: {} securitySchemes: Access token: type: jwt scheme: bearer bearerFormat: JWT x-apidog: addTokenTo: header headerPrefix: Bearer Import token: type: jwt scheme: bearer bearerFormat: JWT x-apidog: addTokenTo: header headerPrefix: Bearer Login token: type: jwt scheme: bearer bearerFormat: JWT x-apidog: addTokenTo: header headerPrefix: Bearer Access or Import token: type: jwt scheme: bearer bearerFormat: JWT x-apidog: addTokenTo: header headerPrefix: Bearer servers: - url: https://api.enectiva.cz description: https://api.enectiva.cz security: [] ```