-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #200 from MewsSystems/unified-structure
Extensive refresh of site for standardized structure
- Loading branch information
Showing
22 changed files
with
297 additions
and
213 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| root: ./ | ||
|
|
||
| redirects: | ||
| mews-operations/operations: mews-operations/README.md | ||
| channel-manager-operations/operations: channel-manager-operations/README.md |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,19 +1,18 @@ | ||
| # Mews Channel Manager API | ||
|
|
||
| Welcome to the __Mews Channel Manager API__. This is the Mews API for distribution and sales channels, supporting two main use cases: distributing availability, rates and inventory data to sales channels; and accepting reservations from sales channels. Typically, the users of this API are Channel Managers, which act as hubs for managing the various sales channels that a property may be connected to. The API connects these Channel Managers with __Mews Operations__. | ||
| Welcome to the __Mews Channel Manager API__. This is the Mews API for distribution and sales channels, supporting two main use cases: distributing availability, rates and inventory data to sales channels, and accepting reservations from sales channels. | ||
| To fully implement the API, you need to both make requests to Mews and also create your own endpoints to accept data from Mews. | ||
|
|
||
| The integration functionality is two-way, so the API is implemented in two parts: | ||
| > ### Two-way functionality | ||
| > * The [Mews side](mews-operations/README.md) handles requests from Channel Managers, including new reservations. | ||
| > * The [Channel Manager side](channel-manager-operations/README.md) handles requests from Mews, including availability updates. | ||
| * The [Mews side](mews-operations/README.md) receives requests from external Channel Managers, including new reservations | ||
| * The [Channel Manager side](channel-manager-operations/README.md) receives requests from Mews, including availability updates | ||
| For detailed information on connecting, authentication tokens, error codes, and more, see our [Usage guidelines](guidelines/README.md). | ||
| To gain deeper insights into Mews concepts, see [Concepts](concepts/README.md). For specific scenarios, see [Use cases](use-cases/README.md). | ||
|
|
||
| To fully implement the functionality of the API, you will need to not only make requests to Mews through defined endpoints on the Mews side, but also create your own endpoints to accept data from Mews on the Channel Manager side. | ||
|
|
||
| For a full guide on how to connect, what authentication tokens you need, the meaning of error codes and much more, see our [Guidelines](guidelines/README.md). For a deeper understanding of **Mews** concepts, see [Concepts](concepts/README.md). | ||
|
|
||
| If you encounter any issues using the API, or you have any questions, please get in touch via [[email protected]](mailto:[email protected]). | ||
| If you have any questions or encounter issues, reach out to us at [[email protected]](mailto:[email protected]). | ||
|
|
||
| > ### Changes to this API | ||
| > * For the history of changes to the API, see the [Changelog](changelog/README.md) | ||
| > * For important information on deprecations, see [Deprecations](deprecations/README.md) | ||
| > * To track changes and updates, you can follow the [GitHub repository](https://github.com/MewsSystems/gitbook-channel-manager-api/tree/master) | ||
| > * For the history of changes, see the [Changelog](changelog/README.md). | ||
| > * For important information on deprecations, see [Deprecations](deprecations/README.md). | ||
| > * To track changes and updates, follow the [GitHub repository](https://github.com/MewsSystems/gitbook-channel-manager-api/tree/master). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,25 +1,29 @@ | ||
| # Channel Manager side | ||
| # API Operations (CHM) | ||
|
|
||
| This section describes the Channel Manager side of the Channel Manager API, i.e. API Operations hosted by the Channel Manager. | ||
| The Channel Manager side receives requests from Mews, including inventory updates \(prices, availability and restrictions\) and booking confirmations. | ||
| This section describes the Channel Manager side of the __Mews Channel Manager API__, i.e. API Operations hosted by the Channel Manager. The Channel Manager side receives requests from Mews, including inventory updates \(prices, availability and restrictions\) and booking confirmations. The list of supported operations is as follows, organised here by theme. | ||
|
|
||
| > ### Inventory update modes | ||
| > Mews pushes inventory to the Channel Manager side in one of two modes, both using the same API Operations, either **Full Inventory Update Mode** or **Delta Inventory Update Mode**. | ||
| > For more information, see [Use cases > Inventory updates](../use-cases/inventory-updates.md). | ||
| ## Environments | ||
| ## Inventory | ||
|
|
||
| Similarly to the Mews side, there should be two environments with different `clientTokens`. | ||
| The test/development environment will be used to verify the connection by Mews before connecting to the live/production environment. | ||
| | <div style="width:200px">Operation</div> | Description | | ||
| | :-- | :-- | | ||
| | [Update prices](inventory.md#update-prices) | This method is used when Mews updates prices of rate plans | | ||
| | [Update availability](inventory.md#update-availability) | This method is used when Mews updates availability of space types | | ||
| | [Update restrictions](inventory.md#update-restrictions) | This method is used when Mews updates restrictions | | ||
| | [Process availability block](availabilityBlock.md) | This method is used when Mews sends availability blocks | | ||
|
|
||
| ## Inventory Update Modes | ||
| ## Reservations | ||
|
|
||
| Mews sends Inventory in two modes, both modes use the same API messages. | ||
| | <div style="width:200px">Operation</div> | Description | | ||
| | :-- | :-- | | ||
| | [Process group](reservations.md#process-group) | \[`async`\] Process a group of reservations, which can be new bookings, modifications or cancellations. | | ||
| | [Confirm booking](reservations.md#confirm-booking) | This method is used when Mews confirms a booking sent via [Process group](../mews-operations/reservations.md#process-group) | | ||
|
|
||
| ### Full Inventory Update Mode | ||
| ## Notifications | ||
|
|
||
| You can request an Inventory update for some specified time period via API operation [Request ARI update](../mews-operations/inventory.md#request-ari-update). | ||
| Alternatively, a property employee can use this mode to push the latest data manually. | ||
| Data sent in this mode is always for **all** connected rate plans and space types combinations. | ||
|
|
||
| ### Delta Inventory Update Mode | ||
|
|
||
| Mews automatically sends changes in Inventory \(once connection is set up\). Data sent in this mode is just the changed data from the last update. | ||
| This is a completely automated process and there is no way to trigger just the delta update to be sent. | ||
| Delta inventory updates are sent repeatedly until they are successfully accepted by the channel manager. | ||
| | <div style="width:200px">Operation</div> | Description | | ||
| | :-- | :-- | | ||
| | [Change notification](notifications.md#change-notification) | This operation is used by Mews to notify the channel manager when there is a change in the connection configuration | |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.