myWebLog API v5: version history
What this page is
What changed in each version of the Main API v5, latest first, in short. The details are on the API page, where each change is marked "New in" with its version. The version in use is "info.version" in openapi.yaml. A new version only adds; when something a caller sees changes, the API page says so.
The history starts at version 5.15.
5.25.0
2026-11-22.
- An organization can be closed temporarily by its administrator on the website. While it is closed every endpoint gives 403 with code 10342, and "detail" has the organization's message.
5.24.0
2026-11-17.
- The country as its ISO 3166-1 two-letter code ("SE"), next to the name: address.country_code in the block address of GET /users and GET /users/{id}, and location.country_code in GET /organization. country is still the name ("SWEDEN").
- The mobile number as one international number: phone.mobile.e164 ("+46701234567") and phone.mobile.country ("SE") in GET /users and GET /users/{id}, and accepted by POST /users and PATCH /users/{id}. phone.mobile.country_code, initial_number and number are deprecated: still sent and accepted until 2027-06-30.
5.23.1
2026-11-16.
- GET /flightlog-options: each object has clock_times, "local" or "utc", the clock rule of the organization that owns the object. For a shared object it is the owner's rule, which is the rule a flight on it is stored in, so an app can mark the time fields and calculate a total before the flight is logged. null when the owner does not have the feature yet.
5.23.0
2026-11-14.
- The clock times of the flight log, in UTC or local time. An organization states on the website whether its logbook is in local time at each airport (LCL) or in UTC. date, blockoff_at, takeoff_at, landing_at and blockon_at of a flight are, and have always been, the logbook's own clock times written with a Z: for most organizations local time, not UTC. The documentation called them points in time in UTC; that text is corrected. The values are unchanged.
- New on a flight (GET /flightlogs, GET /flightlogs/{id} and the reply of POST /flightlogs): clock_times ("local" or "utc"), time_zone and utc_offset in departure and in arrival, and the true points in time in UTC: departure.blockoff_utc, departure.takeoff_utc, arrival.landing_utc and arrival.blockon_utc. The four ..._at fields are deprecated in favour of them and stay as they are for all of version 5.
- GET /organization has logbook: clock_times, home_time_zone and answered.
- POST /flightlogs and POST /flightlogs/preview take clock_times, "utc" or "local": how the times of the body are to be read. The server converts them when the logbook's rule is the other one. Left out, the times are stored as sent, as before. New code 11090.
- Until the website opens this to every organization, only its test organizations have the new fields and can send clock_times. Nothing that exists changes, for any organization.
- In an organization that has the logbook's clock: a total that is not sent is worked out as the time that passed, also between two time zones, and "A flight can not be logged in the future" compares true points in time.
5.22.0
2026-11-14.
- A member's expiry date has image_missing: the type requires an image and the date has none (GET /expiry-dates, GET and PUT /users/{id}/expiry-dates, and the block expiry_dates of GET /users).
- expired is now as the website judges the date at booking: also true when the type requires an image and the date has none. The filter expired of GET /expiry-dates does the same.
- "Today" is the organization's day, in its time zone, not the server's.
5.21.0
2026-11-14.
- An expiry date type has applies_to: which members the type applies to, by user group and membership (only, except), as "Applies to" on the website.
- POST and PATCH /expiry-date-types take applies_to, from every organization since the website's launch the same day.
- The lists of the members' dates are as before.
5.20.0
2026-11-07.
- POST /flightlogs gives meta.remark_ids: the id of each remark written with the flight, so photos can be added to them with POST /remarks/{id}/images.
5.19.0
2026-11-05.
- Images on remarks: up to two on a remark, and one on each comment or closing. GET, POST and DELETE /remarks/{id}/images.
- A remark gives its images, and each item its id and image.
- New codes 10337 to 10341.
5.18.0
2026-11-01.
- Simulators: objects of category 3, with simulator_class and the simulated type.
- Flight logs give object.category and is_simulator, and take the filter simulator=true|false.
- A simulator session is logged with POST /flightlogs.
- A flight with several remarks is given once in the flight log.
5.17.0
2026-10-31.
- Engine cycles: engine_cycles on flights and in POST /flightlogs; the objects' settings, cycles left, totals and maintenance items in cycles.
5.16.0
2026-10-21.
- Booking types: booking_type on every booking, booking_type_id in POST and PATCH /bookings.
5.15.1
2026-10-18.
- The flight log no longer gives the empty rows of an object's journey log.
5.15.0
2026-10-18.
- The flight log also gives the flights on objects shared with the organization, as the website's journey log does.