JouView for your AI

What your AI can do

All of this goes through https://jouview.com/api/journal/* (see the agent sections below and the OpenAPI schema).

For you (human)

1. Sign inAccount with Google.
2. Create a tokenUse the button below, then paste the token into your AI only if it can call APIs (see the prompt).
3. Ask your AI to personalizeCopy the prompt, fill in your task, and send it to any AI you use. Or attach CSVs/exports/screenshots to import an existing journal into JouView.
4. Refresh JouViewAfter the AI finishes, open the JouView menu (bottom tab) and press Refresh so the journal picks up the new columns, styles or changes.

I want you to modify my JouView journal via the Journal API.

Read https://jouview.com/ai-usage/

My token (keep private): <PASTE_jvtr_TOKEN>

What I want done:
<DESCRIBE_TASK>

Usage recipes

Concrete tasks your AI should follow. Transferring an old journal is only one of them.

GET /api/journal/columns
PUT /api/journal/columns
{
  "replaceCustom": false,
  "columns": [
    { "name": "Setup", "type": "text", "enumValues": "CBreak, Impulse, Bias" },
    { "name": "Planned", "type": "bool" },
    {
      "name": "Score",
      "type": "number",
      "formula": "([Planned] === \"true\" ? 1 : 0) + ([Retest] === \"true\" ? 1 : 0)"
    }
  ]
}

GET /api/journal/row-styles
PUT /api/journal/row-styles
{
  "rules": [
    {
      "BackgroundColor": "[Profit] < 0 ? \"#3d1f1f\" : \"\"",
      "TextColor": "[Profit] > 0 ? \"#26a69a\" : \"#ef5350\"",
      "Bold": "[Score] >= 3"
    }
  ]
}

GET /api/journal/entries?take=200
GET /api/journal/columns

POST /api/journal/entries
{
  "symbol": "ES",
  "quantity": 2,
  "entryPrice": 5200.25,
  "entryTime": "2024-06-12T14:32:00Z",
  "exitPrice": 5210.5,
  "exitTime": "2024-06-12T15:10:00Z",
  "externalId": "manual-2024-06-12-es-1",
  "fields": { "Setup": "CBreak", "Planned": "1", "Profit": "420", "Notes": "Clean retest" }
}

POST /api/journal/reset
{ "removeImportedEntries": true }

Concepts

• Entry / position: one trade row. Core facts: symbol, quantity, entryPrice, entryTime, exitPrice, exitTime.
• Column: a grid field. Custom columns hold playbook data (setup, checklist, tags). System columns are seeded by JouView.
• fields{}: map of columnName → value on an entry. Unknown names are skipped and returned in unknownFields.
• Computed cell: column with formula. The UI evaluates it. You usually don't need to also write fields[ThatColumn].
• Cell style: per-column params: textColor, backgroundColor, bold, and so on.
• Row style: rules from PUT /api/journal/row-styles. They apply to the whole row. Cell styles override per channel.
• externalId: stable source id. Same externalId + import broker key upserts the same row.

System columns (read-only identity)

Created automatically. isSystem: true. You cannot rename, retype, or delete them via this API. You can reorder them by including their names in PUT /columns. Do not create custom columns with these names.

Column types & allowed JSON values

Enums

enumValues: comma-separated choices, e.g. "CBreak, Impulse, Bias". Set enumMultiValue: true only if the user needs multi-select. Not allowed on bool / richtext / stars / group / actions.

Column JSON properties (PUT /columns)

{
  "name": "Setup",
  "type": "text",
  "visible": true,
  "sortable": true,
  "formula": null,
  "enumValues": "CBreak, Impulse, Bias",
  "enumMultiValue": false,
  "textColor": null,
  "backgroundColor": null,
  "bold": null,
  "italic": null,
  "underline": null,
  "fontSize": null,
  "textAlign": null,
  "displayFormat": null,
  "groupMembers": null,
  "groupSummaryColumn": null
}

Row styles & cell styles

Style channels: BackgroundColor, TextColor, FontSize, Bold, Italic, Underline, TextAlign.

• Literals: "#26a69a", "12", "true", "left"
• Or formulas: [Profit] > 0 ? "#26a69a" : "#ef5350"
• Row rules: ordered list. The first rule that sets a channel wins for that channel.
• Cell styles (on the column) override the row for that cell

PUT /api/journal/row-styles
{
  "rules": [
    {
      "BackgroundColor": "[Profit] < 0 ? \"#3d1f1f\" : \"\"",
      "TextColor": "[Profit] > 0 ? \"#26a69a\" : \"#ef5350\"",
      "Bold": "[Score] >= 3"
    }
  ]
}

Groups (optional: one level)

Prefer flat columns for imports. If the user wants a packed checklist cell:

