> ## Documentation Index
> Fetch the complete documentation index at: https://flowdrop.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> The REST API that FlowDrop expects your backend to implement.

FlowDrop is a frontend editor — it talks to **your backend** over a REST API.
This reference documents that contract: the endpoints FlowDrop calls to discover
node types, persist workflows, run pipelines, and resolve port compatibility.

You implement these endpoints (or run a ready-made [server
implementation](/server-implementations/overview)); FlowDrop calls them.

<Card title="OpenAPI specification" icon="file-code" href="https://github.com/flowdrop-io/flowdrop/blob/main/libs/flowdrop/api/v1/openapi.yaml">
  The spec is maintained alongside the library. The endpoint pages in this
  section are generated from it.
</Card>

## Base URL

FlowDrop targets a single base path that you configure with
`createEndpointConfig('/api/flowdrop')`. All endpoint paths in this reference are
relative to that base — for example, `GET /nodes` resolves to
`/api/flowdrop/nodes`.

## Authentication

The API supports two authentication schemes, applied per your deployment:

* **`BearerAuth`** — an `Authorization: Bearer <token>` header (JWT). In the
  editor, supply tokens through an [`AuthProvider`](/guides/integration/authentication-patterns)
  (for example `StaticAuthProvider` or `CallbackAuthProvider`).
* **`SessionAuth`** — a session cookie (`SESS`), for same-origin deployments
  that rely on an existing session.

Use whichever your backend enforces; FlowDrop attaches credentials via the
configured `AuthProvider`.

## Endpoints

The pages under **Endpoints** are generated directly from the OpenAPI
specification and cover workflow CRUD, node-type discovery, pipeline execution
and status, port configuration, and import/export.