---
title: "POST /v4/{+parent}/dataPoints:dailyRollUp"
method: POST
path: "/v4/{+parent}/dataPoints:dailyRollUp"
tags: ["users"]
---

# POST /v4/{+parent}/dataPoints:dailyRollUp

`POST /v4/{+parent}/dataPoints:dailyRollUp`

Roll up data points over civil time intervals for supported data types.

## Path parameters

- `parent` string, required

## Request body

- DailyRollUpDataPointsRequest — Request to roll up data points by civil time intervals.
  - `windowSizeDays` integer — Optional. Aggregation window size, in number of days. Defaults to 1 if not specified.
  - `pageSize` integer — Optional. The maximum number of data points to return. If unspecified, at most 1440 data points will be returned. The maximum page size is 10000; values above that will be truncated accordingly.
  - `dataSourceFamily` string — Optional. The data source family name to roll up. If empty, data points from all available data sources will be rolled up. Format: `users/me/dataSourceFamilies/{data_source_family}` The supported values are: - `users/me/dataSourceFamilies/all-sources` - default value - `users/me/dataSourceFamilies/google-wearables` - tracker devices - `users/me/dataSourceFamilies/google-sources` - Google first party sources
  - `range` CivilTimeInterval — Counterpart of google.type.Interval, but using CivilDateTime.
    - `start` CivilDateTime — Civil time representation similar to google.type.DateTime, but ensures that neither the timezone nor the UTC offset can be set to avoid confusion between civil and physical time queries.
      - `date` Date — Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp
        - `year` integer — Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
        - `month` integer — Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
        - `day` integer — Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.
      - `time` TimeOfDay — Represents a time of day. The date and time zone are either not significant or are specified elsewhere. An API may choose to allow leap seconds. Related types are google.type.Date and `google.protobuf.Timestamp`.
        - `minutes` integer — Minutes of an hour. Must be greater than or equal to 0 and less than or equal to 59.
        - `seconds` integer — Seconds of a minute. Must be greater than or equal to 0 and typically must be less than or equal to 59. An API may allow the value 60 if it allows leap-seconds.
        - `hours` integer — Hours of a day in 24 hour format. Must be greater than or equal to 0 and typically must be less than or equal to 23. An API may choose to allow the value "24:00:00" for scenarios like business closing time.
        - `nanos` integer — Fractions of seconds, in nanoseconds. Must be greater than or equal to 0 and less than or equal to 999,999,999.
    - `end` CivilDateTime — Civil time representation similar to google.type.DateTime, but ensures that neither the timezone nor the UTC offset can be set to avoid confusion between civil and physical time queries.
      - `date` Date — Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp
        - `year` integer — Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
        - `month` integer — Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
        - `day` integer — Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.
      - `time` TimeOfDay — Represents a time of day. The date and time zone are either not significant or are specified elsewhere. An API may choose to allow leap seconds. Related types are google.type.Date and `google.protobuf.Timestamp`.
        - `minutes` integer — Minutes of an hour. Must be greater than or equal to 0 and less than or equal to 59.
        - `seconds` integer — Seconds of a minute. Must be greater than or equal to 0 and typically must be less than or equal to 59. An API may allow the value 60 if it allows leap-seconds.
        - `hours` integer — Hours of a day in 24 hour format. Must be greater than or equal to 0 and typically must be less than or equal to 23. An API may choose to allow the value "24:00:00" for scenarios like business closing time.
        - `nanos` integer — Fractions of seconds, in nanoseconds. Must be greater than or equal to 0 and less than or equal to 999,999,999.
  - `pageToken` string — Optional. The `next_page_token` from a previous request, if any. All other request fields need to be the same as in the initial request when the page token is specified.

## Response `200`

Successful response

---

[API](https://skmtc.dev/google/apis/health.md) · [All operations](https://skmtc.dev/google/apis/health/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/google/health/revisions/601e805b7a55/schema)