Deploy EDI rule file

Deploys the provided EDI rule file into corresponding INUBIT repository path.

Request

URL: /edirules

Method: PUT or POST

Authorization: required (user with role System Administrator)

PUT /ibis/rest/edirules HTTP/1.1
Accept: application/json
Content-Type: multipart/form-data
Host: localhost:8080

Name Description Required Allowed values

Name	Description	Required	Allowed values
`ruleFile`	EDI rule file	yes	Any attachment
`ruleFileName`	EDI Rule File Name i.e. EDIGAS-TSIMSG-5.9.xml	yes	Any string

ruleFile

EDI rule file

yes

Any attachment

ruleFileName

EDI Rule File Name i.e. EDIGAS-TSIMSG-5.9.xml

yes

Any string

HTTP/1.1 200 OK
Content-Tye: application/json

{
  "responsedata": "Created/updated successfully."
}

Authorization Failed (401): Authorization with the given username and password failed. Please revisit both values and provide valid credentials.

{
    "statusCode": 401,
    "message": "Unauthorized access",
    "path": "/rest/<endpoint>",
    "timestamp": "2025-06-07T14:21:11.781"
}

Resource Not Found (404): The 404 (Not Found) status code indicates that the requested endpoint or resource is unavailable or does not exist on the server.
Server Error (500): Execution on the INUBIT server failed. Have a look into the response message, otherwise access to the INUBIT log is required to retrieve further information.

{
  "statusCode": 500,
  "message": "Internal Server Error",
  "path": "/rest/<endpoint>",
  "timestamp": "2025-08-06T12:55:31.862"
}

Service Unavailable (503): In maintenance mode the INUBIT server endpoint will not respond to incoming requests but return this error response. Once the maintenance mode is switched off the endpoint will respond normally.

{
  "statusCode": 503,
  "message": "Service Unavailable",
  "path": "/rest/<endpoint>",
  "timestamp": "2025-08-06T12:58:06.688"
}