swift-outgoings

Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.

Response body, read from the service source

The route declares its response as IEnumerable<SwiftOutgoingDto>.

Field	Declared type	Nullable
Id	Guid	no
MTId	Guid	no
Reference	string	no
MessageType	string	no
MessageText	string	no
Status	string	no
TransactionDate	DateTime	no
ValueDate	DateTime?	yes
SendDate	DateTime?	yes
Response	string	no
UETR	string	no
MessageContentHtml	string	no
BusinessKey	string	no
ParentReference	string	no

Member names are the service's declaration names.

Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.

Response body, read from the service source

The route returns AuraCommandDto<Guid>, which is the response body itself and not a wrapper around one: the framework declares it as a class with a single property, Id, of type Guid. A caller gets a JSON OBJECT with one field, not a bare value. The field is id on the wire.

Field	Name on the wire	Declared type	Nullable
Id	id	Guid	no

Member names are the service's declaration names.

Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.

Response body, read from the service source

The route declares its response as SwiftOutgoingDto.

Field	Declared type	Nullable
Id	Guid	no
MTId	Guid	no
Reference	string	no
MessageType	string	no
MessageText	string	no
Status	string	no
TransactionDate	DateTime	no
ValueDate	DateTime?	yes
SendDate	DateTime?	yes
Response	string	no
UETR	string	no
MessageContentHtml	string	no
BusinessKey	string	no
ParentReference	string	no

Member names are the service's declaration names.

Error codes this operation is known to raise

Code	Status	Meaning
ERR_FRGN_TRD_11	400	SWIFT_OUTGOING_NOT_FOUND