Baserow

Baserow Secure file serve API

The Secure file serve API from Baserow — 1 operation(s) for secure file serve.

Documentation GitHub OpenAPI

Operations 1

GET /api/files/{signed_data} Secure file serve download #

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/baserow:baserow-secure-file-serve-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

openapi: 3.2.0
info:
  title: Baserow API spec Secure file serve API
  version: 2.2.2
  description: 'For more information about our REST API, please visit this page.


    For more information about our deprecation policy, please visit this page.'
  contact:
    url: https://baserow.io/contact
  license:
    name: MIT
    url: https://github.com/baserow/baserow/blob/develop/LICENSE
tags:
- name: Secure file serve
paths:
  /api/files/{signed_data}:
    get:
      operationId: secure_file_serve_download
      description: 'Downloads a file using the backend and the secure file serve feature. The signed data is extracted from the URL and used to verify if the user has access to the file. If the permissions check passes and the file exists, the file is served to the user.


        This is a **enterprise** feature.'
      parameters:
      - in: path
        name: signed_data
        schema:
          type: string
          pattern: ^.*$
        required: true
      tags:
      - Secure file serve
      responses:
        '200':
          content:
            application/octet-stream:
              schema:
                description: File download
          description: ''
        '403':
          content:
            application/octet-stream:
              schema:
                type: object
                properties:
                  error:
                    type: string
                    description: Machine readable error indicating what went wrong.
                    enum:
                    - ERROR_SECURE_FILE_SERVE_EXCEPTION
                  detail:
                    oneOf:
                    - type: string
                      format: string
                      description: Human readable details about what went wrong.
                    - type: object
                      format: object
                      description: Machine readable object about what went wrong.
          description: ''
      summary: Secure file serve download
      x-summary-source: derived
components:
  securitySchemes:
    Database_token:
      type: http
      scheme: bearer
      bearerFormat: Token your_token
    JWT:
      type: http
      scheme: bearer
      bearerFormat: JWT your_token
    UserSource_JWT:
      type: http
      scheme: bearer
      bearerFormat: JWT your_token

Baserow Secure file serve API

Operations 1

Documentation

Specifications

Schemas & Data

Other Resources