Skip to main content
POST
/
api
/
v1
/
context
/
notes
Create a note context item
curl --request POST \
  --url https://api.staging.getmodus.com/api/v1/context/notes \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "title": "Q3 churn analysis",
  "content": "## Findings\n\nChurn rate increased 2.3% MoM."
}
'
{
  "contextItemId": "7a3f9d2c-1111-4000-a000-000000000abc",
  "kind": "note",
  "s3Key": "context_notes/7a3f9d2c.../Q3_churn_analysis.md",
  "title": "Q3 churn analysis"
}

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
title
string
required

Display title for the note. Used in the SPA list and as the s3 object filename.

Example:

"Q3 churn analysis"

content
string
required

Note body — markdown text. Stored in tenant S3 + context_items.

Example:

"## Findings\n\nChurn rate increased 2.3% MoM."

Response

contextItemId
string
required

UUID of the newly-created context item. Use it on subsequent GET / PATCH / DELETE calls.

Example:

"7a3f9d2c-1111-4000-a000-000000000abc"

kind
enum<string>
required

Kind of context item created.

Available options:
note,
saved_query,
link,
dimension,
fact,
metric,
filter
Example:

"note"

s3Key
string | null

Tenant S3 key for the raw content blob (notes, saved queries, links). Null for kinds without S3 backing.

Example:

"context_notes/7a3f9d2c.../Q3_churn_analysis.md"

title
string | null

Resolved title for the created item. Null for kinds without a title field.

Example:

"Q3 churn analysis"