Silverflow

Silverflow Report Scheduling API

The Report Scheduling API from Silverflow — 2 operation(s) for report scheduling.

Documentation GitHub OpenAPI

Operations 5

POST /reportSchedules Create a Report Schedule #

GET /reportSchedules List Report Schedules #

GET /reportSchedules/{reportScheduleKey} Get Report Schedule #

DELETE /reportSchedules/{reportScheduleKey} Archive a Report Schedule #

PATCH /reportSchedules/{reportScheduleKey} Update a Report Schedule #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/silverflow-report-scheduling-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  description: '**This OpenAPI specification cannot be used for code generation.** Please reach out to your TAM regarding code generation using the API Spec.'
  version: 1.417.0
  title: Silverflow Report Scheduling API
  contact:
    name: API Support
    email: support@silverflow.com
  license:
    name: Commercial
servers:
- url: https://eu-west-1.api.silverflow.com/v1
  description: Production URL for Europe - Equivalent to https://api.silverflow.co/v1
- url: https://us-east-2.api.silverflow.com/v1
  description: Production URL for North America
- url: https://eu-west-1.api-sbx.silverflow.com/v1
  description: Sandbox URL - Equivalent to https://api-sbx.silverflow.co/v1
security:
- ApiKey: []
- BearerToken: []
tags:
- name: Report Scheduling
paths:
  /reportSchedules:
    post:
      operationId: createReportSchedule
      summary: Create a Report Schedule
      description: 'Creates a new report schedule for generating various types of reports.


        It requires the `reportSchedules:Create` permission in the API key.


        The date range for the report is based on the `trigger` configuration and uses the standard UTC format for all times and timestamps.

        However, to ensure completeness, the report schedule may execute with a slight delay.

        This delay allows the system to capture any last-minute records and ensure accurate and comprehensive data.


        Once the report schedule is executed, a new report will be created, and can be retrieved by calling the List Reports or Get Report endpoint.


        To be notified of the creation of these reports, you can subscribe to the reports events using the `eventSource` `https://silverflow.com/reports` on `POST /v1/eventSubscriptions`.


        When a scheduled report is completed, if it has one of more related distribution objects, it will trigger the distribution to the specified targets.'
      tags:
      - Report Scheduling
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateReportScheduleRequest'
            examples:
              Scheme Fee Details - Hourly Interval:
                $ref: '#/components/examples/HourlySchemeFeeDetails'
              Scheme Fee Details - Daily Interval:
                $ref: '#/components/examples/DailySchemeFeeDetails'
              Scheme Fee Details - Daily with distributions:
                $ref: '#/components/examples/DailySchemeFeeDetailsWithDistributions'
              Merchant Payout:
                $ref: '#/components/examples/MerchantPayoutRequest'
              Settlement Details - Hourly Interval:
                $ref: '#/components/examples/HourlySettlementDetails'
              Settlement Details - Daily Interval:
                $ref: '#/components/examples/DailySettlementDetails'
              AMMF - Monthly Interval:
                $ref: '#/components/examples/AmmfRequest'
      responses:
        '201':
          description: The newly created report schedule object
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportScheduleResponse'
              examples:
                Scheme Fee Details - Hourly Interval:
                  $ref: '#/components/examples/Hourly'
                Scheme Fee Details - Daily Interval:
                  $ref: '#/components/examples/Daily'
                Scheme Fee Details - Daily with distributions:
                  $ref: '#/components/examples/DailyWithDistributions'
                Merchant Payout:
                  $ref: '#/components/examples/MerchantPayoutResponse'
                Settlement Details - Hourly Interval:
                  $ref: '#/components/examples/settlement-details_Hourly'
                Settlement Details - Daily Interval:
                  $ref: '#/components/examples/settlement-details_Daily'
                AMMF - Monthly Interval:
                  $ref: '#/components/examples/AmmfResponse'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                oneOf:
                - $ref: '#/components/schemas/InputValidationError'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotAuthorizedErrorDetails'
        '403':
          $ref: '#/components/responses/openapi_components-responses-ForbiddenError-3'
        '409':
          description: Conflict
          content:
            application/json:
              schema:
                oneOf:
                - $ref: '#/components/schemas/EntityAlreadyExistsErrorDetails'
                - $ref: '#/components/schemas/schemas-ReferencedEntityNotFoundErrorDetails'
                - $ref: '#/components/schemas/ReferencedEntityArchivedErrorDetails'
              examples:
                EntityAlreadyExistsErrorDetails:
                  $ref: '#/components/examples/EntityAlreadyExistsErrorExample'
                ReferencedEntityNotFoundErrorDetails:
                  $ref: '#/components/examples/openapi_components-examples-ReferencedEntityNotFoundErrorExample'
                ReferencedEntityArchivedErrorDetails:
                  $ref: '#/components/examples/ReferencedEntityArchivedErrorExample'
        '429':
          $ref: '#/components/responses/openapi_components-responses-TooManyRequestsError-3'
    get:
      operationId: listReportSchedules
      summary: List Report Schedules
      description: 'Lists all active report schedules.


        It requires the `reportSchedules:List` permission in the API key.'
      tags:
      - Report Scheduling
      parameters:
      - $ref: '#/components/parameters/reportName'
      - $ref: '#/components/parameters/parameters-limit'
      - $ref: '#/components/parameters/openapi_components-parameters-offsetToken-3'
      - $ref: '#/components/parameters/components-parameters-sortOrder'
      responses:
        '200':
          description: The report schedules
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListReportSchedulesResponse'
              example:
                items:
                - reportName: SchemeFeeDetails
                  trigger:
                    type: interval
                    cadence: hourly
                  mimeType: application/json
                  key: rsk-1e1dAHhgstYTUhlphPzZ
                  status: active
                  agentKey: cgt-1e1dAHhgstYTUhlphPzZ
                  created: '2019-08-24T14:15:22Z'
                  lastModified: '2019-08-25T14:15:22Z'
                  version: 2
                  reference: Report Reference
                - reportName: NetworkFundsTransfers
                  trigger:
                    type: interval
                    cadence: daily
                    hour: 15
                  mimeType: text/csv
                  key: rsk-1e1dAHhgstYTUhlphPzZ
                  status: active
                  agentKey: cgt-1e1dAHhgstYTUhlphPzZ
                  created: '2019-08-24T14:15:22Z'
                  lastModified: '2019-08-25T14:15:22Z'
                  version: 2
                  reference: Report Reference
                moreItems: true
                offsetToken: eyJMaXN0SW5kZXhLZXkiOiJjZ3QtMTIzNDU2IiwiTGlzdEluZGV4U29ydEtleSI6IjIwMjMtMTEtMTdUMTQ6NDA6MjcuOTcwWiIsIlR5cGVLZXkiOiJSZXBvcnQiLCJPYmplY3RLZXkiOiJyZXAtMTIzNDU2In0
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                oneOf:
                - $ref: '#/components/schemas/InputValidationError'
                - $ref: '#/components/schemas/schemas-InvalidOffsetTokenError'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotAuthorizedErrorDetails'
        '403':
          $ref: '#/components/responses/openapi_components-responses-ForbiddenError-3'
        '429':
          $ref: '#/components/responses/openapi_components-responses-TooManyRequestsError-3'
  /reportSchedules/{reportScheduleKey}:
    get:
      operationId: getReportSchedule
      summary: Get Report Schedule
      description: 'Retrieves a specific report schedule identified by its `reportScheduleKey`.


        Requirements:

        - The API key must include the `reportSchedules:Get` permission.'
      tags:
      - Report Scheduling
      parameters:
      - in: path
        name: reportScheduleKey
        required: true
        schema:
          $ref: '#/components/schemas/reportScheduleKey'
      responses:
        '200':
          description: Successfully retrieved the report schedule.
          content:
            application/json:
              schema:
                oneOf:
                - $ref: '#/components/schemas/SchemeFeeDetailsReportSchedule'
                - $ref: '#/components/schemas/NetworkFundsTransferReportSchedule'
                - $ref: '#/components/schemas/MerchantPayoutReportSchedule'
                - $ref: '#/components/schemas/ReconciliationDetailsReportSchedule'
                - $ref: '#/components/schemas/SettlementDetailsReportSchedule'
                - $ref: '#/components/schemas/AmmfReportSchedule'
              example:
                reportName: SchemeFeeDetails
                trigger:
                  type: interval
                  cadence: hourly
                mimeType: application/json
                key: rsk-1e1dAHhgstYTUhlphPzZ
                status: active
                agentKey: cgt-1e1dAHhgstYTUhlphPzZ
                created: '2019-08-24T14:15:22Z'
                lastModified: '2019-08-25T14:15:22Z'
                version: 2
                reference: Report Reference
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                oneOf:
                - $ref: '#/components/schemas/InputValidationError'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotAuthorizedErrorDetails'
        '403':
          $ref: '#/components/responses/openapi_components-responses-ForbiddenError-3'
        '404':
          description: Report schedule not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportScheduleNotFoundErrorDetails'
              example:
                type: /silverflow/problems/report/report-schedule-not-found
                title: Report schedule not found
                status: 404
                detail: The report schedule rsk-1e1dAHhgstYTUhlphPzZ is not found
                instance: /silverflow/b4cc37a0-ab24-46b4-aa8c-cc2d6eddf1b6
        '429':
          $ref: '#/components/responses/openapi_components-responses-TooManyRequestsError-3'
    delete:
      operationId: archiveReportSchedule
      summary: Archive a Report Schedule
      description: 'Archives a report schedule, meaning it will no longer be generating reports.


        It requires the `reportSchedules:Archive` permission in the API key.'
      tags:
      - Report Scheduling
      parameters:
      - in: path
        name: reportScheduleKey
        required: true
        schema:
          $ref: '#/components/schemas/reportScheduleKey'
      responses:
        '204':
          description: Successfully archived report schedule
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                oneOf:
                - $ref: '#/components/schemas/InputValidationError'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotAuthorizedErrorDetails'
        '403':
          $ref: '#/components/responses/openapi_components-responses-ForbiddenError-3'
        '404':
          description: Report schedule not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportScheduleNotFoundErrorDetails'
              example:
                type: /silverflow/problems/report/report-schedule-not-found
                title: Report schedule not found
                status: 404
                detail: The report schedule rsk-1e1dAHhgstYTUhlphPzZ is not found
                instance: /silverflow/b4cc37a0-ab24-46b4-aa8c-cc2d6eddf1b6
        '429':
          $ref: '#/components/responses/openapi_components-responses-TooManyRequestsError-3'
    patch:
      operationId: updateReportSchedule
      summary: Update a Report Schedule
      description: 'Updates an existing report schedule configuration.


        It requires the `reportSchedules:Update` permission in the API key.


        Only active report schedules can be updated. If the schedule is already deleted or archived, the request will result in an error.'
      tags:
      - Report Scheduling
      parameters:
      - in: path
        name: reportScheduleKey
        required: true
        schema:
          $ref: '#/components/schemas/reportScheduleKey'
      requestBody:
        required: true
        content:
          application/merge-patch+json:
            schema:
              $ref: '#/components/schemas/UpdateReportScheduleRequest'
            examples:
              UpdateReportSchedule:
                $ref: '#/components/examples/UpdateReportSchedule'
      responses:
        '200':
          description: The report schedule updated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportScheduleResponse'
              example:
                reportName: SchemeFeeDetails
                key: rsk-1e1dAHhgstYTUhlphPzZ
                status: active
                agentKey: cgt-1UF2NafdfrdPMf2XrS2
                created: '2019-08-24T14:15:22Z'
                lastModified: '2019-08-24T14:15:22Z'
                version: 0
                reference: string
                distributions:
                - dst-1e1dAHhgstYTUhlphPzZ
                mimeType: application/json
                trigger:
                  type: interval
                  cadence: hourly
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                oneOf:
                - $ref: '#/components/schemas/InputValidationError'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotAuthorizedErrorDetails'
        '403':
          $ref: '#/components/responses/openapi_components-responses-ForbiddenError-3'
        '404':
          description: Report schedule not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReportScheduleNotFoundErrorDetails'
              example:
                type: /silverflow/problems/report/report-schedule-not-found
                title: Report schedule not found
                status: 404
                detail: The report schedule rsk-1e1dAHhgstYTUhlphPzZ is not found
                instance: /silverflow/b4cc37a0-ab24-46b4-aa8c-cc2d6eddf1b6
        '409':
          description: Conflict
          content:
            application/json:
              schema:
                oneOf:
                - $ref: '#/components/schemas/EntityAlreadyExistsErrorDetails'
                - $ref: '#/components/schemas/schemas-ReferencedEntityNotFoundErrorDetails'
                - $ref: '#/components/schemas/ReferencedEntityArchivedErrorDetails'
              examples:
                EntityAlreadyExistsErrorDetails:
                  $ref: '#/components/examples/EntityAlreadyExistsErrorExample'
                ReferencedEntityNotFoundErrorDetails:
                  $ref: '#/components/examples/openapi_components-examples-ReferencedEntityNotFoundErrorExample'
                ReferencedEntityArchivedErrorDetails:
                  $ref: '#/components/examples/ReferencedEntityArchivedErrorExample'
        '415':
          description: Unsupported mimeType
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UnsupportedMimeTypeErrorDetails'
              example:
                type: /silverflow/problems/report/unsupported-mime-type
                title: Unsupported mimeType
                status: 415
                detail: Unsupported mimeType 'text/csv'
                instance: /silverflow/b4cc37a0-ab24-46b4-aa8c-cc2d6eddf1b6
        '429':
          $ref: '#/components/responses/openapi_components-responses-TooManyRequestsError-3'
