On the project page you're stating:

Please report back. I need bug-testers ;)

That's good to know, but to test something we need to get it working first. At least for new users it is impossible to guess which submodules are actually required to accomplish which functionality, and what other modules are required to set up any end-user functionality (probably either 'Public Bookings' or 'Event Bookings', where both modules appear to provide similar functionality).

For example, the current dev release of 'Bookins API' sets up a weird content type with (non CCK) fields like "Location", "Parent", and "Default Availability". Which location? Whose parent? Default availability of what? Has location anything to do with geospatial data like provided by the 'Location' module, and does it integrate somehow with existing locative data, or is this a non-geographical location like "Room 302" or "Storage locker 27498B"? Do we need to manually add a CCK date field to the 'bookingsapi_resource' content type, and if so: which settings does 'Bookins API' require?

Also please note that the documentation available at http://groups.drupal.org/node/34868 is misleading and completely outdated, especially the "Steps to use Public Bookings and Bookings API" have no resemblance how 6.x-3.x-dev actually is working.

So, could someone of this module's users please update the documentation?