Personal Library

Reference - IOM REST API - Transmissions 1.0

https://support.intershop.com/kb/294A28

Share this document

ReDoc View
Document View

Product Version	2.13
Product To Version	4.1
Status	New Labels

This API specification is available for download as an Open API 3.0 YAML file:

intershop-order-management-transmission-1.0.yaml

API Specification

Introduction

OpenAPI Version: 3.0.0

IOM TRANSMISSION REST API Version: 1.0

The transmission REST API supports tasks to view and manage transmissions of the IOM.

transmission API

Transmission related operations exposed by this service.

/transmissions

GET: Get transmissions by search criterias.

Description

Returns all transmissions for selected search criterias.

Request Body

Request Parameters

Location	Name	Format	Default	Example	Description
in query	creationDate[gte]	string `date-time`			Required \| The earliest creation date of a transmission.
in query	creationDate[lte]	string `date-time`			Required \| The latest creation date of a transmission.
in query	transmissionTypes	array
in query	transmissionSubtypes	array
in query	transmissionStatuses	array
in query	transmissionResponseStatuses	array
in query	receiverTypes	array
in query	shopIds	array		`1`
in query	supplierIds	array		`1`
in query	limit	integer	`1000`		The number of items to return. If not set the limit is 1000.
in query	offset	integer	`0`		The number of items to skip before starting to collect the result set.
in query	orderBy
in query	sortDirection

Response

200 - OK The response for a transmission collection request.

TransmissionCollectionContainer application/vnd.intershop.transmission.v1+json

400 - Bad Request - Generic or business logic validation error.

ErrorReport application/vnd.intershop.transmission.v1+json

401 - Unauthorized - Authentication information is missing or invalid.

Response Header	Description
`WWW-Authenticate`

403 - Forbidden - the user is not authorized to use this resource.

406 - Not Acceptable - A representation of the response in the media type that was requested in the ACCEPT header cannot be provided.

500 - Internal Server Error - An unexpected error occured.

Request and Response Object Schemata

ErrorReport application/vnd.intershop.transmission.v1+json

{

"status":
integer
The HTTP status code. | Format: int32 | Example: 400
"errors":
array
An array of Error objects.
[
Error
{
- "code":
  string
  Required | Exception / Error code | Example: VALIDATION_EXCEPTION
- "message":
  string
  Required | Exception / Error message | Example: Attribute XYZ is mandatory
- "value":
  object
  Value which caused the exception / error.
}
]

}

TransmissionCollectionContainer application/vnd.intershop.transmission.v1+json

