Flowra Browser API

Live browser sessions and view

GitHub OpenAPI

Operations 4

POST /api/v1/browser/sessions/{sessionId}/close Close live browser session #
GET /api/v1/browser/sessions/{sessionId}/status Browser session status #
POST /api/v1/browser/sessions/{sessionId}/touch Heartbeat for open browser panel #
GET /api/v1/browser/sessions/{sessionId}/view Live browser panel (iframe) #

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/flowra-dev:flowra-dev-browser-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.

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

OpenAPI Specification

flowra-dev-browser-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Flowra API (API Key Endpoints) Browser API
  description: '**Flowra** is an AI-powered platform for building agents, workflows, and integrations.


    ### Capabilities

    - **Tools & Toolkits** – Define and group tools for agents and workflows.

    - **Workflows** – Orchestrate steps and automate processes.

    - **Triggers** – Schedule or event-based execution.

    - **Auth & Connections** – OAuth, API keys, and connected accounts.

    - **MCP** – Model Context Protocol server integration.

    - **Knowledge / RAG** – Add files and URLs for retrieval-augmented generation.


    ### Authentication

    Use the **x-api-key** header with a project API key to access endpoints that support API Key auth. Create and manage API keys in the dashboard under your project settings.


    Only endpoints that support API Key authentication via the @ApiKeyEnabled() decorator.


    Send x-api-key (required). On multi-tenant endpoints, optionally send x-username to act as an external user.'
  version: '1.0'
  contact:
    name: Flowra
    url: https://flowra.dev
servers:
- url: https://flowra.dev
  description: Flowra API
tags:
- name: Browser
  description: Live browser sessions and view
paths:
  /api/v1/browser/sessions/{sessionId}/close:
    post:
      operationId: BrowserController_browserClose
      x-apiKeyEnabled: true
      summary: Close live browser session
      description: Flushes profile when possible, stops billing, and ends the Browserbase session.
      parameters:
      - name: sessionId
        required: true
        in: path
        description: Browser session id (chat thread id or standalone session id)
        schema:
          example: b737d8af-a9e0-4251-9714-3fdc1126e5fb
          type: string
      - name: x-username
        in: header
        required: false
        description: External user (end user) to act as. Optional — if omitted, Flowra uses the project’s default external user. Send a stable username (e.g. customer_alice) only when you need another end-user context.
        schema:
          type: string
          default: (project default user)
        example: customer_alice
      responses:
        '200':
          description: Operation completed successfully
        '201':
          description: ''
      tags:
      - Browser
      security:
      - x-api-key: []
      - x-api-key: []
        x-username: []
  /api/v1/browser/sessions/{sessionId}/status:
    get:
      operationId: BrowserController_browserStatus
      x-apiKeyEnabled: true
      summary: Browser session status
      description: Alive flag, live-pulse, and official liveViewUrl when available.
      parameters:
      - name: sessionId
        required: true
        in: path
        description: Browser session id (chat thread id or standalone session id)
        schema:
          example: b737d8af-a9e0-4251-9714-3fdc1126e5fb
          type: string
      - name: x-username
        in: header
        required: false
        description: External user (end user) to act as. Optional — if omitted, Flowra uses the project’s default external user. Send a stable username (e.g. customer_alice) only when you need another end-user context.
        schema:
          type: string
          default: (project default user)
        example: customer_alice
      responses:
        '200':
          description: Operation completed successfully
      tags:
      - Browser
      security:
      - x-api-key: []
      - x-api-key: []
        x-username: []
  /api/v1/browser/sessions/{sessionId}/touch:
    post:
      operationId: BrowserController_browserTouch
      x-apiKeyEnabled: true
      summary: Heartbeat for open browser panel
      description: Keeps the Live pulse fresh while the panel is open (including minimized). Does not extend hosted-session idle lifetime — idle is based on agent/user activity.
      parameters:
      - name: sessionId
        required: true
        in: path
        description: Browser session id (chat thread id or standalone session id)
        schema:
          example: b737d8af-a9e0-4251-9714-3fdc1126e5fb
          type: string
      - name: x-username
        in: header
        required: false
        description: External user (end user) to act as. Optional — if omitted, Flowra uses the project’s default external user. Send a stable username (e.g. customer_alice) only when you need another end-user context.
        schema:
          type: string
          default: (project default user)
        example: customer_alice
      responses:
        '200':
          description: Operation completed successfully
        '201':
          description: ''
          content:
            application/json:
              schema:
                type: object
      tags:
      - Browser
      security:
      - x-api-key: []
      - x-api-key: []
        x-username: []
  /api/v1/browser/sessions/{sessionId}/view:
    get:
      operationId: BrowserController_browserView
      x-apiKeyEnabled: true
      summary: Live browser panel (iframe)
      description: Embeds the live browser viewer for this session. Requires auth.
      parameters:
      - name: sessionId
        required: true
        in: path
        description: Browser session id (chat thread id or standalone session id)
        schema:
          example: b737d8af-a9e0-4251-9714-3fdc1126e5fb
          type: string
      - name: x-username
        in: header
        required: false
        description: External user (end user) to act as. Optional — if omitted, Flowra uses the project’s default external user. Send a stable username (e.g. customer_alice) only when you need another end-user context.
        schema:
          type: string
          default: (project default user)
        example: customer_alice
      responses:
        '200':
          description: Operation completed successfully
      tags:
      - Browser
      security:
      - x-api-key: []
      - x-api-key: []
        x-username: []
components:
  securitySchemes:
    x-api-key:
      type: apiKey
      in: header
      name: x-api-key
      description: 'Project API key. Create and manage keys in the dashboard under Project → API Keys. Send as header: x-api-key: <your-key>'
    x-username:
      type: apiKey
      in: header
      name: x-username
      description: 'Optional. External user username. If omitted, Flowra uses the project’s default external user. Send as header: x-username: <username>'