NovumOS Search API
The search API from NovumOS — 1 operation(s) for search.
The search API from NovumOS — 1 operation(s) for search.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/novumos-app:novumos-app-search-api"
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.
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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: NovumOS Search API
description: Block-based kanban where agents are first-class users.
version: 0.0.0
tags:
- name: Search
paths:
/v1/search:
post:
tags:
- Search
summary: Search
description: 'Full-text search across the caller''s org (spec §8.2).
NOV-457: the service still assembles the Notion-shape envelope as a dict —
the MCP wrapper consumes it in that form — so the router validates it into
the declared model. That is deliberate: the published schema is then the
same object the response is serialized from, rather than a promise made
alongside an untyped blob.'
operationId: search_v1_search_post
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/SearchRequest'
required: true
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/PaginatedResponse_SearchHitResponse_'
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
security:
- IntegrationToken: []
parameters:
- name: X-Board-Version
in: header
required: true
schema:
type: string
default: '2026-06-19'
description: Required on every `/v1` request. Send `2026-06-19`. The middleware validates *presence*, not the value, so an older pinned date keeps working; `Notion-Version` is accepted as a Notion-SDK compatibility fallback when this header is absent.
- name: X-Novum-Org
in: header
required: false
schema:
type: string
format: uuid
description: 'Optional. Selects the workspace this request acts in. An integration token is **pinned** to its own workspace, so a conflicting value returns `404`. For a browser session the value is re-checked against live membership on every request: it can only ever narrow to a workspace you already belong to, never widen. Omit it to act in the session''s active workspace.'
components:
schemas:
SearchRequest:
properties:
query:
type: string
maxLength: 500
minLength: 1
title: Query
types:
anyOf:
- items:
type: string
const: card
type: array
- type: 'null'
title: Types
board_id:
anyOf:
- type: string
format: uuid
- type: 'null'
title: Board Id
page_size:
anyOf:
- type: integer
maximum: 100.0
minimum: 1.0
- type: 'null'
title: Page Size
start_cursor:
anyOf:
- type: string
- type: 'null'
title: Start Cursor
additionalProperties: false
type: object
required:
- query
title: SearchRequest
AgentActivity:
properties:
agent_name:
type: string
title: Agent Name
doing:
type: string
title: Doing
started_at:
anyOf:
- type: string
format: date-time
- type: 'null'
title: Started At
additionalProperties: false
type: object
required:
- agent_name
- doing
title: AgentActivity
description: 'NOV-86 / NOV-91: "an agent is working on this card right now" payload.
Stored as ``cards.agent_activity`` JSONB. Set via
``POST /v1/cards/{id}/agent_activity``, cleared via the matching
DELETE, the next mutation on the card, or a 10-minute TTL on read
(NOV-91 lifecycle).
The model is strict (``extra="forbid"`` + required fields) but
``started_at`` is optional so legacy blobs written before NOV-91
don''t fail validation. The outer ``CardResponse.agent_activity``
validator silently downgrades a malformed stored blob to ``None``
so a bad write from the agent runtime can''t 500 every card read.'
SearchResultMeta:
properties:
score:
type: number
title: Score
highlight:
anyOf:
- type: string
- type: 'null'
title: Highlight
additionalProperties: false
type: object
required:
- score
title: SearchResultMeta
description: 'Search-only envelope attached to result objects under the `_search` key.
Kept off the canonical Card shape so result consumers can ignore it and
callers wanting ranking signal can pluck it out.'
PaginatedResponse_SearchHitResponse_:
properties:
object:
type: string
title: Object
default: list
results:
items:
$ref: '#/components/schemas/SearchHitResponse'
type: array
title: Results
has_more:
type: boolean
title: Has More
default: false
next_cursor:
anyOf:
- type: string
- type: 'null'
title: Next Cursor
page_size:
type: integer
title: Page Size
default: 25
type: object
required:
- results
title: PaginatedResponse[SearchHitResponse]
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
SearchHitResponse:
properties:
object:
type: string
title: Object
default: card
id:
type: string
format: uuid
title: Id
board_id:
type: string
format: uuid
title: Board Id
column_id:
anyOf:
- type: string
format: uuid
- type: 'null'
title: Column Id
title:
type: string
title: Title
properties:
additionalProperties: true
type: object
title: Properties
position:
type: number
title: Position
assignees:
items:
type: string
type: array
title: Assignees
due_date:
anyOf:
- additionalProperties: true
type: object
- type: 'null'
title: Due Date
labels:
items:
additionalProperties: true
type: object
type: array
title: Labels
is_archived:
type: boolean
title: Is Archived
agent_activity:
anyOf:
- $ref: '#/components/schemas/AgentActivity'
- type: 'null'
created_time:
type: string
format: date-time
title: Created Time
last_edited_time:
type: string
format: date-time
title: Last Edited Time
body_last_edited_time:
anyOf:
- type: string
format: date-time
- type: 'null'
title: Body Last Edited Time
etag:
type: integer
title: Etag
attachment_count:
type: integer
title: Attachment Count
default: 0
unique_id:
anyOf:
- type: string
- type: 'null'
title: Unique Id
_search:
$ref: '#/components/schemas/SearchResultMeta'
additionalProperties: false
type: object
required:
- id
- board_id
- title
- properties
- position
- assignees
- labels
- is_archived
- created_time
- last_edited_time
- etag
- _search
title: SearchHitResponse
description: 'One ``POST /v1/search`` result: a card PLUS its relevance block (NOV-457).
A search hit is a full ``CardResponse`` with one extra key — it is NOT a
different object, so this subclasses the card rather than wrapping it. That
keeps the wire flat (the hit *is* the card) and means every card field stays
in one place; adding a field to ``CardResponse`` reaches search for free.
``_search`` cannot be a Python field name — pydantic reserves the leading
underscore for private attributes — so the field is ``search`` carrying an
explicit alias. FastAPI serializes response models with ``by_alias=True``,
and ``populate_by_name`` (inherited from ``APIModel``) lets the service''s
hand-built ``{"_search": ...}`` dict validate, so the key crosses the wire
unchanged in both directions.'
securitySchemes:
IntegrationToken:
type: http
scheme: bearer
description: 'Integration token. Mint one in the app under **Settings → Integrations** and paste the `nov_…` value here. It is sent as `Authorization: Bearer nov_…`, the same credential the API enforces. Browser session cookies are NOT used by try-it-out (the cookie flow additionally requires an `X-CSRF-Token` header this page cannot mint).'