{

"meta":
object
A CollectionMetaData object. The meta data of collection.
{
- "totalCount":
  integer
  The total number of objects in the collection (without offset and limit). | Format: int64 | Example: 10000
}
"data":
array
An array of Transmission objects. The core data of the transmission collection.
[
Transmission
{
- "id":
  string
  The transmission identifier. | Example: ORDERTRANSMISSION-10000
- "transmissionType":
  string
  The type of the transmission.
  
  ORDERTRANSMISSION - Transmissions that are used for order processing messages, e.g. to announce an order entry. Subtypes of this type start with ORDER_.
  DISPATCHTRANSMISSION - Transmissions that are used for dispatch messages, e.g. a delivery that was made. Subtypes of this type start with DISPATCH_.
  RETURNTRANSMISSION - Transmissions that are used for return messages, e.g. a received return. Subtypes of this type start with RETURN_.
  PAYMENTTRANSMISSION - Transmissions that are used for payment notification messages, e.g. a received payment. Subtypes of this type start with PAYMENT_.
  MAILTRANSMISSION - Transmissions that are used for emails, e.g. to send a delivery email to the customer. Subtypes of this type start with MAIL_.
  RESPONSETRANSMISSION - Transmissions that are used for response messages, e.g. to respond to a delivery request. Subtypes of this type start with RESPONSE_.
  INVOICETRANSMISSION - Transmissions that are used for invoice processing messages. Subtypes of this type start with INVOICE_.
  DOCUMENTTRANSMISSION - Transmissions that are used for document processing messages. Subtypes of this type start with DOCUMENT_.
  RETURNANNOUNCEMENTTRANSMISSION - Transmissions that are used for return announcements messages. Subtypes of this type start with RETURNANNOUNCEMENT_.
  
  For any type use OTHERS for subtypes that are not listed, e.g. custom ones.
  | Example: ORDERTRANSMISSION | Possible Values: ORDERTRANSMISSIONDISPATCHTRANSMISSIONRETURNTRANSMISSIONPAYMENTTRANSMISSIONMAILTRANSMISSIONRESPONSETRANSMISSIONINVOICETRANSMISSIONDOCUMENTTRANSMISSIONRETURNANNOUNCEMENTTRANSMISSION
- "transmissionSubtype":
  string
  The subtype of the transmission.
  Please note the string representation to support subtypes from schema TransmissionType and unknown subtypes, e.g. custom ones. | Example: MAIL_ORDER
- "status":
  string
  The processing status of the transmission.
  
  INITIAL - Transmission is initially stored.
  DO_PULL - Transmission will be pulled.
  PULLED - Transmission was received (pulled) from the sender.
  DO_PUSH - Transmission can be sent (pushed) to the receiver.
  PUSHED - Transmission was sent (pushed) to the receiver.
  DO_MANUAL_CHECK - The processing of transmission was canceled because of errors. The transmission has to be checked manually.
  CHECKED - The transmission was checked manually and is ready to process.
  DO_CANCEL - The transmission will be canceled.
  CANCELED - Transmission can be canceled because processing is not required any longer.
  TRANSMISSIONED - Transmission was submitted.
  CONFIRMED - Transmission was confirmed from the receiver. | Example: CONFIRMED | Possible Values: INITIALDO_PULLPULLEDDO_PUSHPUSHEDDO_MANUAL_CHECKCHECKEDDO_CANCELCANCELEDTRANSMISSIONEDCONFIRMED
- "responseStatus":
  string
  The status of the response of the transmission.
  
  OK - The transmission was successfully received.
  INVALID - An error occurred during validation check at the receiver.
  REJECTED - The operation was rejected by the receiver.
  EXTERNAL_ERROR - An unexpected error occurred at the receiver.
  INTERNAL_ERROR - Internal unexpected error has occurred.
  NOT_AVAILABLE - The response status is not set. | Example: REJECTED | Possible Values: OKINVALIDREJECTEDEXTERNAL_ERRORINTERNAL_ERRORNOT_AVAILABLE
- "creationDate":
  string
  The date when the transmission was created. | Format: date-time
- "modificationDate":
  string
  The date when the transmission was modified. | Format: date-time
- "orderId":
  integer
  The id of the order. | Format: int64 | Example: 10026
- "shopOrderNumber":
  string
  The order number as used by the shop. | Example: 20180303123
- "shopId":
  integer
  The id of the shop. | Format: int64 | Example: 1000
- "shopName":
  string
  The name of the shop. | Example: Test Shop US DE
- "supplierId":
  integer
  The id of the supplier. | Format: int64 | Example: 1000
- "supplierName":
  string
  The name of the supplier. | Example: Test Supplier US DE
- "receiverType":
  string
  The type of the receiver of a transmission.
  
  OMS - The OMS-application itself.
  SHOP - The shop is the receiver of the transmission.
  SUPPLIER - The supplier is the receiver of the transmission, e.g. of a delivery request.
  CUSTOMER - The customer is the receiver of the transmission, e.g. an email to confirm an order.
  PAYMENTPROVIDER - A payment provider is the receiver of the transmission, e.g. to note a received payment to.
  FINANCECONTROLLER - A finance contoller is the receiver of the transmission, e.g. a debitor management system that receives open amounts. | Example: SHOP | Possible Values: OMSSHOPSUPPLIERCUSTOMERPAYMENTPROVIDERFINANCECONTROLLER
- "retryCount":
  integer
  Number of sending attempts. | Example: 2
- "retryDate":
  string
  The date of the last attempt to send the transmission. | Format: date-time
- "nextRetryDate":
  string
  The next date to send the transmission. | Format: date-time
- "errorText":
  string
  The error text, if the transmission failed. | Example: This was no error, because the status was set OK.
}
]

}

Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.