Skip to main content
PUT
Update transaction

Authorizations

Authorization
string
header
required

First-party access token for your own signed-in session, obtained from the /api/enterprise-auth/login endpoint. The REST API returns your own account data to you — it is a first-party consumer surface, not a third-party integration channel. Data from connected bank feeds (open-banking / CDR data) is your own data, returned only to you in your own authenticated session.

Headers

Idempotency-Key
string

Optional. Any string of at most 256 characters (a UUID is a good choice). The first response to a POST, PUT or PATCH carrying this key is stored for 24 hours, scoped to your account; repeating the request with the same key and the same body returns that stored response (with Idempotency-Replay: true) instead of running the request again. The same key with a different body returns 409. A key longer than 256 characters returns 400. Whatever the first response was, including an error, is what is replayed. The store is held in memory on the server instance that answered, so it does not survive a restart and is not shared between instances: treat it as protection against quick retries, not as a durable guarantee.

Maximum string length: 256

Path Parameters

id
string
required

Body

application/json
description
string
required
amount
number
required

With primaryType expense the amount is stored negative, with income positive.

date
string<date-time>
required
primaryType
enum<string>
Available options:
income,
expense,
transfer
type
enum<string>

Derived from primaryType and amount when omitted.

Available options:
debit,
credit
categoryId
string
merchant
string
reference
string
isTaxDeductible
boolean
businessUsePercentage
number
Required range: 0 <= x <= 100
notes
string
gstIncluded
boolean
gstAmount
number
clientRequestId
string

Optional durable de-duplication key for this create. Sending the same value again returns the transaction already saved with replayed: true instead of creating a second one. Unlike Idempotency-Key it is stored with the transaction itself.

Pattern: ^[A-Za-z0-9-]{8,64}$

Response

Transaction updated successfully