Current behaviour:

When a reservation is created through the Connector API (reservations/add), no Source is assigned. The reservation only carries Origin = "Mews Open API". The endpoint does not support a SourceId field, so there is no way to tag the reservation with the channel or source it actually came from.

By contrast, the Channel Manager API accepts a sources array in the reservation payload, and Mews assigns the source automatically. That capability simply doesn't exist on the Connector API side.

Why this is a problem:

We run our own booking engine built on the Connector API. Source codes are how we understand our business mix when pulling reservation data via the API, and right now those reservations are indistinguishable from any other Connector API traffic.

Our current workaround is to infer booking engine reservations from the Origin field. This does not scale: as soon as we add a second integration through the Connector API (additional channels, partner systems, corporate booking tools), every one of them reports the same Origin = "Mews Open API" and we lose the ability to tell them apart entirely. There is no fallback, because sourceAssignments in the Connector API is read-only.

The practical consequence is that direct and API-driven business cannot be segmented or reported on accurately, which undermines revenue analysis, channel cost comparisons, and any decision that depends on knowing where bookings originate.

Requested change:

Allow a source to be assigned to reservations created via the Connector API, ideally by supporting a SourceId (or a sources array, matching the Channel Manager API pattern) on reservations/add.

As an alternative or complement, a writable sourceAssignments/add operation would also solve it, letting us assign the source in a second call after reservation creation.

Business impact:

Any Mews customer running a custom booking engine or multiple Connector API integrations has the same blind spot. For us it currently blocks accurate business mix reporting across the chain, and it becomes a hard blocker as we onboard further channels through the Connector API.