> ## Documentation Index > Fetch the complete documentation index at: https://docs.voucherify.io/llms.txt > Use this file to discover all available pages before exploring further. # Get program spending daily report > ⚠️ **BETA endpoint** This is a work-in-progress documentation of a BETA endpoint. The parameters, fields, request and response bodies, and other data may subject to change. If you want to share feedback or improvements, contact Voucherify support or your Technical Account Manager. Returns aggregated daily points-spending statistics for the program over the given date range and resolution, optionally filtered by card definition. The date range is limited per resolution: maximum 90 days for `day`, 12 weeks for `week`, 12 months for `month`, 4 quarters for `quarter`. ## OpenAPI ````yaml /openapi/loyalties-v2.json get /v2/loyalties/programs/{programId}/reports/spending/daily openapi: 3.1.0 info: title: Voucherify Loyalty v2 API version: 2.0.0 description: >- Complete OpenAPI specification for the Voucherify Loyalty v2 API. All endpoints require the LOYALTY_V2 feature flag. Combined from per-domain specs: programs.yaml, members.yaml, program-operations.yaml, card-definitions.yaml, earning-rules.yaml, tier-structures.yaml, benefits.yaml, rewards.yaml, examine.yaml servers: - url: '{protocol}://{host}' variables: protocol: default: https enum: - https - http host: default: api.voucherify.io security: - bearerAuth: [] X-App-Id: [] X-App-Token: [] tags: - name: Programs description: >- Loyalty program CRUD, lifecycle management, program-scoped resource assignments (card definitions, earning rules, rewards, tier structures), member management (create, list, get, activate, deactivate, delete), card operations (points adjustment, pending points, expiring points, transactions), reward purchases, and activity history. - name: Card Definitions description: >- CRUD operations, lifecycle management, and activity history for card definitions. Card definitions describe the configuration for loyalty cards, including code generation, points expiration, earning/spending limits, pending points, refunds, and balance settings. - name: Earning Rules description: >- Manage earning rules that define how customers earn points or receive incentives based on triggers (events, segments, custom events). Includes CRUD, lifecycle, and activity history. - name: Tier Structures description: >- CRUD operations, lifecycle management, and activity history for tier structures. Includes nested tier definitions (create, list, update, delete) within tier structures. Tier structures define the tiering model for loyalty programs — how members qualify for and move between tiers. - name: Benefits description: >- Manage benefit definitions (fixed points, proportional points, material, digital). Includes CRUD, lifecycle transitions, and activity history. - name: Rewards description: >- CRUD, lifecycle operations, and activity history for reward definitions. Rewards can be material (product/SKU) or digital (discount coupons, gift vouchers). - name: Examine description: >- Evaluation endpoints that estimate earning opportunities and reward availability for a customer across their loyalty program memberships, without side effects. paths: /v2/loyalties/programs/{programId}/reports/spending/daily: get: tags: - Programs summary: Get program spending daily report description: > ⚠️ **BETA endpoint** This is a work-in-progress documentation of a BETA endpoint. The parameters, fields, request and response bodies, and other data may subject to change. If you want to share feedback or improvements, contact Voucherify support or your Technical Account Manager. Returns aggregated daily points-spending statistics for the program over the given date range and resolution, optionally filtered by card definition. The date range is limited per resolution: maximum 90 days for `day`, 12 weeks for `week`, 12 months for `month`, 4 quarters for `quarter`. operationId: getProgramSpendingDailyReport parameters: - name: programId in: path required: true description: > Unique loyalty program identifier (format: `lprg_` followed by hexadecimal characters). schema: type: string - name: start_date in: query required: true description: Start of the report date range (inclusive), in `YYYY-MM-DD` format. schema: type: string format: date pattern: ^\d{4}-\d{2}-\d{2}$ - name: end_date in: query required: true description: End of the report date range, in `YYYY-MM-DD` format. schema: type: string format: date pattern: ^\d{4}-\d{2}-\d{2}$ - name: resolution in: query required: true description: > Aggregation resolution of the report. The allowed date range depends on the resolution: `day` — max 90 days, `week` — max 12 weeks, `month` — max 12 months, `quarter` — max 4 quarters. schema: type: string enum: - day - week - month - quarter - name: filters in: query required: false style: deepObject explode: true description: > Field filters, e.g. `filters[card_definition_id][conditions][$is]=lcdef_...`. Each field accepts a `conditions` object with condition operators. schema: $ref: '#/components/schemas/SpendingReportListFilters' responses: '200': description: Program spending daily report. content: application/json: schema: $ref: '#/components/schemas/SpendingReportDailyResponse' '400': description: >- Validation error - request body or query parameters failed validation, or the operation is not allowed in the current resource state. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: Conflict - e.g. duplicate resource or invalid state transition. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: SpendingReportListFilters: type: object description: | Filters for spending reports. properties: junction: description: >- Logical junction between the field filters. Defaults to AND behavior. oneOf: - type: string enum: - AND - OR - type: 'null' card_definition_id: description: | Filter by card definition id. oneOf: - $ref: >- #/components/schemas/SpendingReportFilterCardDefinitionIdConditions - type: 'null' additionalProperties: false SpendingReportDailyResponse: type: object description: Program spending daily report result. properties: data: type: array description: Report entries, one per aggregation period and card definition. items: $ref: '#/components/schemas/SpendingReportDailyEntry' object: type: string const: report description: Object type marker. Always `report`. ErrorResponse: type: object description: Standard error response returned by all Loyalty v2 endpoints. properties: code: type: integer description: HTTP status code of the error. key: type: string description: Machine-readable error key. message: type: string description: Human-readable error message. details: type: string description: Additional details about the error. request_id: type: string description: Identifier of the request that produced the error. SpendingReportFilterCardDefinitionIdConditions: type: object description: > ID filter conditions for card definition ids. Values must match pattern `^lcdef_[a-f0-9]+$`. `$is`/`$is_not` accept a single value (string or 1-element array); `$in`/`$not_in` accept a string or an array of 1-100 values. properties: conditions: type: object minProperties: 1 additionalProperties: false properties: $is: description: Matches rows whose card definition id equals the given value. oneOf: - type: string pattern: ^lcdef_[a-f0-9]+$ - type: array items: type: string pattern: ^lcdef_[a-f0-9]+$ minItems: 1 maxItems: 1 - type: 'null' $is_not: description: >- Matches rows whose card definition id does not equal the given value. oneOf: - type: string pattern: ^lcdef_[a-f0-9]+$ - type: array items: type: string pattern: ^lcdef_[a-f0-9]+$ minItems: 1 maxItems: 1 - type: 'null' $in: description: >- Matches rows whose card definition id is one of the given values. oneOf: - type: string pattern: ^lcdef_[a-f0-9]+$ - type: array items: type: string pattern: ^lcdef_[a-f0-9]+$ minItems: 1 maxItems: 100 - type: 'null' $not_in: description: >- Matches rows whose card definition id is not one of the given values. oneOf: - type: string pattern: ^lcdef_[a-f0-9]+$ - type: array items: type: string pattern: ^lcdef_[a-f0-9]+$ minItems: 1 maxItems: 100 - type: 'null' required: - conditions additionalProperties: false SpendingReportDailyEntry: type: object description: > Aggregated daily program spending statistics for one period and card definition. All numeric fields default to 0. properties: date: type: string format: date description: Date of the aggregation period (`YYYY-MM-DD`). card_definition_id: type: string description: Identifier of the card definition (format `lcdef_...`). success: type: number description: Number of successful spending operations in the period. success_on_reward: type: number description: Number of successful reward purchases in the period. success_on_order: type: number description: Number of successful order payments in the period. points: type: number description: Total points spent in the period. points_on_rewards: type: number description: Points spent on reward purchases in the period. points_on_order: type: number description: Points spent on order payments in the period. amount_on_order: type: number description: Order amount paid with points in the period. object: type: string const: spending_daily_report description: Object type marker. Always `spending_daily_report`. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT X-App-Id: type: apiKey name: X-App-Id in: header X-App-Token: type: apiKey name: X-App-Token in: header ````