Overview
DELMIA Apriso is Dassault Systemes’ manufacturing operations platform (MES, quality, warehouse, maintenance). Its Web API lets an external system call the Standard Operations you publish as REST web services, and its Business Integrator accepts inbound XML messages. This connector lets plant logic on MQTT declare production, push machine status, record quality results and read orders in Apriso without custom code.- DelmiaAprisoApi (
DelmiaAprisoRestApi.lot) is a client connector onhttps://YOUR_APRISO_SERVERwith 16 events. - DelmiaAprisoWebhookReceiver (
mes_delmia-apriso_webhook.lot, optional) is a server connector on port9008that receives calls from Apriso.
Server host
Apriso is installed per customer on IIS. ReplaceYOUR_APRISO_SERVER in BASE_ADDRESS with your Apriso web server, with no trailing slash. The endpoints already include the /Apriso application path: the Web API lives under /Apriso/HttpServices and the Secure Token Service (STS) at /Apriso/Portal/sts/2.0/token. On a lab server without TLS, use http:// and set USE_SSL to "false".
Authentication
- Register Coreflux as a client application in
ClientApplications.xml(in the server’sCentralConfigurationfolder) with aClientId, and anApiKeyand/or aClientSecret, theScopesit may request (standard_operations,message_processing, …) and theClientCredentialsgrant. Restart the Apriso services. - Pick a flow. Every Web API event takes
"authorization"and"client_id"in its MQTT payload and sends them asAuthorizationandX-Client-Application.- API key:
"authorization": "ApiKey <ApiKey>","client_id": "<ClientId>". Check it withHelloApiKey. - Access token: publish
GetToken(client credentials) withclient_id,client_secretandscope, then send"authorization": "Bearer <access_token>". Check it withHelloToken.GetUserToken(password grant,login_typestandardorldap) andRefreshTokenare there too.
- API key:
- Publish the Standard Operations you want to call in Process Builder > Web Services Manager, with security level API Key or Access Token.
APRISO_CLIENT_ID, APRISO_API_KEY and APRISO_CLIENT_SECRET. Wrong or missing credentials return 401 Unauthorized. A token only reaches the endpoints of the scopes it was issued for.
Payload conventions
- Standard Operations.
DescribeOperationreturns the operation’sInputs,Outputsand a sampleExecutionParametersbody. The run events send"body"unchanged:{"Inputs": {...}, "ExecutionMode": 1, "JobPool": "", "Retries": 1, "SleepTime": 1000, "SynchronuousQueue": "", "Timeout": 5000}. OnlyInputsis required.ExecutionModeis0(in the IIS process),1(synchronous through Job Executor, the default) or2(queued asynchronously). The response carriesOutputs. - Revisions. Calls use the operation’s default revision. The
...Revisionevents take arevisionsuch asREV.001.001. - Presets.
DeclareProduction,ReportMachineStatus,PostQualityInspectionResultandGetOrderuse the same contract on their own topics, so each plant use case gets a clean topic. Their operation codes and Inputs are examples: send the codes and Inputs of the operations you published. - Business Integrator.
ProcessMessageAsyncsends"body"as an XML string withContent-Type: application/xmlfor themessage_nameof your external system, and needs a token with themessage_processingscope. - Formats. Apriso answers JSON by default. Token requests are form-encoded, so keep the values in
client_secret,passwordandscopefree of&and=.
Tokens and auth checks
Standard Operations
Plant presets
Business Integrator and discovery
Receiving calls from Apriso (optional)
Deploymes_delmia-apriso_webhook.lot to let Apriso call the broker. It runs in server mode on port 9008 and republishes each request body unchanged.
For the Business Integrator REST Adapter, set the REST Client URL to
http(s)://<broker>:9008 and RELATIVEURI to /delmia-apriso/outbound/message. The connector has no authentication, so keep the port on the plant network or behind a reverse proxy with TLS.
Examples
Get a token (client credentials):docs-helper-actions.lot):
Writes
Write events: RunOperation, RunOperationRevision, DeclareProduction, ReportMachineStatus, PostQualityInspectionResult, ProcessMessageAsync. They change data in Apriso through the operations you published or through Business Integrator.GetOrder posts too, but only runs the read-only operation you point it at. No event deletes anything.
Not packaged
The SOAP web services (IFlexNetMessageProcessor), the Implicit and Authorization Code browser flows (they need a user in the Apriso Portal), the cache, personalization and data paging controllers (their endpoints are only in each server’s Web API Reference), 3DPassport authentication, and any DELETE.

