> ## Documentation Index > Fetch the complete documentation index at: https://docs.mixpanel.com/llms.txt > Use this file to discover all available pages before exploring further. # Aggregrated Event Property Values > Get unique, total, or average data for of a single event and property over days, weeks, or months. The Query API has a rate limit of 60 queries per hour and a maximum of 5 concurrent queries. ## OpenAPI ````yaml openapi/query.openapi.yaml GET /events/properties openapi: 3.0.3 info: title: Query API description: query api license: name: MIT url: https://opensource.org/licenses/MIT contact: url: https://mixpanel.com/get-support version: 1.0.0 servers: - url: https://{regionAndDomain}.com/api/query description: Mixpanel's calculated data API variables: regionAndDomain: default: mixpanel enum: - mixpanel - eu.mixpanel - in.mixpanel description: | The server location to be used: * `mixpanel` - The default (US) servers used for most projects * `eu.mixpanel` - EU servers if you are enrolled in EU Data Residency * `in.mixpanel` - India servers if you are enrolled in India Data Residency security: - ServiceAccount: [] - ProjectSecret: [] tags: - name: Activity Feed description: See a profiles recent events history - name: Cohorts description: Understand what defines a cohort and how many profiles qualify - name: Engage description: Query for profile information - name: Event Breakdown description: Breakdowns on the most common events in your project - name: Funnels description: Query data shown in your Funnels reports - name: Insights description: Query data shown in your Insights reports - name: JQL description: Write a custom query on your data - name: Retention description: Query data shown in your Retention reports - name: Segmentation description: Query data shown in your Segmenation reports paths: /events/properties: get: tags: - Event Breakdown summary: Aggregrated Event Property Values description: >- Get unique, total, or average data for of a single event and property over days, weeks, or months. The Query API has a rate limit of 60 queries per hour and a maximum of 5 concurrent queries. operationId: query-event-properties parameters: - in: query name: project_id schema: type: integer description: Required if using service account to authenticate request. required: true - $ref: '#/components/parameters/workspaceId' - in: query name: event schema: type: string description: >- The event that you wish to get data for. Note: this is a single event name, not an array. required: true - $ref: '#/components/parameters/propertyName' - in: query name: values schema: type: array items: type: string description: >- The specific property values that you would like to get data for, encoded as a JSON array. Example: If you have a property "gender" you may have values "male", "female" and "unknown". If you just want data for female and unknown users, you can include a values property that looks like "["female", "unknown"]". - $ref: '#/components/parameters/type' - $ref: '#/components/parameters/unit' - $ref: '#/components/parameters/interval' - in: query name: from_date schema: type: string description: >- The date in yyyy-mm-dd format to begin querying from. This date is inclusive. required: true - in: query name: to_date schema: type: string description: The date in yyyy-mm-dd format to query to. This date is inclusive. required: true - $ref: '#/components/parameters/format' - $ref: '#/components/parameters/limit255' responses: '200': description: Success. content: application/json: examples: example: value: data: series: - '2010-05-29' - '2010-05-30' - '2010-05-31' values: splash features: '2010-05-29': 6 '2010-05-30': 4 '2010-05-31': 5 legend_size: 2 schema: type: object properties: data: type: object properties: series: $ref: '#/components/schemas/series' values: type: object additionalProperties: description: >- A mapping of the date of each unit to the number of events with that property value. (ex. {"2010-05-30": 6}) legend_size: type: integer components: parameters: workspaceId: in: query name: workspace_id schema: type: integer description: The id of the workspace if applicable. propertyName: in: query name: name schema: type: string description: The name of the property you would like to get data for. required: true type: in: query name: type schema: type: string enum: - general - unique - average description: >- The analysis type you would like to get data for - such as general, unique, or average events. Valid values: "general", "unique", or "average". required: true unit: in: query name: unit schema: type: string enum: - minute - hour - day - week - month description: >- This can be "minute", "hour", "day", "week", or "month". It determines the level of granularity of the data you get back. Note that you cannot get hourly uniques. required: true interval: in: query name: interval schema: type: integer description: >- The number of "units" to return data for - minutes, hours, days, weeks, or months. 1 will return data for the current unit (minute, hour, day, week or month). 2 will return the current and previous units, and so on. Specify either interval or from_date and to_date. format: in: query name: format schema: type: string enum: - json - csv description: >- The data return format, such as JSON or CSV. Options: "json" (default), "csv". limit255: in: query name: limit schema: type: integer description: The maximum number of values to return. Defaults to 255. schemas: series: type: array items: type: string description: All dates we have data for in the response. securitySchemes: ServiceAccount: type: http scheme: basic description: Service Account ProjectSecret: type: http scheme: basic description: Project Secret ````