Skip to main content
GET
List extraction flows

Authorizations

Authorization
string
header
required

Use Authorization: Bearer <token>. The token is either a user token / OAuth access token, or a service-account API key (cfk_...). A key is valid on every endpoint and acts as its service account, an organization member with per-store permissions. Refused keys answer 403 with Invalid API key., API key revoked., API key expired. or API key disabled..

Path Parameters

project_id
string<uuid>
required

UUID of the project

Response

Successful response

id
string<uuid>
name
string
publish_mode
enum<string>
  • auto_publish — runs automatically push extracted data to downstream indexes.
  • manual_publish — publishing is triggered explicitly via the publish action.
Available options:
auto_publish,
manual_publish
dag
object

DAG describing the extractor pipeline. PATCH replaces the stored DAG verbatim — there is no node-level patch endpoint.

tpuf_namespaces
object

Per-namespace-type TurboPuffer namespace mapping populated on publish.

last_pushed_to_tpuf
string<date-time> | null
created_at
string<date-time>
updated_at
string<date-time>