Search for code artifacts (Auth policies: ApiKeyOrJwt)

curl --request GET \
  --url https://app.codealive.ai/api/search \
  --header 'Authorization: Bearer <token>'

{
  "results": [
    {
      "kind": "<string>",
      "dataSource": {
        "type": "<string>",
        "id": "<string>",
        "name": "<string>"
      },
      "identifier": "<string>",
      "location": {
        "path": "<string>",
        "range": {
          "start": {
            "line": 123,
            "character": 123
          },
          "end": {
            "line": 123,
            "character": 123
          }
        }
      },
      "score": 123,
      "description": "<string>",
      "contentByteSize": 123,
      "snippet": "<string>",
      "content": "<string>"
    }
  ],
  "pathFilter": "<unknown>"
}

Search for code artifacts (Auth policies: ApiKeyOrJwt)

deprecated

Sample requests:

Basic search with IDs: GET /api/search?Query=how%20to%20connect%20to%20database&DataSourceIds=67f664fd4c2a00698a52bb6f&Mode=fast

Search with workspace/repository names: GET /api/search?Query=authentication&Names=MyWorkspace&Names=my-repository&Mode=auto

Mixed search (IDs and names): GET /api/search?Query=user%20service&DataSourceIds=67f664fd4c2a00698a52bb6f&Names=MyWorkspace&Mode=auto

Mode=auto: Intelligent search mode (recommended)
Mode=fast: Quick search for exact matches
Mode=deep: Thorough semantic analysis (use sparingly)
IncludeContent=true: Include full file content in results
DescriptionDetail=Short|Full: Control summary detail level
DataSourceIds: Specify data sources by their IDs
Names: Specify data sources by workspace or repository names (case-insensitive)

Legacy compatibility note: This endpoint is intentionally kept for older MCP clients, prompts, and API integrations that still call /api/search with Mode and DescriptionDetail. New integrations must use /api/search/semantic or /api/search/grep instead. The split matters because the canonical endpoints separate semantic retrieval from exact/regex search, while this legacy route bundles multiple search behaviors behind one surface and therefore exposes policy knobs that newer clients should not depend on. As part of that compatibility contract, Mode is accepted but ignored: legacy callers may still send it, but the endpoint now always executes the fast path to keep behavior stable, cheap, and predictably backward-compatible while canonical routes own the richer strategy selection.

GET

api

Search for code artifacts (Auth policies: ApiKeyOrJwt)

curl --request GET \
  --url https://app.codealive.ai/api/search \
  --header 'Authorization: Bearer <token>'

{
  "results": [
    {
      "kind": "<string>",
      "dataSource": {
        "type": "<string>",
        "id": "<string>",
        "name": "<string>"
      },
      "identifier": "<string>",
      "location": {
        "path": "<string>",
        "range": {
          "start": {
            "line": 123,
            "character": 123
          },
          "end": {
            "line": 123,
            "character": 123
          }
        }
      },
      "score": 123,
      "description": "<string>",
      "contentByteSize": 123,
      "snippet": "<string>",
      "content": "<string>"
    }
  ],
  "pathFilter": "<unknown>"
}

Authorizations

Authorization

string

header

required

API Key authentication using Bearer token. Example: "Authorization: Bearer {apiKey}"

Headers

CodeAlive-Version

string

Query Parameters

Query

string

DataSourceIds

string[]

Names

string[]

Mode

enum<string>

Available options:

Auto,

Fast,

FastComplex,

Deep

IncludeContent

boolean

DescriptionDetail

enum<string>

Available options:

Short,

Full

Limit

integer<int32>

Response

results

object[] | null

Show child attributes

pathFilter

any

Dify External Knowledge API - Retrieval endpoint. Searches CodeAlive repositories and workspaces for relevant code artifacts. (Auth policies: ApiKeyOrJwt) (Auth policies: ApiKeyOrJwt)