---
title: "Send an outbound Swift message"
method: POST
path: "/webapi/outbound-messages"
tags: ["Outbound Messages"]
---

# Send an outbound Swift message

`POST /webapi/outbound-messages`

## Request

- Base URL: `https://your-environment.appiancloud.com/suite`
- URL: `https://your-environment.appiancloud.com/suite/webapi/outbound-messages`
- Auth: API key in header `appian-api-key`
- TypeScript: <https://skmtc.dev/appian/apis/appian-adapter-for-swift-api/docs/webapi/outbound-messages/post.ts> (a function with typed inputs; its response is checked against the schema)

Receives a structured Appian data object, converts it to a valid Swift MT or MX
message, validates the message, and sends it to the configured upstream channel.
The `content` field contains the message-type-specific payload structured as JSON.

## Request body

- OutboundMessageRequest
  - `content` object, required: The structured message payload. Contains the message type identifier and the message-type-specific content as a nested JSON object.
    - `messageType` string, required: The Swift message type identifier. For MX messages, use the ISO 20022 message identifier (e.g., `pacs.008.001.08`, `camt.057.001.06`). For MT messages, use the MT type number (e.g., `MT103`, `MT202`).
    - `content` object, required: The message-type-specific content. The structure of this object varies by message type. See the companion file `message-type-schemas.yaml` for the full field definitions of each supported message type.
  - `swiftVersion` '2025' | '2026': The Swift standards version to use for message generation and validation. Determines which Prowide library version is applied.
  - `source` string, required: Identifier of the system sending the outbound request.
  - `destination` string: The target system or channel for the outbound message. This is a free-form string; any value can be passed through this field.
  - `destinationFields` object[]: Additional metadata key-value pairs for the destination.
  - `ignoreValidation` boolean: If `true`, skips Swift message validation before sending. Use with caution — invalid messages may be rejected by the Swift network.
  - `validateBic` boolean: Whether to validate BIC codes in the outbound message against the BIC reference database.

## Response `200`

Message created, validated, and sent successfully.

- OutboundMessageResponse: Response returned when an outbound message is processed.
  - `messageId` string, uuid: The unique identifier assigned to the outbound message.
  - `status` 'RCVD' | 'ERR-001' | 'ERR-002': The processing status of the outbound message.
  - `error` string, nullable: Error message, or null on success.
  - `content` object, nullable: Additional content returned by the service, or null.

## Other responses

- `400`: Bad request. Validation failed or payload is malformed.
- `401`: Unauthorized. Invalid or missing API key.
- `500`: Internal server error.

---

[API](https://skmtc.dev/appian/apis/appian-adapter-for-swift-api.md) - [All operations](https://skmtc.dev/appian/apis/appian-adapter-for-swift-api/llms.txt) - [OpenAPI document](https://skmtc.dev/appian/apis/appian-adapter-for-swift-api/revisions/e569d9171a33?raw)