Categorization

Categorize transactions

Categorize transactions on the fly. The transaction data is provided in the request rather than fetched from the bank. Note: Currently the number of transactions that can be sent in one request is limited to 2000.

post/rpc/categorize

Request

Parameters

#/paths/~1auth~1user/post/parameters/0 (unresolved $ref)
#/paths/~1catalog/get/parameters/0 (unresolved $ref)

Request body

idstring required

An identifier that should be used for mapping this transaction to the categorization result. It is highly recommended to make this ID unique for the scope of the request.

amountBalance required(unresolved $ref)
currencystring ISO 4217:2015 required

Three-letter currency code.

ibanIban (unresolved $ref)
namestring

Name of counterparty.

purposestring

Purpose of the transaction potentially including other structured SEPA information (e.g. EREF+, MREF+).

sepa_purpose_codestring ISO 20022

SEPA category purpose code classifying the transfer as defined in ISO 20022 (e.g. SALA for salary payment or GDDS for purchase/sale of goods).

creditor_idstring

SEPA creditor identifier (for SEPA direct debits). Must be unique in combination with mandate_reference.

mandate_referencestring

SEPA mandate reference (for SEPA direct debits). Must be unique in combination with creditor_id.

end_to_end_referencestring

A reference code that can be used by the creditor for further identification of the transaction (e.g. a customer number or invoice number).

booked_atEndedAt (unresolved $ref)
user_idstring

A free-form identifier of the user to which the transaction belongs to.

Changes

No recorded changes to this operation across all 2 revisions of this API.