openapi: 3.0.4
info:
title: Mews Booking Engine API (Distributor) Account notes Commands API
version: v1
description: The Mews Booking Engine API (historically the Distributor API, served from /api/distributor/v1) lets developers build guest-facing booking engines that create reservations directly in Mews. It exposes enterprise configuration, availability, pricing, products, vouchers, payment cards, and reservation group creation for front-end client consumption.
x-generated-from: documentation
x-source-url: https://api.mews.com/Swagger/distributor/swagger.json
x-last-validated: '2026-06-02'
servers:
- url: https://api.mews.com
description: Production
- url: https://api.mews-demo.com
description: Demo / sandbox
security:
- MewsClientToken: []
MewsAccessToken: []
tags:
- name: Commands
paths:
/api/connector/v1/commands/getAllByIds:
post:
tags:
- Commands
summary: Mews Get All Commands by Ids
description: Returns all commands by their identifiers.
operationId: commands_getAllByIds
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/DeviceCommandFilterParameters'
example:
ClientToken: E0D439EE522F44368DC78E1BFB03710C-D24FB11DBE31D4621C4817E028D9E1D
AccessToken: C66EF7B239D24632943D115EDE9CB810-EA00F8FD8294692C940F6B5A8F9453D
Client: Sample Client 1.0.0
CommandIds:
- aa20961f-6d9e-4b35-ad25-071213530aec
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/DeviceCommandResult'
example:
Commands:
- Id: aa20961f-6d9e-4b35-ad25-071213530aec
State: Pending
CreatedUtc: '2015-09-02T19:25:44Z'
Creator:
FirstName: Sample
LastName: User
ImageUrl: '...'
Device:
Id: 63efb573-fc58-4065-b687-9bdd51568529
Name: Test Printer
Type: Printer
Data:
CopyCount: 1
FileType: application/pdf
FileData: '...'
PrinterName: Printer
PrinterDriverName: ''
PrinterPortName: ''
'400':
description: Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllByIds400Example:
summary: Default commands_getAllByIds 400 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'401':
description: Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllByIds401Example:
summary: Default commands_getAllByIds 401 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'403':
description: Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllByIds403Example:
summary: Default commands_getAllByIds 403 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'408':
description: Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see [Request timeouts](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts)
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllByIds408Example:
summary: Default commands_getAllByIds 408 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'204':
description: Server has successfully fulfilled the request and there is no additional information to send back.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllByIds204Example:
summary: Default commands_getAllByIds 204 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'429':
description: Error caused by too many requests sent in a given amount of time. Response contains `Retry-After` header indicating how long the user agent should wait before making a follow-up request. For more information, see [Request limits](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-limits).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllByIds429Example:
summary: Default commands_getAllByIds 429 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'500':
description: Unexpected error on the Mews side. This may be due to a software fault. If such a situation occurs, the error will be logged and the development team notified, however you can raise an issue through GitHub on our [documentation repository](https://github.com/MewsSystems/gitbook-connector-api).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllByIds500Example:
summary: Default commands_getAllByIds 500 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
/api/connector/v1/commands/getAllActive:
post:
tags:
- Commands
summary: Mews Get All Commands
description: Returns all commands the are still active from the client application point of view. That means commands that are in either `Pending` or `Received` state.
operationId: commands_getAllActive
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/GetAllActiveCommandsParameters'
example:
ClientToken: E0D439EE522F44368DC78E1BFB03710C-D24FB11DBE31D4621C4817E028D9E1D
AccessToken: C66EF7B239D24632943D115EDE9CB810-EA00F8FD8294692C940F6B5A8F9453D
Client: Sample Client 1.0.0
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/DeviceCommandResult'
example:
Commands:
- Id: aa20961f-6d9e-4b35-ad25-071213530aec
State: Pending
CreatedUtc: '2015-09-02T19:25:44Z'
Creator:
FirstName: Sample
LastName: User
ImageUrl: '...'
Device:
Id: 63efb573-fc58-4065-b687-9bdd51568529
Name: Test Printer
Type: Printer
Data:
CopyCount: 1
FileType: application/pdf
FileData: '...'
PrinterName: Printer
PrinterDriverName: ''
PrinterPortName: ''
'400':
description: Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllActive400Example:
summary: Default commands_getAllActive 400 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'401':
description: Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllActive401Example:
summary: Default commands_getAllActive 401 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'403':
description: Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllActive403Example:
summary: Default commands_getAllActive 403 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'408':
description: Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see [Request timeouts](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts)
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllActive408Example:
summary: Default commands_getAllActive 408 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'204':
description: Server has successfully fulfilled the request and there is no additional information to send back.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllActive204Example:
summary: Default commands_getAllActive 204 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'429':
description: Error caused by too many requests sent in a given amount of time. Response contains `Retry-After` header indicating how long the user agent should wait before making a follow-up request. For more information, see [Request limits](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-limits).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllActive429Example:
summary: Default commands_getAllActive 429 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'500':
description: Unexpected error on the Mews side. This may be due to a software fault. If such a situation occurs, the error will be logged and the development team notified, however you can raise an issue through GitHub on our [documentation repository](https://github.com/MewsSystems/gitbook-connector-api).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsGetAllActive500Example:
summary: Default commands_getAllActive 500 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
/api/connector/v1/commands/addPrinter:
post:
tags:
- Commands
summary: Mews Add Printer Command
description: Adds a new printer command representing printing of the specified document on a printer. Note this operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
operationId: commands_addPrinter
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/PrinterCommandParameters'
example:
ClientToken: E0D439EE522F44368DC78E1BFB03710C-D24FB11DBE31D4621C4817E028D9E1D
AccessToken: C66EF7B239D24632943D115EDE9CB810-EA00F8FD8294692C940F6B5A8F9453D
Client: Sample Client 1.0.0
PrinterId: d117866d-78de-4459-9077-42d7ea0120e3
EnterpriseId: 3fa85f64-5717-4562-b3fc-2c963f66afa6
CopyCount: 1
Data: JVBERi0xLjcKCjEgMCBvYmogICUgZW50cnkgcG9pbnQKPDwKICAvVHlwZSAvQ2F0YWxvZwogIC9QYWdlcyAyIDAgUgo+PgplbmRvYmoKCjIgMCBvYmoKPDwKICAvVHlwZSAvUGFnZXMKICAvTWVkaWFCb3ggWyAwIDAgMjAwIDIwMCBdCiAgL0NvdW50IDEKICAvS2lkcyBbIDMgMCBSIF0KPj4KZW5kb2JqCgozIDAgb2JqCjw8CiAgL1R5cGUgL1BhZ2UKICAvUGFyZW50IDIgMCBSCiAgL1Jlc291cmNlcyA8PAogICAgL0ZvbnQgPDwKICAgICAgL0YxIDQgMCBSIAogICAgPj4KICA+PgogIC9Db250ZW50cyA1IDAgUgo+PgplbmRvYmoKCjQgMCBvYmoKPDwKICAvVHlwZSAvRm9udAogIC9TdWJ0eXBlIC9UeXBlMQogIC9CYXNlRm9udCAvVGltZXMtUm9tYW4KPj4KZW5kb2JqCgo1IDAgb2JqICAlIHBhZ2UgY29udGVudAo8PAogIC9MZW5ndGggNDQKPj4Kc3RyZWFtCkJUCjcwIDUwIFRECi9GMSAxMiBUZgooSGVsbG8sIHdvcmxkISkgVGoKRVQKZW5kc3RyZWFtCmVuZG9iagoKeHJlZgowIDYKMDAwMDAwMDAwMCA2NTUzNSBmIAowMDAwMDAwMDEwIDAwMDAwIG4gCjAwMDAwMDAwNzkgMDAwMDAgbiAKMDAwMDAwMDE3MyAwMDAwMCBuIAowMDAwMDAwMzAxIDAwMDAwIG4gCjAwMDAwMDAzODAgMDAwMDAgbiAKdHJhaWxlcgo8PAogIC9TaXplIDYKICAvUm9vdCAxIDAgUgo+PgpzdGFydHhyZWYKNDkyCiUlRU9G
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/DeviceCommandAddResult'
example:
CommandId: 2391a3df-1c61-4131-b6f8-c85b4234adcb
'400':
description: Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPrinter400Example:
summary: Default commands_addPrinter 400 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'401':
description: Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPrinter401Example:
summary: Default commands_addPrinter 401 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'403':
description: Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPrinter403Example:
summary: Default commands_addPrinter 403 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'408':
description: Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see [Request timeouts](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts)
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPrinter408Example:
summary: Default commands_addPrinter 408 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'204':
description: Server has successfully fulfilled the request and there is no additional information to send back.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPrinter204Example:
summary: Default commands_addPrinter 204 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'429':
description: Error caused by too many requests sent in a given amount of time. Response contains `Retry-After` header indicating how long the user agent should wait before making a follow-up request. For more information, see [Request limits](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-limits).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPrinter429Example:
summary: Default commands_addPrinter 429 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'500':
description: Unexpected error on the Mews side. This may be due to a software fault. If such a situation occurs, the error will be logged and the development team notified, however you can raise an issue through GitHub on our [documentation repository](https://github.com/MewsSystems/gitbook-connector-api).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPrinter500Example:
summary: Default commands_addPrinter 500 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
/api/connector/v1/commands/addKeyCutter:
post:
tags:
- Commands
summary: Mews Add Key Cutter Command
description: Adds a new key cutter command representing cutting of a key for the specified reservation. Note this operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
operationId: commands_addKeyCutter
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/KeyCutterCommandParameters'
example:
ClientToken: E0D439EE522F44368DC78E1BFB03710C-D24FB11DBE31D4621C4817E028D9E1D
AccessToken: C66EF7B239D24632943D115EDE9CB810-EA00F8FD8294692C940F6B5A8F9453D
Client: Sample Client 1.0.0
EnterpriseId: 3fa85f64-5717-4562-b3fc-2c963f66afa6
KeyCutterId: 7dafffff-a727-4917-a203-bd53995f21bf
ReservationId: be35b39e-ad7e-460a-8de9-4c7581e016a2
KeyCount: 1
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/DeviceCommandAddResult'
example:
CommandId: 2391a3df-1c61-4131-b6f8-c85b4234adcb
'400':
description: Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddKeyCutter400Example:
summary: Default commands_addKeyCutter 400 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'401':
description: Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddKeyCutter401Example:
summary: Default commands_addKeyCutter 401 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'403':
description: Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddKeyCutter403Example:
summary: Default commands_addKeyCutter 403 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'408':
description: Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see [Request timeouts](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts)
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddKeyCutter408Example:
summary: Default commands_addKeyCutter 408 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'204':
description: Server has successfully fulfilled the request and there is no additional information to send back.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddKeyCutter204Example:
summary: Default commands_addKeyCutter 204 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'429':
description: Error caused by too many requests sent in a given amount of time. Response contains `Retry-After` header indicating how long the user agent should wait before making a follow-up request. For more information, see [Request limits](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-limits).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddKeyCutter429Example:
summary: Default commands_addKeyCutter 429 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'500':
description: Unexpected error on the Mews side. This may be due to a software fault. If such a situation occurs, the error will be logged and the development team notified, however you can raise an issue through GitHub on our [documentation repository](https://github.com/MewsSystems/gitbook-connector-api).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddKeyCutter500Example:
summary: Default commands_addKeyCutter 500 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
/api/connector/v1/commands/addPaymentTerminal:
post:
tags:
- Commands
summary: Mews Add Payment Command
description: "> ### Restricted!\r\n> This operation is part of a custom workflow for Mews partners such as POS systems to access Mews Payment Terminals.\r\n> See [Mews Payment Terminals](https://mews-systems.gitbook.io/connector-api/use-cases/mews-terminals).\r\n\r\nAdds a new Mews Payment Terminal command for taking a customer payment.\r\nThe operation instructs a specified terminal device to take a payment from a specified customer for a specified amount."
operationId: commands_addPaymentTerminal
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentTerminalCommandParameters'
example:
ClientToken: E0D439EE522F44368DC78E1BFB03710C-D24FB11DBE31D4621C4817E028D9E1D
AccessToken: 7059D2C25BF64EA681ACAB3A00B859CC-D91BFF2B1E3047A3E0DEC1D57BE1382
Client: MyPOS 1.0
Type: Payment
TerminalId: be35b39e-ad7e-460a-8de9-4c7581e016a2
CustomerId: 35d4b117-4e60-44a3-9580-c582117eff98
BillId: null
Amount:
Currency: EUR
Value: 230
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/DeviceCommandAddResult'
example:
CommandId: 2391a3df-1c61-4131-b6f8-c85b4234adcb
'400':
description: Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPaymentTerminal400Example:
summary: Default commands_addPaymentTerminal 400 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'401':
description: Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPaymentTerminal401Example:
summary: Default commands_addPaymentTerminal 401 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'403':
description: Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectorApiExceptionResult'
examples:
CommandsAddPaymentTerminal403Example:
summary: Default commands_addPaymentTerminal 403 response
x-microcks-default: true
value:
Message: string
RequestId: 3edd5f9e-7e64-4f2a-9a0e-b3f200e6c111
Details: string
'408':
description: Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see [Request timeouts](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts)
content:
application/json:
schema:
$ref: '#/components/s
# --- truncated at 32 KB (149 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/mews-systems/refs/heads/main/openapi/mews-systems-commands-api-openapi.yml