Recurring Integration REST APIs in d365 FO

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/recurring-integrations

Decision point	Recurring integrations API
Scheduling	Scheduling in finance and operations apps
Format	Files and data packages
Transformation	Support for Extensible Stylesheet Language Transformations (XSLT) if the data file is in XML format
Supported protocols	SOAP and REST
Service type	Custom service

API for import (enqueue):

Make an HTTP POST call against the following URL.

POST: https://<base URL>/api/connector/enqueue/activity ID?entity=entity name

Body ->Binary -> we have to attach file

Output: Message ID

API for getting message status:

Make an OData call against the following URL.

POST: https://<base URL>/data/DataManagementDefinitionGroups/Microsoft.Dynamics.DataEntities.GetMessageStatus

BODY

{

    "messageId":"<string>"

}

Getting execution id by message Id:

POST: https://<base URL>/data/DataManagementDefinitionGroups/Microsoft.Dynamics.DataEntities.GetExecutionIdByMessageId

BODY

{

    "messageId": "<string>"

}

 

API to get the list of execution errors:

POST : https://<base URL>/data/DataManagementDefinitionGroups/Microsoft.Dynamics.DataEntities.GetExecutionErrors

BODY

{

     "executionId":"<executionId>"

}

 

API for export (dequeue):

Make an HTTP Get call against the following URL.

GET: https://<base URL>/api/connector/dequeue/activity ID

This response body will be used ack action

Output: we will get the JSON message in that we will have DownloadLocation URL ->click on that it will open another tab execute --> it will give you downloadable message ->Save response to file as XXX.zip

 

API for acknowledgment:

Make an HTTP Post call against the following URL.

POST: https://<base URL>/api/connector/ack/activity ID

Note: The body of the response of /dequeue must be sent in the body of the /ack POST request.