Prerequisites
1. An application and an access credential
SOFT Integration is consumed with the same credentials as the rest of the AI Services: an APP Id and an API Key associated with your registered application.
If you do not have an application registered yet, follow the procedure described in Credentials.
2. The GENESIS-SOFT-INTEGRATION permission
Each API Key carries a set of permissions that determine which services it can consume. To issue SOFT Integration
signatures, the API Key must hold the GENESIS-SOFT-INTEGRATION permission.
| Behaviour | Description |
|---|---|
| Newly created API Keys | The permission is enabled by default. |
| Existing API Keys | Not enabled automatically. Enable it per API Key from the administration console. |
| API Key without it | Generate signature responds 403. |
3. An access token
Every REST call in this section is authenticated with a Bearer token obtained from /api/v1/token, exactly as for
the rest of the AI Services:
- Concatenate APP Id and API Key separated by
:. - Encode the result in base64.
- Send it as
Authorization: Basic <token>to/api/v1/token.
const token = btoa(`${appId}:${apiKey}`);
const response = await fetch(
"https://api-suite.invoxmedical.com/api/v1/token",
{
method: "POST",
headers: { Authorization: `Basic ${token}` },
body: JSON.stringify({ grant_type: "client_credentials" }),
},
);
const { accessToken } = await response.json();
The access token is valid for two hours. The full procedure is described in Credentials.
4. Physicians registered in the platform
SOFT Integration does not create users. Every physician you open a consultation for must already exist in your Invox Medical organization, be enabled, and be identified by the same email address you send in the signature request.
Users are created from the administration console or through Invite user.
5. Optional: a notification channel
Decide how you want to be told that a consultation has finished:
- Webhook — configure the
OnMedicalReportFinisheddestination for your organization. SOFT Integration reuses that event. - WebSocket — no configuration needed; you open the connection with the same signature.
Both channels can be used at the same time. See Notifications overview.