Skip to main content
POST
Create bank transfer
See the overview page for required fields, lines, the exchange rate calculation and the customer movement override.

Error codes

Codes this endpoint can return. The general errors that apply to every endpoint (authentication, permissions, request headers, daily limit) are not repeated here.

Authorizations

Authorization
string
header
required

Access token obtained from the Noyax auth service with your API key.

Headers

X-UserID
integer<int32>
required

ID of the Noyax user the request is made on behalf of. Written to the audit fields of created, updated and deleted records.

Required range: x >= 1
X-CompanyID
integer<int32>
required

ID of the company. The user must be assigned to this company. All reads and writes are limited to this company.

Required range: x >= 1
X-PeriodID
integer<int32>

ID of the accounting period. Optional for customer endpoints; if sent, it is written to created records.

Required range: x >= 1

Body

TransferType
integer<int32>

Required. 1: Incoming transfer (Gelen EFT/Havale), 2: Outgoing transfer (Giden EFT/Havale). Cannot be changed after the voucher is created.

Example:

1

VoucherNumber
null | string

Required. Voucher number, unique within the company among all bank vouchers. Send "Next" on create to generate it from the company's bank voucher number series. At most 20 characters.

Example:

"Next"

Date
null | string<date-time>

Required. Voucher date. If a time is sent it is stored as the voucher time, otherwise the current time is used.

Example:

"2026-09-24T14:06:00"

BankAccountCode
null | string

Required. Bank account name (Name from GET /api/v1/finance/bank-accounts). All lines are recorded against this account.

Example:

"TEST POS"

Description
null | string

Description. At most 1000 characters.

SharingCode
null | string

Sharing code that limits who can see the voucher. Empty means visible to everyone; otherwise it must be one of the user's sharing codes.

Lines
object[]

Required, at least one line.

Response

Created

Success
boolean
required

Whether the operation succeeded.

Example:

true

ResultCode
string
required

"0000" on success. On failure, the code of the first error; all errors are listed in Errors.

Example:

"0000"

Data
object
required

Response data. Null when Success is false.

Message
null | string

Error message when Success is false. Messages of all errors are joined into a single text.