Suggested bank transactions for this credit note
Bank transactions that most likely settled this credit note — the mirror of
listTransactionSuggestions,
same engine, record on the other side.
Read-only. To act on one, post it to
pair on the SUGGESTED TRANSACTION
(pairable.id here is the transaction), naming this credit note as the
pairable — pairing is always written from the transaction’s side.
A paid or overpaid credit note is not searched and returns an empty list. An overpayment is still recorded by pairing the transaction by hand.
Authentication
JWT issued via POST /api/v1/auth/sign_in. Used by mobile and SPA clients. Revoked tokens are rejected.
Lucanto API key. Two prefixes:
lct_pat_<random><checksum>— personal access token (owner: User)lct_live_<random><checksum>— workspace token, live data
Issue keys at /settings/api_keys (personal) or
/:workspace_id/settings/api_keys (workspace). Plaintext token is
shown once and never again.
Path parameters
CreditNote ID. Either the numeric id or the public_id (doc_…).
Query parameters
How many suggestions to return. Values above the maximum are clamped rather than rejected, and a non-positive value falls back to the default.