infor

Access to Mongoose through a RESTful service interface.

Mongoose REST Service

This method returns the list of supported versions of the IMS.

VERSIONS :: Gets IMS services supported versions

This method returns the server availability status.

PING :: Ping Service interface, checks whether the server is available or not.

This method is used to retrieve the expected IMS API version and protocol parameters of the client application.

PROTOCOL :: Gets IMS API supported version and protocol parameters

This method will be validating message request as per API specification and publish the message and returns whether the message is successfully published or not.

MULTIPARTMESSAGE :: Publish message via IMS

MESSAGE_V2 :: Publish message via IMS

This method returns the full list of documents supported by the application. It also indicates which documents are published and which ones are subscribed.

DISCOVERY :: Return the full list of documents supported by the application.

This method will be validating message request as per API specification and publish the message and returns whether the message is successfully published or not. The IMS via ION API Connector verifies if the calling request is done with the defined ION API Client Id. ION API swagger uses a different Client ID, so the test for this method will fail for this method.

MULTIPARTMESSAGE_V3 :: Publish message to ION via IMS

 For the given logicalid and tenant, this service request will return the list of documents the service (application) can exchange including the direction of exchange.
&lt;i&gt;Note: Implementation is only needed if in the protocol method hasDiscovery is set to true.

DISCOVERY_BY_LOGICALID_V3 :: Document discovery service by tenantId and logicalId.

GetConfigurations

SecurityToken

InvokeMethod

IDOPropInfo

A basic Load Collection with a record cap of 200

LoadCollection

A Load Collection with all potential parameters available

LoadCollectionAdvanced

A Load Collection with all parameters and a full inline XSD schema

LoadCollectionWithSchema

InsertItem

InsertItemRefresh

InsertItems

InsertItemsRefresh

UpdateItem

UpdateItemRefresh

UpdateItems

UpdateItemsRefresh

DeleteItem

DeleteItems

Execute an update based on a complete UpdateCollectionRequest

ExecuteUpdateRequest

FireAESEvent

FireAESEventAdvanced

UploadFileStream

UploadDocumentObject

json

A Load Collection returning a list of values for one property

LoadPropertyValues

DownloadFileStream

DownloadDocumentObject

Default

IDORequestService MGRestService.svc

Infor API | IDORequestService MGRestService.svc

Unauthorized

Not Found

Method Not Allowed

Not Acceptable Response

Internal Server Error 

Precondition Failed

Internal Server Error

Parameter Request File. The content type must be set to application/json.
 Example: 
{
  "documentName" : "Sync.SalesOrder",
  "messageId" : "message1",
  "fromLogicalId" : "lid://infor.ims.imsap",
  "toLogicalId" : "lid://default",
  "encoding" : "NONE",
  "characterSet" : "UTF-8",
  "accountingEntity" : "ae1",
  "location" : "loc123",
  "documentId" : "sdafas",
  "variationId" : 1,
  "revisionId" : "123",
  "batchId" : "infor.SSJE:1",
  "batchSequence" : 2,
  "batchSize" : 1,
  "batchRevision" : 1,
  "batchAbortIndicator" : true,
  "instances" : "1",
  "source" : "DB Connector",
  "custom_property1" : "value1",
  "custom_property2" : "value2"
}

ParameterRequest

Message Payload File. The content type must be set to application/octet-stream.

MessagePayload

Unsupported Media Type

documentName

messageId

fromLogicalId

toLogicalId

document

additionalProperties

logicalId

The tenantId as header parameter. Resource will be located based on tenantId.The TenantId is not required if IMS via ION API is used.

X-TenantId

Parameter Request File. The content type must be set to application/json. When selecting a file in this swagger, make sure that file has a '.json' extension
 Example: 
{
  "documentName" : "Sync.SalesOrder",
  "messageId" : "message1",
  "fromLogicalId" : "lid://infor.ims.imsap",
  "toLogicalId" : "lid://default",
  "encoding" : "NONE",
  "characterSet" : "UTF-8",
  "accountingEntity" : "ae1",
  "location" : "loc123",
  "documentId" : "sdafas",
  "variationId" : 1,
  "revisionId" : "123",
  "batchId" : "infor.SSJE:1",
  "batchSequence" : 2,
  "batchSize" : 1,
  "batchRevision" : 1,
  "batchAbortIndicator" : true,
  "instances" : "1",
  "source" : "DB Connector",
  "custom_property1" : "value1",
  "custom_property2" : "value2"
}

Message Payload File. The content type must be set to application/octet-stream. When selecting a file in this swagger, make sure that file has no extension, a '.bin' extension or any other extension which resolves to this content type.

The From LogicalId as query parameter to specify from which application multipart message is being published

The document name as query parameter of multipart message that is being published

Sections