---
schema_version: "1"
id: 2c5343cbcf91620eefb97c97caf34e74769a8ae518da3ce4646560ada4af4f11
title: Outbound Message Routing
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/outbound-message-routing.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/outbound-message-routing
source_site: docs.mulesoft.com
content_type: documentation
content_hash: acab788b841a6bba9f8e9fd21b1160f03fb510724448c0e31862eb4ef84b635c
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: Partner Manager
version: 2.x
is-latest-version: true
---

# Outbound Message Routing

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The Anypoint Partner Manager outbound message routing framework enables you to implement receiving
endpoints in a variety of ways. You can:

- Use a single endpoint to receive different types of application messages, such as advance shipment
  notices and invoices, from your backend systems.

- Use dedicated endpoints for each message type from backend systems.

- Follow a balanced approach by implementing a mixed set of receive endpoints to receive application
  messages from backend systems.

When messages are received by the endpoint, Partner Manager routes the payload to the appropriate
message flow based on the message type, partner reference ID, and host reference ID configurations:

1.  Identifies the message type using the following criteria:

    - Relative path for HTTP or HTTPS endpoints

    - Filename for SFTP endpoints, which follow this convention:

      `<message-type>_<endpoint-information>.<file-type>`.

      For example, if your message type ID is ar-invoice, then the filename is
      `ar-invoice_20210217_1055_000.json`.

2.  Validates the payload against the schema supplied during the message type definition.

3.  Uses the supplied DataWeave map to obtain the partner reference ID, optional host reference IDs,
    and the business key.

    The partner reference ID and host reference ID specify the message flow through which the
    transaction is processed.

![A flowchart showing how outbound messages are routed](/mulesoft/current/en-us/partner-manager/latest/_images/pm-outbound-message-routing.png)

## See Also

- [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows)

- [Modifying Message Flow Settings](https://docs.mulesoft.com/partner-manager/latest/manage-message-flows)

- [Track Transmission Activity](https://docs.mulesoft.com/partner-manager/latest/activity-tracking)