PATCH endpoint for updating the processing status of outbound EDI Transactions. By default, the system assumes successful processing for an outbound message, unless autoMarkAsSuccess is passed into the GET endpoint. Call the PATCH endpoint to keep the transaction status up-to-date with actual processing status. If there is a failure in processing seen by the EDI Provider, the PATCH endpoint marks the EDI transaction with a required failure message.
OAuth 2.0 Client Credentials flow for server-to-server communication.
Valid authentication, valid patch requests, no errors
Patch operation payload does not pass validation
EDI Transaction ID is required
"Bad request: EDI Transaction is required"Status is not one of the available options we support
"Bad request: Status provided \"\" is not a supported EDI Transaction Status (Pending, Success, Failure)" Payload does not match expected request model
"Bad request: Could not deserialize request"Unauthorized credentials. Provided by Salesforce.
Description of the error
Unique ID for the error
Forbidden User.
Description of the error
Unique ID for the error
The context user set up in the connected app doesn't match any of the edi provider context users in TMS Admin, check setup.
"Forbidden: Invalid EDI Context User"The edi transaction whose status is attempted to be patched is not for the provider identified in authentication
"Forbidden: EDI Transaction does not match provider" Catchall for any unexpected errors encountered when trying to queue edi events
EDI Rest API isn't enabled in TMS Admin