Skip to main content
POST
Assign category to 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

transactionId
string
required

Body

application/json
categoryId
string
required
categorySetId
string
isPrimary
boolean
default:false
confidence
number
Required range: 0 <= x <= 1
assignedBy
enum<string>
Available options:
user,
ai,
import,
rule,
bulk
notes
string

Response

Category assigned

success
boolean
category
object

A category assignment for a transaction. Transactions can have multiple categories from different sets.