iDempiere API Authentication

How to authenticate iDempiere API requests: one Bearer API key plus a connectionId. MindCloud handles iDempiere's custom auth scheme for you.

Every iDempiere API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your iDempiere account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

Create a MindCloud account at app.mindcloud.co if you do not already have one.
Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
Create a iDempiere connection in Connections. iDempiere uses its own authentication scheme. You provide whatever it requires when you create the connection — MindCloud handles the provider-specific details for you.
Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected iDempiere account that should run the action. MindCloud stores and refreshes the iDempiere credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling Create Contact with an iDempiere connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/iDempiere/actions/create-contact/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "arguments": {}
}'

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which iDempiere account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect iDempiere SOAP Web Services

You need the root URL of your iDempiere server, a user account that can access the web service, and a Web Service Security entry for each service type you plan to call.

Copy your server root URL
Enter the base host for your iDempiere instance, for example https://your-server.com. MindCloud appends /ADInterface/services/ModelADService?wsdl automatically.
Create or verify Web Service Security entries
In iDempiere, configure a Web Service Security record for each SOAP query you want to use. The Search Key becomes the serviceType value sent in requests.
Collect your AD login context
Enter username, password, language, client ID, role ID, organization ID, warehouse ID, and stage using the same values required by ADLoginRequest.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.