Airweave API

Name: Airweave API API
Brand: Airweave API
Availability: InStock

★ Only Publicly Available SpecAI/MLEmbeddings SearchapiKey27 EndpointsREST

For Agents

Index data from SaaS sources into searchable collections, then run instant, classic, or agentic search to retrieve relevant content for an AI agent. Streaming agentic search is supported.

Quickstart

Get started with Airweave API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search across my connected SaaS data"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Airweave API API.

Create and manage collections that index data from connected SaaS sources

Configure source connections to sync from Notion, Slack, Google Drive, Stripe, and other platforms

Run instant keyword search across a collection for low-latency lookups

Run classic semantic search for embedding-based retrieval

GET STARTED

Start building with Airweave API API

Explore with Jentic

View OpenAPI Spec

Use for: I need to search across all my connected SaaS data, Run an agentic search and stream the response, Create a new collection that indexes my Notion workspace, List all source connections and their last sync status

Not supported: Does not host LLMs, generate embeddings as a standalone service, or run web crawls of arbitrary sites — use for SaaS-source ingestion and search only.

Jentic publishes the only available OpenAPI specification for Airweave API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Airweave API, keeping it validated and agent-ready. Airweave is a search and data-management platform that lets developers build retrieval over heterogeneous SaaS sources (Notion, Slack, Google Drive, Stripe, and more). The 27-endpoint API exposes collections (search-ready indexes), source connections (sync configurations), webhook ingestion, and three search modes — instant keyword search, classic semantic search, and agentic search with optional streaming. Authentication uses an x-api-key header.

Use Cases

Patterns agents use Airweave API API for, with concrete tasks.

★ Unified RAG over SaaS data

Build a retrieval-augmented application that searches across Notion, Slack, Google Drive, and other tools without writing per-source connectors. Airweave handles ingestion, embedding, and indexing into collections, and exposes search via instant, classic, and agentic modes.

Create a collection 'company-knowledge', attach a Notion source connection, and run a classic search for 'Q4 roadmap commitments'

Agentic enterprise search

Use the agentic search endpoint to let an AI agent plan a multi-step retrieval — for example, decomposing 'find the latest customer feedback on the new pricing page' into sub-queries across docs and chat. The streaming variant returns intermediate reasoning so a UI can render progress.

POST to /collections/{readable_id}/search/agentic/stream with the query 'recent customer complaints about pricing' and consume the stream

Sync orchestration and observability

Manage source connections programmatically — create, update, run, and cancel sync jobs, and list job history to surface failures. Useful when an agent operates a knowledge platform and must respond to ingestion incidents.

List sync jobs for source-connection {id}, identify the most recent failed job, and trigger a new run via POST /source-connections/{id}/run

AI agent integration via Jentic

Wire Airweave into a Jentic-powered agent so it can search company knowledge by intent. The agent loads the Airweave operation schema at runtime, the Jentic vault holds the API key, and the agent calls instant, classic, or agentic search depending on the latency and depth required.

Search Jentic for 'agentic search across SaaS data', load the matching Airweave operation, and execute against the user's collection

Key Endpoints

27 endpoints — jentic publishes the only available openapi specification for airweave api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/collections

Create a new collection

POST

/collections/{readable_id}/search/instant

Run instant keyword search

POST

/collections/{readable_id}/search/classic

Run classic semantic search

POST

/collections/{readable_id}/search/agentic

Run agentic multi-step search

POST

/collections/{readable_id}/search/agentic/stream

Stream agentic search results

POST

/source-connections

Create a source connection

POST

/source-connections/{source_connection_id}/run

Trigger a sync job

POST

/collections

Create a new collection

POST

/collections/{readable_id}/search/instant

Run instant keyword search

POST

/collections/{readable_id}/search/classic

Run classic semantic search

POST

/collections/{readable_id}/search/agentic

Run agentic multi-step search

POST

/collections/{readable_id}/search/agentic/stream

Stream agentic search results

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Airweave x-api-key tokens are stored encrypted in the Jentic vault. Agents receive scoped execution capabilities and never see the raw key.

Intent-based discovery

Agents search by intent (e.g., 'search across my SaaS data') and Jentic returns the matching Airweave operation with its input schema, so the agent calls the correct search mode without browsing docs.

Time to first call

Direct Airweave integration: 1-2 days to wire connectors, sync triggers, and search modes. Through Jentic: under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Pinecone

Pure vector database — you bring the connectors and embedding pipeline.

Choose Pinecone when you want a raw vector store and full control over ingestion. Choose Airweave when you want prebuilt SaaS connectors and managed sync.

Complementary

Notion API

Connect Notion as an Airweave source to make pages searchable.

Pair Notion with Airweave to index a workspace, then let the agent search across pages without managing Notion's API directly.

Complementary

OpenAI API

Generate the answer or summary from Airweave's retrieved context.

Pair OpenAI with Airweave for retrieval-then-generation flows: Airweave returns relevant chunks, OpenAI composes the response.

FAQs

Specific to using Airweave API API through Jentic.

Why is there no official OpenAPI spec for Airweave API?

Airweave does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Airweave API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Airweave API use?

Airweave uses an API key in the x-api-key header. Through Jentic, the API key is stored in the encrypted Jentic vault and injected at execution time, so the agent never sees the raw key.

What is the difference between instant, classic, and agentic search?

Instant search at /collections/{id}/search/instant is keyword-based and optimised for low latency. Classic search at /search/classic runs semantic embedding retrieval. Agentic search at /search/agentic plans multi-step queries and can be streamed via /search/agentic/stream for live UIs.

Can I run agentic search through Jentic?

Yes. Use the Jentic search query 'agentic search across collected data'. Jentic returns the POST /collections/{readable_id}/search/agentic operation with its input schema so the agent can pass the query and collection id directly.

How do I sync a new data source into Airweave?

Create a source connection via POST /source-connections with the source short name and credentials, then trigger a sync via POST /source-connections/{id}/run. Track progress with GET /source-connections/{id}/jobs.

Are webhooks supported for real-time ingestion?

Yes. The /webhooks resource exposes message listing endpoints used to inspect inbound events. Configure upstream sources to post to your Airweave webhook URL so changes propagate without waiting for a scheduled sync.