myWebLog API Service
Two APIs are provided: the Main API for club/organization servers, and the Mobile API for apps. Both are in version 5, built on the same framework.
Main API
For administrative tasks on a club/organization server: users, objects, bookings, economy and more.
Main API v5 Current version
Use this version for all new integrations. Coming from v4? The documentation has a guide to moving from v4 to v5.
Documentation →Older versions
Main API v4 Until 2027-09-30
Not developed or changed. From 2027-10-01 every call is answered with an error. Move to v5 before then.
Documentation →Main API v3.1 Deprecated 2026-11-01
Operational until 2026-10-31. From 2026-11-01 every call is answered with an error. Move to v5 before then.
Documentation →Mobile API
For apps: the member logs in through the app (OAuth 2.0) and sees their own objects, bookings, flight log and account.
Mobile API v5 Current version
Use this version for all new apps. Coming from v3? The documentation has a guide to moving from v3 to v5.
Documentation →Older versions
Mobile API v3 Until 2027-09-30
Not developed or changed. From 2027-10-01 every call is answered with an error. Move to v5 before then.
Documentation →API Access
Main API: each booking system administrator can create their own API authorization keys. Log in to myWebLog as a booking system administrator and select ADMIN > System settings > Authorization > API access from the menu. Each API key can be restricted to one or more IP addresses, if desirable. Readonly or read/write access can be assigned per module (users, objects, economy, bookings etc.) per key. This facilitates a customized and appropriately limited access for different API function users.
Mobile API: please contact support@myweblog.se to apply for access. Each app gets a client id and a key; the key is handed over through a link that works once.
Customized API functions
Other types of customized API functions may be available on request. Please contact support@myweblog.se with your query.