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 días gratis · sin tarjeta · hosting UE
Pregunta cualquier cosa a d.velop
Prueba un prompt real contra d.velop documents vía AnythingMCP — Claude llama a los tools y responde. Pulsa Enter en tu mensaje para instalar en Cloud.
Instalar d.velop en CloudClaude es IA y puede equivocarse. Verifica siempre las respuestas.
Setup en 2 minutos
- 1Inicia trial gratuita en cloud.anythingmcp.com.
- 2Click en d.velop documents en el connector store. Pega las credenciales.
- 3Genera MCP API key y apunta el cliente AI a la URL MCP.
Guías para d.velop
Setup paso a paso para los principales clientes AI.
Configurar d.velop documents
Directamente de la definición del conector: dónde encontrar las credenciales, qué permisos necesitan y con qué API habla este adaptador. Proporcionadas en inglés por el autor del conector.
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.
Tu IA está a dos clicks de d.velop documents.
Instala el conector, pega credenciales, pregunta a la IA. 7 días gratis, sin tarjeta.