Corporate API


If you have a corporate account, these functions can be very useful to program the wubook services.


To launch these functions, you need to use a Token acquired with the credentials of your corporate account.

Global Information

corporate_fetch_accounts(token[, acode])

Returns a KV struct, each Key being the account code, and the Value being another KV struct with the information about the account (like coins, the list of properties, …).

corporate_get_providers_info(token[, acodes=[]])

Returns a list of providers that accessed corporate’s sub-accounts through Wired, each value of this list being a KV struct with the fields pkey (Provider Key), emails (of the provider) and acode (the accessed account code).

The filter acodes is a list of account codes; an empty one will return information for every corporate’s sub-account.

corporate_fetch_channels(token, lcode)
corporate_get_channels(token[, filters])

The corporate_get_channels(), called without the filters argument, returns all of the channels of all of your properties. If you want to filter results, you can pass them inside the KV structure filters, which supports the following (optional and not exclusive) filters:

  • dfrom: channels expiring not before this european date

  • dto: channels expiring before this european date

  • lcodes: a list of lcode, to return channels of a specific set of properties


This function is used to receive a list of properties having new reservations to be fetched. If you use the Push Notification feature, this function could be periodically called (let’s say with a 4 hours frequence) to prevent problems arising from missing notifications. That’s of course seriously better than periodically cycling all of your properties with a fetch_new_bookings() call.


This function could return False Positive cases: properties tagged as “fetchable” but having no new reservations/modifications/cancellations. If you want them to desappear from the list, please, call mark_bookings()

Create accounts and properties

corporate_new_property(token, lodg, woodoo_only, acode)
corporate_new_account_and_property(token, lodg, woodoo_only, account)

Those functions are used to add new properties on your corporate account. The first one will be used when the new property has to be associated to an existing account. The second one will be used when you also need a new account owning the property.

For both functions, the lodg parameter is a KV struct containing the following values:




The name of the property


The address of the property


The url of its site


Zip code










Two digits code (IT, ES, ..)

While using corporate_new_account_and_property(), you need to pass a similar KV structure to define a new account, having the following values:




The name of the account owner


The last name of the account owner




Two digits code (IT, ES, ..)




Three digits code (EUR, USD, ..)

Notice that both functions return information about the new property and, eventually, the new account. The return values is in fact a KV structure containing the lcode (property identifier), acode and password (username and password assigned to the new account) values.

Click on the following link to have a corporate_new_account_and_property() xml example.

+ show/hide code

Renewing services

corporate_renew_booking(token, lcode, months[, pretend= 1])
corporate_renew_channels(token, lcode, channels[, pretend= 1])

Those functions are used to renew your services (with coins). They return the number of used coins. For both functions, you have an optional argument: pretend. When 1, you are just making a simulation.

For the corporate_renew_booking() function, the argument months is an integer representing the number of months you want to renew.

For the corporate_renew_channels() function, the channels argument is a KW structure, having Channel IDs as keys and, as values, a renewal quantity. A simple example will make these concepts clearier:

channels= {
  '111': '3d', # it means: renew the channel with ID= 111 for three days
  '112': '2m', # 2m= 2 Months
  '113': '2',  # 2= 2 Months (m is the default unity),
  '114': '1y', # 1y= 1 Year

As you can see, you can use an integer (in this case, it is considered a number of months) or you can specify a string with a final “d”, “y” or “m”, respectively for days, years and months.

corporate_set_autorenew_wb(token, lcode, set_autorenew)
corporate_set_autorenew_zak(token, lcode, set_autorenew)

Those functions allows to setup the autorenew feature. They accept the argument set_autorenew, which is an integer. If 1, you are activating the autorenew feature, while 0 disables it.

corporate_set_channel_status(token, lcode, lchans, running)

Since channels don’t have autorenew but can only be either running or paused, the function for them is a bit different.

running is a boolean integer:

  • If 0, it will change the status to paused for the channels in lchans

  • If 1, it will change the status to running for the channels in lchans

lchans argument is an array of Channel IDs.

Balance and transactions

As for direct users, corporate can programmatically read the additional costs that WuBook is registering for your users. It is possible to use the following functions:

corporate_balance_details(token, transaction_id)

They work as described in the section Transactions with small differences. In particular, the corporate_balance_details function will return richer information: each item of the array will contain the field:

  • account: the user account code

So that you will be able to detect which account generated your costs.