Technical documentation
Reference for XEN's API, event system, webhooks and protocols for agents, for the technical team integrating the platform with its own systems.
The reference is published section by section, in the order of this index.
Each section ships with its request and response examples checked against the production server. A team that needs to integrate today receives the reference for the endpoints it uses and a person from Xeneural during the integration.
Request the reference for an integrationEight sections
Authentication
Every request carries the user's session token in the authorization header; the server validates it, resolves the user and rejects any request without a token before touching a single piece of data.
Organization scope
The active organization is resolved by the server from the session; the client never declares it in the request, so an identifier sent from outside cannot open another company's data.
Sales endpoints
Issuing documents, drafts and scheduled documents; status checks; credit and debit notes linked to the original; numbering by point of issue.
Inventory endpoints
Inbound and outbound movements, transfers between warehouses, adjustments with a reason, and querying physical and available balance per item and warehouse.
Event system
Every server result carries a small, sequential event code from a single registry; the codes are read from the same catalog in the application, in integrations and in agents.
Webhooks
Registering a destination per organization, payload format, signature to verify the origin, and retry policy when the destination does not respond.
Protocols for agents
How an external agent authorizes itself with MCP, AP2 and UCP, operates with the permissions of the user who authorized it, and leaves every action in the same history as a person.
Errors and codes
Shape of the error response, catalog of codes by family (validation, permissions, tax, integration) and what to fix in each case before retrying.