Haufe X360
Haufe X360 cloud ERP (the German Acumatica distribution): customers, stock items, sales orders, invoices and shipments over the contract-based REST API. Cookie-session auth against your own tenant. Partner credentials required.
7 天免费 · 无需信用卡 · EU 托管
问 Haufe 任何事
通过 AnythingMCP 对 Haufe X360 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 HaufeClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Haufe X360。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 Haufe X360
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
Partner credentials required. Haufe X360's API is not self-service: access is arranged through your Haufe implementation partner, who enables the endpoint on the tenant and creates the integration user. Do not expect to find an API key in the web UI.
Setup
- Ask your partner to publish the Default contract-based endpoint (or a custom one) and note its version — typically
Default/20.200.001. - Have them create a dedicated API user with the licence type that permits API access, and the roles for the screens you want to read.
- Set
X360_URLto your tenant root (e.g.https://mycompany.haufe-x360.de, no trailing slash), plusX360_USERNAME,X360_PASSWORD, andX360_ENDPOINT_VERSIONif it differs from the default. A tenant with several companies also needsX360_COMPANY.
Acumatica's session is a cookie, and there is a licence limit on concurrent sessions. The adapter logs in at /entity/auth/login and reuses the returned .ASPXAUTH cookie. Because the tenant licenses a fixed number of concurrent API sessions, a connector that logs in on every call will exhaust them; the cached session here is what keeps that from happening.
Field names are the screen's, not the database's. The contract-based API exposes the screen field names, e.g. CustomerID, CustomerName, OrderNbr — with values wrapped as {"value": …}. Read a row before composing a $filter.
OData-style filtering ($filter, $top, $skip, $expand, $select) works on the list endpoints. $expand=Details is what fetches an order's line items; without it you get the header only.
Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.