> ## Documentation Index > Fetch the complete documentation index at: https://documentation.qonversion.io/llms.txt > Use this file to discover all available pages before exploring further. # Get scheduled report > Returns details for a single scheduled report. ## OpenAPI ````yaml /api-reference/rest-api-v4.yaml get /scheduled-reports/{report_id} openapi: 3.0.3 info: title: Qonversion REST API v4 version: '4.0' description: >- Qonversion REST API v4 follows REST standards. It has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. servers: - url: https://api.qonversion.io/v4 description: Production security: - secretAuth: [] tags: - name: Users description: Retrieve Qonversion users - name: User Properties description: Manage user-level attributes - name: Identities description: Link Qonversion users to your own auth IDs - name: Entitlements description: Entitlement definitions and user grants - name: Purchases description: A user's purchase history - name: Products description: Products configured in the Qonversion dashboard - name: Customers description: Aggregated customer records, properties, permissions, and metrics - name: Segments description: Dynamic and system segments of users - name: Experiments description: Paywall and offering A/B experiments - name: Screens description: No-code paywall screens — CRUD, publish, analytics - name: Analytics description: Charts, cards, cohorts, LTV, and insights - name: Exports description: Asynchronous data exports - name: Events description: Event catalog - name: Scheduled Reports description: Recurring reports delivered to external destinations - name: Integrations description: Third-party integrations configuration - name: Automations description: Event-driven automations - name: Project Settings description: Project-level configuration, secret, and store credentials paths: /scheduled-reports/{report_id}: get: tags: - Scheduled Reports summary: Get scheduled report description: Returns details for a single scheduled report. operationId: v4GetScheduledReport parameters: - name: report_id in: path required: true schema: type: string maxLength: 64 pattern: ^[a-zA-Z0-9._-]+$ responses: '200': description: Scheduled report details. headers: Cache-Control: schema: type: string example: no-cache content: application/json: schema: $ref: '#/components/schemas/V4ScheduledReport' '400': description: Invalid report_id content: application/json: schema: $ref: '#/components/schemas/V4Error' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/V4Error' '403': description: Feature not available content: application/json: schema: $ref: '#/components/schemas/V4Error' '404': description: Report not found content: application/json: schema: $ref: '#/components/schemas/V4Error' '429': description: Rate limited content: application/json: schema: $ref: '#/components/schemas/V4Error' '500': description: Internal error content: application/json: schema: $ref: '#/components/schemas/V4Error' '502': description: Storage error content: application/json: schema: $ref: '#/components/schemas/V4Error' '504': description: Upstream timeout content: application/json: schema: $ref: '#/components/schemas/V4Error' security: - secretAuth: [] components: schemas: V4ScheduledReport: type: object description: | A scheduled report configuration. Delivers an analytics snapshot to the listed destinations once per day at `send_at` UTC, covering the prior `included_range_days` days of data. required: - object - id - url - report_name - send_at - included_range_days - status - environment - runs - destinations - created_at - updated_at properties: object: type: string example: scheduled_report id: type: string description: Report identifier. example: wbRlfw1x url: type: string example: /v4/scheduled-reports/wbRlfw1x report_name: type: string description: Human-readable name, 1-255 chars. example: Daily Revenue send_at: type: string description: | UTC time-of-day for the daily delivery, `HH:MM` format, aligned to 30-minute slots. Valid values range from `"00:00"` to `"23:30"`. example: '09:00' included_range_days: type: integer description: Coverage window in whole days — one of 1, 3, 7. enum: - 1 - 3 - 7 example: 1 status: type: string description: | `draft` — paused, no deliveries. `active` — enqueued for delivery at each `send_at`. enum: - draft - active example: active environment: type: string enum: - sandbox - production example: production runs: type: integer description: Number of deliveries completed so far. example: 14 destinations: type: array items: $ref: '#/components/schemas/V4ScheduledReportDestination' created_at: type: string format: date-time example: '2026-04-23T11:44:36Z' updated_at: type: string format: date-time example: '2026-04-23T11:44:36Z' V4Error: type: object required: - error properties: error: type: object required: - type - code - message properties: type: type: string enum: - request - resource - logical - internal code: type: string description: | Machine-readable snake_case error code. Examples include `invalid_data`, `invalid_request`, `invalid_product_id`, `not_found`, `already_exists`, `offering_already_exists`, `product_not_in_project`, `cannot_set_main_directly`, `cannot_demote_main`, `cannot_patch_experiment_variant`, `cannot_delete_experiment_variant`, and `cannot_setmain_experiment_variant`. Resource-specific codes are documented on the corresponding reference page. message: type: string description: Human-readable description. May change; do not parse. details: type: array nullable: true description: Per-field validation errors, present on 400 validation failures. items: type: object properties: field: type: string message: type: string V4ScheduledReportDestination: type: object description: > Pointer to a pre-existing destination (created via the Integrations API). Use `GET /v4/scheduled-reports/destinations` to enumerate valid `{type, id}` pairs for a project. required: - type - id properties: type: type: string description: Destination kind. Currently always `target_integration`. example: target_integration id: type: string description: Destination identifier within the given type. example: int-wh-01 label: type: string description: Human-readable label — present on read, ignored on write. example: 'Webhooks: Release alerts' securitySchemes: secretAuth: type: http scheme: bearer bearerFormat: sk_… description: >- Bearer authentication using the project **Secret Key** (prefixed with `sk_`, or `test_sk_` for sandbox). All v4 public endpoints require the Secret Key — see [Authentication](/reference/v4/authentication). Never expose the Secret Key in client-side code. ````