Fluxito

Fluxito Reports API

The Reports API from Fluxito — 2 operation(s) for reports.

GitHub OpenAPI

Operations 2

GET /api/reports/schedules List Project Schedules #
GET /reports/schedules Reports Schedules Page #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/fluxito-app/openapi/fluxito-app-reports-api-openapi.yml

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/fluxito-app:fluxito-app-reports-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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

fluxito-app-reports-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Fluxito Platform Reports API
  version: 3.0.120
tags:
- name: Reports
paths:
  /api/reports/schedules:
    get:
      summary: List Project Schedules
      description: 'List every ReportSchedule across the caller''s active project.


        The per-dashboard CRUD endpoints above stay authoritative for

        mutations; this is the single project-scoped read the /reports/schedules

        page needs so it doesn''t have to fan out one request per dashboard.

        Each row carries its ``dashboard_id`` so the page can call the existing

        dashboard-scoped PATCH/DELETE/run endpoints directly.'
      operationId: list_project_schedules_api_reports_schedules_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Reports
  /reports/schedules:
    get:
      summary: Reports Schedules Page
      description: 'The standalone Scheduled reports page merged into the Dashboards hub

        (site revamp) — it is now the #schedules tab there. Redirect old links.'
      operationId: reports_schedules_page_reports_schedules_get
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
      tags:
      - Reports