Browse the docs

Reference · Payees

Create a payee

POSThttps://api.paygoro.com/v1/payees

Saves a beneficiary. The IBAN is checksum-validated and normalized; one payee per IBAN per company.

Authorization

Requires a bearer API key with payees:write. See Authentication.

Request body

application/json

FieldTypeDescription
companyIdstringRequired when the workspace has more than one legal entity.
namerequiredstringmax 70 chars
ibanrequiredstringAny formatting; validated and normalized server-side.max 42 chars
defaultReferencestringDefault SEPA remittance reference (1–35 characters from the SEPA character set).

Response

201 · application/json

FieldTypeDescription
idstringOpaque resource id.
companyIdstringOpaque resource id.
namestringmax 70 chars
ibanstringNormalized IBAN (uppercase, no spaces).
defaultReferencestring | null
lastUsedAtstring (date-time) | nullWhen a transfer to this payee was last initiated.
createdAtstring (date-time)Timestamp in RFC 3339 format (UTC).
updatedAtstring (date-time)Timestamp in RFC 3339 format (UTC).

Errors

400BAD_REQUESTThe request was malformed or failed validation.
401UNAUTHORIZEDMissing, malformed, expired or revoked API key.
403FORBIDDENThe API key does not have the scope this operation requires.
404NOT_FOUNDNo resource with this id exists in your workspace, or a `companyId` filter does not match one of your companies.
409CONFLICTA payee with this IBAN already exists for the company.
429TOO_MANY_REQUESTSRate limit exceeded. Retry after the `Retry-After` header.

All errors share one envelope — see Errors.