{
  "name": "Checklist pack",
  "type": "group",
  "groupMembers": ["Planned", "Retest", "Liquidity"],
  "groupSummaryColumn": "Planned",
  "formula": "[Planned] + [Retest] + [Liquidity]"
}

• Members hide from the main grid. Double-click opens them.
• A column belongs to at most one group
• Groups can't nest inside other groups
• groupSummaryColumn must be one of the members

Chart snapshots

JouView's snapshot viewer stores a SnapshotUrl per image on a trade. Choose the lightest option that works:

• TradingView (preferred when applicable): if the chart is already at https://tradingview.com/x/{id}, pass only the {id} suffix in snapshots[]. The viewer prefixes https://tradingview.com/x/. Full tradingview.com/x/... URLs are accepted and normalized to the id. These do not count toward the upload limit.
• External https URL: any permanent image URL whose host is not jouview.com. Store the full URL as-is. It doesn't use any upload. It doesn't use any quota.
• Upload to JouView: only when you must host the file on jouview.com (local file / private blob). That is the only case that uses the hosted-upload quota (Trader is effectively unlimited).

1. Upload the image file (only if hosting on JouView)

POST /api/journal/snapshots/upload
Authorization: Bearer jvtr_...
Content-Type: multipart/form-data

[email protected]

→ {
  "url": "https://jouview.com/media/snapshots/{userId}/{fileId}.png",
  "path": "/media/snapshots/{userId}/{fileId}.png",
  "snapshotUrl": "https://jouview.com/media/snapshots/...",
  "uploadedCount": 12,
  "remainingUploads": 9988,
  "maxUploadsPerUser": …
}

Max 10 MB per file. Types: png, jpg, jpeg, webp, gif. Public GET at the returned URL. TradingView ids and non-jouview.com https URLs do not consume quota. Trader hosted uploads are effectively unlimited.

2. Attach to a trade

PUT /api/journal/entries/{positionId}/snapshots
{
  "replace": true,
  "snapshots": [
    "AbCdEfGh",
    "https://some-other-cdn.example/chart.jpg",
    "https://jouview.com/media/snapshots/.../....png"
  ]
}

Or include "snapshots": [ "..." ] on POST /api/journal/entries. replace: false appends. Attaching never increments the upload quota.

Endpoints

{
  "replaceCustom": false,
  "columns": [
    { "name": "Trade" },
    { "name": "Setup", "type": "text", "enumValues": "CBreak, Impulse, Bias" },
    { "name": "Planned", "type": "bool" },
    { "name": "Retest", "type": "bool" },
    { "name": "Liquidity", "type": "bool" },
    {
      "name": "Score",
      "type": "number",
      "formula": "[Planned] + [Retest] + [Liquidity]",
      "textColor": "[Score] >= 3 ? \"#26a69a\" : \"#ef5350\""
    },
    { "name": "Grade", "type": "stars" },
    {
      "name": "Profit",
      "textColor": "[Profit] > 0 ? \"#26a69a\" : \"#ef5350\"",
      "displayFormat": "0.00"
    },
    { "name": "Notes" }
  ]
}

{
  "symbol": "ES",
  "quantity": 2,
  "entryPrice": 5200.25,
  "entryTime": "2024-06-12T14:32:00Z",
  "exitPrice": 5210.5,
  "exitTime": "2024-06-12T15:10:00Z",
  "accountCurrency": "USD",
  "externalId": "source-row-42",
  "fields": {
    "Setup": "CBreak",
    "Planned": "1",
    "Retest": "1",
    "Liquidity": "0",
    "Grade": "4",
    "Profit": "420",
    "Risk": "100",
    "Notes": "Clean retest"
  }
}

HTTP status & edge cases

• API failures return a JSON body with the exception message and context (type, path, method, traceId, stackTrace, innerExceptions). Use that when filing support reports.
• Reusing externalId upserts. Changing it creates another row.
• Only soft-deletes via reset affect brokerKey=ai-transfer rows. Broker-synced trades are left alone.
• Column names max 50 chars. They must be unique per user (case-insensitive).

Limits & security

Enforced server-side. Full numbers live in limits on /api/journal/openapi.json.

• Tokens (agents): max 1 hour. Auth via Authorization: Bearer or ?access_token=. First successful call binds the token to that client IP for the rest of its life. Other IPs get 401. Legacy long-lived tokens are rejected.
• Rate limits (429): per token user (else IP): schema 600/min, reads 1200/min, writes 400/min, uploads 100/min, token mint 100/hour, reset 60/hour. Response may include Retry-After.
• Columns: max 800 per PUT, 800 custom, 1000 total with system. Max 400 value formulas and 800 style expressions per PUT. Each expression is <= 40000 chars.
• Row styles: max 200 rules / 400 expressions.
• Entries: max 2000 per batch. Field values are length-capped. Max 200 snapshots per trade.
• Injection guard: formulas/styles reject host APIs (fetch, eval, document, window, and so on) and script-like patterns. Column names use a safe charset. The server rejects control characters.
• Body size: JSON requests capped at 10 MB (uploads use the separate photo size limit).

