journalize-dev Journal API
The Journal API from journalize-dev — 3 operation(s) for journal.
The Journal API from journalize-dev — 3 operation(s) for journal.
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/journalize-dev:journalize-dev-journal-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. 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: journalize Journal API
contact:
name: Journalize
email: hello@journalize.dev
version: 0.1.0
tags:
- name: Journal
paths:
/journal/directives:
post:
summary: Submit Directive
operationId: submit_directive_journal_directives_post
parameters:
- name: X-Public-Key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Public-Key
- name: X-Nonce
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Nonce
- name: X-Timestamp
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Timestamp
- name: X-Signature
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Signature
- name: X-PAYMENT
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Payment
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/DirectiveSubmitRequest'
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/DirectiveWriteResponse'
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Journal
get:
summary: List Directives
operationId: list_directives_journal_directives_get
parameters:
- name: account
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: Account
- name: since
in: query
required: false
schema:
anyOf:
- type: string
format: date
- type: 'null'
title: Since
- name: until
in: query
required: false
schema:
anyOf:
- type: string
format: date
- type: 'null'
title: Until
- name: limit
in: query
required: false
schema:
type: integer
default: 100
title: Limit
- name: X-Public-Key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Public-Key
- name: X-Nonce
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Nonce
- name: X-Timestamp
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Timestamp
- name: X-Signature
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Signature
- name: X-PAYMENT
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Payment
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/DirectiveListResponse'
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Journal
/journal/directives/validate:
post:
summary: Validate Directive
description: 'Free dry-run — no payment dependency at all. Still goes through
require_auth (identity/replay protection is not a billing concern), but
never touches payments.py.
Unlike every paid route (which now lets an anonymous request through
to see the 402 challenge, for x402 discovery — see payment_required()''s
docstring), this route has no such path: it validates against a
SPECIFIC user''s ledger history, so there''s no meaningful way to
"validate anonymously." An anonymous request here gets a real 401,
explicitly, rather than silently proceeding with no identity to
validate against.
Consumes the nonce immediately, explicitly, rather than deferring —
unlike paid routes, this endpoint has no 402-then-retry concept at
all, so there''s no reason to delay (see auth.consume_nonce()''s
docstring for why paid routes defer this and why this one doesn''t
need to).'
operationId: validate_directive_journal_directives_validate_post
parameters:
- name: X-Public-Key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Public-Key
- name: X-Nonce
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Nonce
- name: X-Timestamp
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Timestamp
- name: X-Signature
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Signature
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/DirectiveValidateRequest'
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/DirectiveWriteResponse'
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Journal
/journal/directives/batch:
post:
summary: Submit Batch
operationId: submit_batch_journal_directives_batch_post
parameters:
- name: X-Public-Key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Public-Key
- name: X-Nonce
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Nonce
- name: X-Timestamp
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Timestamp
- name: X-Signature
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Signature
- name: X-PAYMENT
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Payment
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/DirectiveBatchRequest'
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/DirectiveBatchResponse'
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Journal
components:
schemas:
DirectiveListItem:
properties:
id:
type: integer
title: Id
date:
type: string
title: Date
text:
type: string
title: Text
type: object
required:
- id
- date
- text
title: DirectiveListItem
DirectiveListResponse:
properties:
directives:
items:
$ref: '#/components/schemas/DirectiveListItem'
type: array
title: Directives
free_directives_list_remaining:
anyOf:
- type: integer
- type: 'null'
title: Free Directives List Remaining
type: object
required:
- directives
title: DirectiveListResponse
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
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
DirectiveWriteResponse:
properties:
accepted:
type: boolean
title: Accepted
errors:
items:
type: string
type: array
title: Errors
directive_id:
anyOf:
- type: integer
- type: 'null'
title: Directive Id
date:
anyOf:
- type: string
- type: 'null'
title: Date
free_writes_remaining:
anyOf:
- type: integer
- type: 'null'
title: Free Writes Remaining
type: object
required:
- accepted
title: DirectiveWriteResponse
description: 'Mirrors ledger.SubmitResult field-for-field, plus one addition
below that ISN''T part of that mirror.'
DirectiveBatchResponse:
properties:
accepted:
type: boolean
title: Accepted
errors:
items:
type: string
type: array
title: Errors
directive_ids:
items:
type: integer
type: array
title: Directive Ids
type: object
required:
- accepted
title: DirectiveBatchResponse
description: Mirrors ledger.BatchResult field-for-field.
DirectiveSubmitRequest:
properties:
text:
type: string
maxLength: 10000
minLength: 1
title: Text
type: object
required:
- text
title: DirectiveSubmitRequest
description: 'POST /journal/directives body. Exactly one directive''s literal
Beancount text — multiplicity and syntax validity are load_string()''s
job (ledger.submit_directive), not this model''s.'
DirectiveValidateRequest:
properties:
text:
type: string
maxLength: 10000
minLength: 1
title: Text
type: object
required:
- text
title: DirectiveValidateRequest
description: 'POST /journal/directives/validate body — identical shape to a real
submission, since it''s the same check minus persistence and payment.'
DirectiveBatchRequest:
properties:
directives:
items:
type: string
type: array
maxItems: 1000
minItems: 1
title: Directives
type: object
required:
- directives
title: DirectiveBatchRequest
description: 'POST /journal/directives/batch body. Cap matches
ledger.MAX_BATCH_SIZE — enforced here too so an oversized batch is
rejected before payment is even attempted (ARCHITECTURE.md §7:
malformed requests never reach the payment step).'