The REST interface of your Advoware law firm software: control files, parties, appointments, deadlines, documents and billing from your own tools and partner systems. The data stays in Advoware, with no duplicate entry and no break in media.
Advoware API
The REST interface of your Advoware law firm software: control files, parties, appointments, deadlines, documents and billing from your own tools and partner systems. The data stays in Advoware, with no duplicate entry and no break in media.
The interface to your law firm software: control case files, parties, appointments, deadlines, documents and billing directly from your own tools and partner systems. The data stays in Advoware, while the work happens wherever you do it.
Years of case files, parties, pleadings and deadlines are stored in Advoware. More and more work is created in other tools. The API connects the two, without data leaving the law firm or being maintained twice.
Connected tools read case files, history and documents directly from Advoware and write results back. No exports, no clipboards, no break in the workflow.
Whether it is an AI assistant, mobile time recording or a client portal: your team opens the case file in the tool they are working in and finds the complete, up-to-date record from Advoware there.
Every access runs through a user of the law firm with their own password for advoware online services and an HMAC-signed token with a limited lifetime (3,600 seconds). The law firm decides which systems are connected through its access credentials.
Law firms should not have to choose between the place where their knowledge resides and the place where their work happens. With the Advoware API, the two work together.
Export the case file, load it into the tool
Download the result, file it in Advoware
Open the case file in the tool, send the result back to the case file
The Advoware API is a REST interface based on OpenAPI 3. Any application that speaks HTTPS can read and write data in Advoware. Here are three examples of what law firms and partners build with the Advoware API.
/api/v1/advonet/Akten/api/v1/advonet/Akten/{akteId}/History/api/v1/advonet/Files/{historyId}/api/v1/advonet/Akten/{akteId}/History/api/v1/advonet/Honorarzeiten/api/v1/advonet/Rechnungen/api/v1/advonet/Akten/{akteId}/MandantenHonorarSaldo/api/v1/advonet/Statistiken/Umsaetze/api/v1/advonet/Terminealso PUT · POST · DELETE/api/v1/advonet/Todosalso PUT · POST · DELETE/api/v1/advonet/Wiedervorlagen· POST /Vorgelegt/api/v1/advonet/FristArten· /FeiertageRead and write access to the law firm's core objects. Base URL of all endpoints: /api/v1/advonet.
| Resource | What the API covers | Methods |
|---|---|---|
| Case files | Search, create, change · Case file history · Department data · Case file balance · Folder structure | GETPOSTPUT |
| Parties | Addresses · Bank details · Contact persons · Communications · Involvement in case files | GETPOSTPUTDELETE |
| Appointments & deadlines | Create, change and delete appointments, tasks and follow-up reminders · Deadline types · Public holidays · Submitted items | GETPOSTPUTDELETE |
| Documents | Upload/download · History and history tree · Incoming/outgoing mail · Dispatch methods | GETPOST |
| Billing | Billable time · Invoices · Receivables · Postings · Billing types · Revenue and case file statistics | GETPOSTPUT |
| Master data & communication | Employees, departments, legal forms, custom fields · Law firm chat and activities | GETPOSTPUT |
As of October 2026, according to the interface description, variant "advoware connector v1 for employees" (93 paths, 120 operations). A second variant, "v1 for clients", is also documented there. The API is continually being revised and is subject to change.
The interface is not technically restricted, so it is not priced in tiers either. There is one licence at one price; how many licences a connection needs depends solely on the number of case files it accesses.
What matters is the number of case files accessed, per connection and year. Two connected third-party systems count as two items, each with its own tier.
| Case files accessed · per connection and year | API licences | Price per month | Price per year |
|---|---|---|---|
| up to 500 case files | 1 | €79 | €948 |
| up to 2,500 case files | 2 | €158 | €1,896 |
| up to 10,000 case files | 4 | €316 | €3,792 |
| up to 40,000 case files | 8 | €632 | €7,584 |
| above that | custom | Enterprise agreement under the master contract | |
A law firm that only connects its telephone system pays for one licence. A firm that processes its entire stock of case files automatically pays for eight. The tiers ensure that everyone pays for what they actually receive.
Throughout the year, the law firm can see in the programme how many case files have passed through the interface. No surprise invoices, no retrospective charges for the past. Anyone who uses less than they booked is moved down a tier at renewal.
The API licence comes with fixed versions, announced changes and a point of contact. The product is the assurance that the interface is still open after the next update.
All prices exclude statutory VAT. As of September 2026, subject to change.
For Advoware law firms and integration partners. To connect, you need an app ID and API key, as well as a user with a password for advoware online services.
Briefly describe which system you would like to connect.
App ID and API key, plus a user in Advoware with a password for online services.
Retrieve the token, call the endpoints, take the connection live.
OpenAPI 3 description with all endpoints and schemas, plus an HMAC-SHA512-signed token request. Authentication in four steps.
Every law firm has a firm identifier. The configuration service returns the relevant gateway URL for it.
GET www2.advo-net.net/AdvonetConfigurator/api/Url?Kanzlei={Kanzleikennung}The string Product:AppID:Nonce:RequestTimeStamp is signed with HMAC-SHA512, using the Base64-decoded API key as the key. For third-party providers, Product is always 64. Upper and lower case matter throughout.
POST to the security gateway with law firm, database, user, online services password, nonce, timestamp and signature. Response: access token, valid for 3,600 seconds.
POST {securityGateway}/api/v1/TokenSend the token as a bearer in the Authorization header. All resources are located under /api/v1/advonet.
GET {host}/api/v1/advonet/Akten// Token request · HMAC-SHA512 · Base64 // Signature = Base64( HMAC-SHA512( // "64:APPID:nonce:timestamp", Base64Decode(apiKey) ) ) POST {securityGateway}/api/v1/Token { "AppID": "YOUR-APP-ID", "Kanzlei": "FIRM-IDENTIFIER", "Database": "ADVOWARE", "User": "EMPLOYEE-INITIALS", "Role": 2, "Product": 64, "Password": "advoware online services password", "Nonce": "9f1c2e4a-…", "RequestTimeStamp": "2026-10-12T09:30:00Z", "HMAC512Signature": "…" } // Response { "token_type": "Bearer", "access_token": "eyJ…", "expires_in": 3600 } // Afterwards GET {host}/api/v1/advonet/Akten Authorization: Bearer eyJ…
Prerequisites: firm identifier (as for the advoware Manager or the release service), app ID and API key, and a user with a password set for advoware online services. The interface description notes that the API is continually being revised and that changes, including incompatible ones, may be made at any time.