Start again from scratch

POST /api/journal/reset
{
  "removeCustomColumns": true,
  "removeImportedEntries": true,
  "clearRowStyles": true
}

Then PUT /columns with replaceCustom: true and re-import entries. Does not delete the JouView account. Set only the flags you need.

Formulas

Full formula language for computed cells, style channels, and row rules. Humans edit these in Settings → Journal columns → pen (or Row styles). AI agents set the same strings on PUT /columns / PUT /row-styles.

What a formula is

A formula is one JavaScript expression. It runs in a sandbox for a single journal row (and, when you ask for it, across other rows via ROWS). You attach formulas in Settings → Journal columns → pen:

• Formula: the value the cell shows (custom columns only). System columns like Profit keep their own logic.
• Style fields: bold, italic, underline, font size, text color, background, align. Each can be fixed or a formula.

Row styles use the same language for whole-trade chrome. Styles never change stored values.

Syntax

• Column references: [Column name]. Names are not case-sensitive. Spacing matters: [Row number] works. [RowNumber] does not.
• Maths: + - * / % and parentheses, e.g. ([A] + [B]) / 2.
• Text: + joins strings. Put literals in quotes: "Long", not Long.
• Choices: ternary only: condition ? whenTrue : whenFalse. JouView doesn't have any IF().
• Comparisons: always === / !== (never a single =), plus < <= > >=, &&, ||, !.
• JavaScript helpers: Math, Number, String, .toFixed, .includes, .split, Date.parse, arrow functions, and so on. The sandbox doesn't allow network, browser storage, or page DOM access.

Empty cells count as 0 when they look numeric to the engine. That keeps [A] + [B] arithmetic when one side is blank. When joining text that may be blank, write ([Notes] || "") + " - done".

Fields you can read

Any journal column as [Name], plus these always-available names (even without a matching column):

Times use the chart timezone. Prefer [Entry date] / [Today] for "same day" bands instead of slicing a UTC stamp.

Style formulas

Same language as value formulas. Typical patterns:

The second example is a Bold/Italic condition: truthy turns the style on. Leave a style field blank to inherit the row rule (or the grid default). false / 0 turns Bold/Italic/Underline off.

Display format (numbers/dates) is a mask such as 0.00 or dd/mm/yyyy HH:mm. It changes how the value is shown, not what is stored.

Yes/No, dropdowns, multivalue

Yes/No columns compare as the text "true" / "false":

Dropdown values are set in the pen panel (comma-separated). Compare with === "A+". Tick Multivalue to allow several checked options. Then treat the cell as a comma list:

Groups and stars

A Group column collapses several members into one journal cell (double-click to edit members). Its Formula can sum the members into a points total. A separate Stars column often maps that total onto 0-5:

Tune the min/max in the map to your real score range so a typical "good" trade lands around 4-5 stars.

Cross-row work with ROWS

ROWS is an array of every trade in the journal. Each element is an object keyed by column name (same names as [Brackets]). Use it for averages, streaks, session reviews, and account stats.

Arrow functions and .filter / .map / .reduce are the usual tools. Keep review rows out of averages with Setup tags such as session review / day review.

Build a checklist (power-user pattern)

Many small inputs → points → stars → optional review averages. Start small. Grow the point list over time.

1. Inputs: Yes/No or dropdown columns for each criterion (e.g. Planned, Retest, Liquidity). Optional Yes/No Checklist Done if you only want a score after finishing the list.

2. Direction helper

3. Points group: Group (or number) column whose Formula adds weighted signals:

4. Stars score: map the raw total onto 0-5 when the checklist is finished:

Replace -20 / 40 with your real min score and the span from max to min after a week of trades.

5. Skip non-trades and average reviews: use a Setup dropdown with values like Bias, Session review, Day review:

6. Color the score: background formula on the stars column:

More examples

When a formula breaks

A cell that cannot be evaluated shows ERR. Hover it: the tooltip names the problem, lists every referenced value with its type, and suggests a fix. Common causes:

• Single = instead of ===
• Missing quotes around text
• Calling a string method on a number (or the reverse). Wrap with String(...) / Number(...).
• Referring to a column that was renamed
• A circular reference between formula columns

After you save a formula it can take a moment to appear. Open JouView → How to on the chart for the live field list of your columns.

Live machine schema

Agents should fetch and follow this JSON (includes OpenAPI-style paths, components.schemas, catalogs, workflows):

Open /api/journal/openapi.json Preview below

Click "Preview below" to load the live schema...

After the AI finishes

Open the JouView menu (bottom tab) and press Refresh so the journal picks up the new columns, styles or changes. Then confirm the journal and adjust anything in Settings.