XAPI or “XenAPI” is the management tool stack used in XenServer.

So for example to talk to XAPI (or the XenServer management interface on a XenServer) – you have to use the XenAPI toolstack.   XenCenter does this for example. And each host in a XenServer pool does this too – to talk to the Master in a pool.

XAPI is at the heart of XenServer. It manages everything – all the resources in your XenServer environment,

It reads in configs, initializes networking paths, checks licensing, maintains a Database with all this info (the XAPI database), manages Storage Repositories, manages VMs, tracks VM states, manages networking, High Availability and other XenServer hosts in the pool and more……

Each XenServer request or action is done via Xapi – and only by asking the Master XenServer XAPI to do so. A copy of the XAPI database (or you could consider this to be the state of XAPI) is synchronized among all the hosts in the pool – so they all have a copy of the current XAPI database – giving them the knowledge of what is going on – and in the case of the master going down – a new master can be appointed from the pool using the XAPI state information or shared database.

When you collect a status report from XenServer – the XAPI Database is stored in the status report. It is a relational database – and shows us the state of the environment at that point in time (when the status report was captured).