Haufe X360

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

1. Ask your partner to publish the Default contract-based endpoint (or a custom one) and note its version — typically Default/20.200.001.
2. 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.
3. Set X360_URL to your tenant root (e.g. https://mycompany.haufe-x360.de, no trailing slash), plus X360_USERNAME, X360_PASSWORD, and X360_ENDPOINT_VERSION if it differs from the default. A tenant with several companies also needs X360_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.