components:
  schemas:
    UnsupportedMimeTypeErrorDetails:
      type: object
      required:
      - type
      - title
      - status
      - detail
      - instance
      properties:
        type:
          allOf:
          - $ref: '#/components/schemas/errorType'
          - enum:
            - /silverflow/problems/report/unsupported-mime-type
        title:
          allOf:
          - $ref: '#/components/schemas/errorTitle'
          - enum:
            - Unsupported mimeType
        status:
          allOf:
          - $ref: '#/components/schemas/errorStatus'
          - enum:
            - 415
        detail:
          $ref: '#/components/schemas/errorDetail'
        instance:
          $ref: '#/components/schemas/errorInstance'
    schemas-InvalidOffsetTokenError:
      type: object
      required:
      - type
      - title
      - status
      - detail
      - instance
      properties:
        type:
          allOf:
          - $ref: '#/components/schemas/errorType'
          - enum:
            - /silverflow/problems/report/invalid-offset-token
        title:
          allOf:
          - $ref: '#/components/schemas/errorTitle'
          - enum:
            - Invalid Offset Token
        status:
          allOf:
          - $ref: '#/components/schemas/errorStatus'
          - enum:
            - 400
        detail:
          $ref: '#/components/schemas/errorDetail'
        instance:
          $ref: '#/components/schemas/errorInstance'
    NetworkFundsTransferReportSchedule:
      allOf:
      - type: object
        required:
        - reportName
        properties:
          reportName:
            $ref: '#/components/schemas/NetworkFundsTransfersReportName'
      - $ref: '#/components/schemas/BaseReportSchedule'
      - type: object
        required:
        - trigger
        - mimeType
        properties:
          mimeType:
            $ref: '#/components/schemas/networkFundsTransfersReportMimeType'
          trigger:
            $ref: '#/components/schemas/NetworkFundsTransfersTrigger'
    ReportScheduleResponse:
      type: object
      oneOf:
      - $ref: '#/components/schemas/SchemeFeeDetailsReportSchedule'
      - $ref: '#/components/schemas/NetworkFundsTransferReportSchedule'
      - $ref: '#/components/schemas/MerchantPayoutReportSchedule'
      - $ref: '#/components/schemas/ReconciliationDetailsReportSchedule'
      - $ref: '#/components/schemas/ChargesReportSchedule'
      - $ref: '#/components/schemas/DisputeHistoryEventsReportSchedule'
      - $ref: '#/components/schemas/FraudNotificationsReportSchedule'
      - $ref: '#/components/schemas/SettlementDetailsReportSchedule'
      - $ref: '#/components/schemas/AmmfReportSchedule'
    MerchantPayoutReportMimeType:
      type: string
      description: The mime-type in which the MerchantPayout report is available.
      enum:
      - text/csv
    ammfAcquirerIdCode:
      type: string
      description: the Acquirer Institution ID. For Visa, this is the BIC. It should be a 6-digit numeric value.
      pattern: ^\d{6}$
    openapi_components-schemas-created-2:
      type: string
      description: The date and time this object was created
      format: date-time
      readOnly: true
    components-schemas-version:
      type: integer
      description: The version of this object
      format: int64
      readOnly: true
    errorStatus:
      type: integer
      format: int32
      description: 'The HTTP status code generated by the origin server for this occurrence

        of the problem.

        '
    fraudNotificationsScheduleTrigger:
      type: object
      description: The trigger conditions for the Fraud Notifications report schedule.
      oneOf:
      - $ref: '#/components/schemas/hourlyCadence'
      - $ref: '#/components/schemas/dailyCadence'
    fraudNotificationsReportMimeType:
      type: string
      description: The mime-type in which the fraud notifications report is available.
      enum:
      - text/csv
      - application/json
      - application/x-ndjson
    MerchantPayoutReportSchedule:
      allOf:
      - type: object
        required:
        - reportName
        properties:
          reportName:
            $ref: '#/components/schemas/MerchantPayoutReportName'
      - $ref: '#/components/schemas/BaseReportSchedule'
      - type: object
        required:
        - reportName
        - trigger
        - mimeType
        - parameters
        properties:
          reportName:
            $ref: '#/components/schemas/MerchantPayoutReportName'
          mimeType:
            $ref: '#/components/schemas/MerchantPayoutReportMimeType'
          trigger:
            $ref: '#/components/schemas/MerchantPayoutScheduleTrigger'
          parameters:
            $ref: '#/components/schemas/MerchantPayoutReportScheduleParameters'
    UpdateReconciliationDetailScheduleRequest:
      type: object
      description: A schedule for Reconciliation Details reports
      additionalProperties: false
      properties:
        mimeType:
          $ref: '#/components/schemas/reconciliationDetailsReportMimeType'
        trigger:
          $ref: '#/components/schemas/reconciliationDetailsScheduleTrigger'
        reference:
          $ref: '#/components/schemas/components-schemas-reference'
        distributions:
          $ref: '#/components/schemas/distributions'
    CreateFraudNotificationsScheduleRequest:
      allOf:
      - type: object
        description: A schedule for Fraud Notifications reports
        required:
        - reportName
        - trigger
        - mimeType
        properties:
          reportName:
            $ref: '#/components/schemas/FraudNotificationsReportName'
          mimeType:
            $ref: '#/components/schemas/fraudNotificationsReportMimeType'
          trigger:
            $ref: '#/components/schemas/fraudNotificationsScheduleTrigger'
      - $ref: '#/components/schemas/BaseCreateReportScheduleRequest'
    errorInstance:
      type: string
      description: 'A reference that identifies the specific occurrence of the error. The instance is unique for every error.

        '
    CreateAmmfReportScheduleRequest:
      allOf:
      - type: object
        required:
        - reportName
        - parameters
        - mimeType
        - trigger
        additionalProperties: false
        properties:
          reportName:
            $ref: '#/components/schemas/AMMFReportName'
          trigger:
            $ref: '#/components/schemas/AmmfReportScheduleTrigger'
          parameters:
            $ref: '#/components/schemas/AMMFReportScheduleParameters'
          reference:
            $ref: '#/components/schemas/components-schemas-reference'
          mimeType:
            $ref: '#/components/schemas/ammfReportMimeType'
          distributions:
            $ref: '#/components/schemas/distributions'
      - $ref: '#/components/schemas/BaseCreateReportScheduleRequest'
    chargesReportMimeType:
      type: string
      description: The mime-type in which the Charges report is available.
      enum:
      - text/csv
    AmmfReportSchedule:
      allOf:
      - type: object
        required:
        - reportName
        properties:
          reportName:
            $ref: '#/components/schemas/AMMFReportName'
      - $ref: '#/components/schemas/BaseReportSchedule'
      - type: object
        required:
        - trigger
        - parameters
        - mimeType
        properties:
          mimeType:
            $ref: '#/components/schemas/ammfReportMimeType'
          parameters:
            $ref: '#/components/schemas/AMMFReportScheduleParameters'
          trigger:
            $ref: '#/components/schemas/AmmfReportScheduleTrigger'
    CreateMerchantPayoutScheduleRequest:
      allOf:
      - type: object
        description: A schedule for Merchant Payout reports
        required:
        - reportName
        - trigger
        - mimeType
        - parameters
        properties:
          reportName:
            $ref: '#/components/schemas/MerchantPayoutReportName'
          mimeType:
            $ref: '#/components/schemas/MerchantPayoutReportMimeType'
          trigger:
            $ref: '#/components/schemas/MerchantPayoutScheduleTrigger'
          parameters:
            $ref: '#/components/schemas/MerchantPayoutReportScheduleParameters'
      - $ref: '#/components/schemas/BaseCreateReportScheduleRequest'
    ReferencedEntityArchivedErrorDetails:
      allOf:
      - $ref: '#/components/schemas/BaseConflictError'
      - type: object
        required:
        - type
        - title
        properties:
          type:
            allOf:
            - $ref: '#/components/schemas/errorType'
            - enum:
              - /silverflow/problems/report/referenced-entity-archived
          title:
            allOf:
            - $ref: '#/components/schemas/errorTitle'
            - enum:
              - Referenced Entity Archived
    errorType:
      type: string
      description: 'A relative URI reference, this property can be used to perform automated error handling.

        '
    InputValidationError:
      type: object
      required:
      - type
      - title
      - status
      - detail
      - instance
      - validationErrors
      properties:
        type:
          allOf:
          - $ref: '#/components/schemas/errorType'
          - enum:
            - /silverflow/problems/invalid-input
        title:
          allOf:
          - $ref: '#/components/schemas/errorTitle'
          - enum:
            - Invalid Input
        status:
          allOf:
          - $ref: '#/components/schemas/errorStatus'
          - enum:
            - 400
        detail:
          allOf:
          - $ref: '#/components/schemas/errorDetail'
          - enum:
            - The request does not adhere to the defined API schema.
        instance:
          $ref: '#/components/schemas/errorInstance'
        validationErrors:
          type: array
          items:
            $ref: '#/components/schemas/openapi_components-schemas-ValidationError'
          description: A list of validation errors.
    errorDetail:
      type: string
      description: 'A human readable explanation specific to this occurrence of the problem.

        '
    SchemeFeeDetailsReportName:
      type: string
      description: The name of the report.
      enum:
      - SchemeFeeDetails
    reconciliationDetailsScheduleTrigger:
      type: object
      description: The trigger conditions for the reconciliation details schedule.
      oneOf:
      - $ref: '#/components/schemas/hourlyCadence'
      - $ref: '#/components/schemas/dailyCadence'
    UpdateMerchantPayoutScheduleRequest:
      type: object
      description: A schedule for Merchant Payout reports
      additionalProperties: false
      properties:
        mimeType:
          $ref: '#/components/schemas/MerchantPayoutReportMimeType'
        trigger:
          $ref: '#/components/schemas/MerchantPayoutScheduleTrigger'
        reference:
          $ref: '#/components/schemas/components-schemas-reference'
        distributions:
          $ref: '#/components/schemas/distributions'
    CreateNetworkFundsTransfersScheduleRequest:
      allOf:
      - type: object
        description: A schedule for Network Funds Transfer reports
        required:
        - reportName
        - trigger
        - mimeType
        properties:
          reportName:
            $ref: '#/components/schemas/NetworkFundsTransfersReportName'
          mimeType:
            $ref: '#/components/schemas/networkFundsTransfersReportMimeType'
          trigger:
            $ref: '#/components/schemas/NetworkFundsTransfersTrigger'
      - $ref: '#/components/schemas/BaseCreateReportScheduleRequest'
    EntityAlreadyExistsErrorDetails:
      allOf:
      - $ref: '#/components/schemas/BaseConflictError'
      - type: object
        required:
        - type
        - title
        properties:
          type:
            allOf:
            - $ref: '#/components/schemas/errorType'
            - enum:
              - /silverflow/problems/report/entity-already-exists
          title:
            allOf:
            - $ref: '#/components/schemas/errorTitle'
            - enum:
              - Entity Already Exists
    openapi_components-schemas-ProblemDetail-2:
      type: object
      description: 'The ''problem detail'' object relays detailed information about the error that occurred. It is defined

        by [RFC 7807 - Problem Details for HTTP APIs](https://tools.ietf.org/html/rfc7807).


        Note that additional properties may be used to relay error specific information. For instance,

        A Bad Request error may hold information about the individual validation errors found in the request.

        '
      properties:
        type:
          type: string
          description: 'An absolute URI that identifies the problem type.

            '
          default: about:blank
          example: https://api.silverflow.co/problem/constraint-violation
        title:
          type: string
          description: 'A short, summary of the problem type. Written in english and readable

            for engineers (usually not suited for non technical stakeholders and

            not localized);

            '
          example: Service Unavailable
        status:
          type: integer
          format: int32
          description: 'The HTTP status code generated by the origin server for this occurrence

            of the problem.

            '
          minimum: 100
          maximum: 599
          example: 503
        detail:
          type: string
          description: 'A human readable explanation specific to this occurrence of the

            problem.

            '
          example: Connection to database timed out
        instance:
          type: string
          description: 'An absolute URI that identifies the specific occurrence of the problem.

            It may or may not yield further information if dereferenced.

            '
      additionalProperties: true
      example:
        type: https://api.silverflow.co/problem/bad-request
        title: Bad Request
        status: 400
        detail: The request could not be processed as it contained an invalid request entity
        instance: https://api.silverflow.co/v1/reports/rep-1hPdFqhgstYTUhlphPDp
        validationErrors:
        - The value of property 'status' should be one of 'idle', 'active' or 'archived'
        - The value of property 'tags.0.businessId' must not be longer than 255 characters
    errorTitle:
      type: string
      description: 'A short, human-readable summary of the problem type. It does not change from occurrence to occurrence of the error.

        '
    ChargesReportSchedule:
      allOf:
      - type: object
        required:
        - reportName
        properties:
          reportName:
            $ref: '#/components/schemas/ChargesReportName'
      - $ref: '#/components/schemas/BaseReportSchedule'
      - type: object
        required:
        - trigger
        - mimeType
        properties:
          mimeType:
            $ref: '#/components/schemas/chargesReportMimeType'
          trigger:
            $ref: '#/components/schemas/chargesScheduleTrigger'
    reportScheduleKey:
      description: Uniquely identifies a report schedule object
      type: string
      pattern: ^rsk-[a-zA-Z0-9]+$
      minLength: 10
      maxLength: 120
      example: rsk-1e1dAHhgstYTUhlphPzZ
    AgentKey:
      description: Uniquely identifies an Agent
      type: string
      pattern: ^cgt-[a-zA-Z0-9]+|current$
      readOnly: true
      example: cgt-1UF2NafdfrdPMf2XrS2
    ReconciliationDetailsReportName:
      type: string
      description: The name of the 

# --- truncated at 32 KB (70 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/silverflow/refs/heads/main/openapi/silverflow-report-scheduling-api-openapi.yml