d.velop documents
d.velop documents (d.3one) DMS: search the repository, read document metadata and source properties, list repositories and categories. REST API on d.velop cloud or on-premises, bearer API key.
7 giorni gratis · senza carta · hosting UE
Chiedi qualsiasi cosa a d.velop
Prova un prompt reale su d.velop documents via AnythingMCP — Claude chiama i tool e risponde. Premi Enter sul tuo messaggio per installare su Cloud.
Installa d.velop su CloudClaude è un'AI e può sbagliare. Verifica sempre le risposte.
Setup in 2 minuti
- 1Avvia la trial gratuita su cloud.anythingmcp.com.
- 2Clicca d.velop documents nel connector store. Incolla le credenziali quando richiesto.
- 3Genera una MCP API key e punta il client AI all'URL MCP generato.
Guide per d.velop
Setup passo-passo per i principali client AI.
Configurare d.velop documents
Direttamente dalla definizione del connettore: dove trovare le credenziali, quali permessi servono e con quale API parla questo adapter. Fornite in inglese dall'autore del connettore.
Getting an API key
- In d.velop cloud open Konfiguration → API-Schlüssel (or, on premises, the identityprovider app) and create an API key for a technical user.
- Give that user read rights on the repositories the agent should reach. d.velop applies its permission model per document, so a restricted user quietly sees a smaller repository.
- Set
DVELOP_URLto your tenant root —https://<tenant>.d-velop.cloudfor cloud, or your own host on premises — andDVELOP_API_KEYto the key.
The Authorization header is Bearer <apikey>, with the API key used directly as the bearer token. d.velop's API keys are long-lived; rotate them the way you would rotate a password.
Repository ids come first. d.velop can host several repositories in one tenant and every document operation is scoped to one. Call d_velop_list_repositories and keep the id — it is an opaque string, not a number.
Responses are HAL JSON. d_velop_list_repositories returns repositories[] (id, name); a search returns items[], each with id, sourceProperties and sourceCategories, plus _links.next.href for the next page. page starts at 1 and pageSize defaults to 25.
Every search and document read needs a source id. d.velop maps its internal properties to a source, and the search (/srm) and document (/o2m) endpoints return property values only through that mapping: sourceid is required. Call d_velop_list_categories first: it returns the repository's default source with its id (normally /dms/r/<repositoryId>/source), its category keys and its property keys. Use that id as sourceid, the category keys in sourcecategories and the property keys in sourceproperties.
Not run against a live tenant. The paths and parameters follow d.velop's DMSApp OpenAPI specification (help.d-velop.de/dev/documentation/dms-app); d.velop does not offer a public sandbox. If you run this against a real system, a correction to the adapter JSON is genuinely welcome.
Read-only by design: no upload, no property change. A DMS is the audit trail, and an agent should not be able to edit it by accident.
La tua AI è a due click da d.velop documents.
Installa il connettore, incolla le credenziali, chiedi all'AI. 7 giorni gratis, niente carta.