DATEV Online APIs (Sandbox)
Sandbox environment for the DATEV Online APIs — read accounting Mandanten (clients), document types and DUO version metadata against DATEV's test data. Use this while you build and test; every new DATEV app must run in sandbox until DATEV grants production approval. Same OAuth2 Authorization Code + PKCE flow as production, pointed at DATEV's sandbox endpoints.
7-day free trial · No credit card · EU-hosted
Ask DATEV anything
Try a real prompt against DATEV Online APIs (Sandbox) via AnythingMCP — Claude calls the tools, returns the answer. Press Enter on your own message to install on Cloud.
Install DATEV on CloudClaude is AI and can make mistakes. Please double-check responses.
Setup in 2 minutes
- 1Start a free trial on cloud.anythingmcp.com.
- 2Click DATEV Online APIs (Sandbox) in the connector store. Paste credentials when prompted.
- 3Mint an MCP API key and point your AI client at the generated MCP URL.
Setting up DATEV Online APIs (Sandbox)
From the connector definition itself: where to find the credentials, what they need to be allowed to do, and which API this adapter talks to.
Use this connector for testing. Every DATEV app runs in the sandbox until DATEV completes its production-approval review — so this is where you start.
Setup:
- Create a Confidential app on the DATEV-Entwicklerportal (https://developer.datev.de) with OpenID Connect Authorization Code Flow. Set the redirect URI to
<your-server>/api/mcp-oauth/callback. - Subscribe the app to the sandbox API products: accounting:clients 2.0 and accounting:documents 2.0.
- Set
DATEV_CLIENT_IDandDATEV_CLIENT_SECRET(from the portal — copy the secret in full, it is shown only once). - Import this adapter — it is pre-configured for the sandbox (authorize
login.datev.de/openidsandbox/authorize, tokensandbox-api.datev.de/token, API baseplatform-sandbox/v2) and authenticates at the token endpoint via HTTP Basic (client_secret_basic), which DATEV requires. - Run the one-time OAuth flow:
POST /api/connectors/{id}/oauth/authorize-> open the returned URL -> log in with your DATEV-Konto -> the platform stores an encrypted refresh token automatically. - Every call then sends
Authorization: Bearer <token>AND the mandatoryX-DATEV-Client-Id: <DATEV_CLIENT_ID>header automatically.
Going to production: once DATEV approves your app for production, use the separate DATEV Online APIs connector (same credentials, production endpoints).
Scopes requested: datev:accounting:clients accounting:clients:read accounting:documents. Do NOT add openid — it is the issuer name, not a requested scope.
Mandant scoping: every per-client tool takes a clientId parameter — the Mandant UUID (RFC4122), returned by datev_list_clients. Distinct from DATEV_CLIENT_ID (the OAuth app identifier, sent in the header).
Your AI is two clicks away from DATEV Online APIs (Sandbox).
Install the connector, paste your credentials, ask your AI a question. 7-day free trial, no credit card.