myWebLog Mobile API v5

Current version: 5.46.0, 2026-11-22. What changed in each version: Version history.

What it is

The Mobile API is what an app shows a member of an organization: their objects, bookings, flight log, balance and transactions, the bookings they make, and their payments (Swish, by card through Nets Easy, or in their bank). It is built on the same framework as the Main API v5: the same addresses, replies, errors and headers. What differs is who calls: an app, on behalf of one member, instead of an organization's own server.

The machine-readable description of the API is openapi.yaml (OpenAPI 3.0). The same endpoints are ready to try in Postman: import postman_collection.json.

Coming from v3? Moving from v3 to v5 lists every difference, function by function, with what to change.

Address

https://api.myweblog.se/mobile/v5/{resource}, for example https://api.myweblog.se/mobile/v5/me

One item is addressed by its id in the path, for example /objects/710. An address does not end with a slash: /me works, /me/ gives 404. A query parameter the endpoint does not know gives 400, so a misspelled filter is never silently ignored.

Two identities: the app and the member

The app is a client in the words of OAuth 2.1. A developer gets a client id from myWebLog (write to support@myweblog.se) and registers the app's redirect addresses. An app with a server of its own also gets a key, handed over through a link that works once; the key must be kept out of source code repositories and out of app binaries that users can unpack. An app without a server (a native iOS or Android app) gets no key: it is a public client, which identifies itself with its client id and PKCE. A client has rights per module, set by myWebLog, and can be limited to some organizations. myWebLog can revoke a key or a client; the app then stops working at once.

The member logs in on myWebLog's own login page, which the app opens in the phone's browser (OAuth 2.1: the authorization code flow with PKCE). The app never sees the password. The app gets an access token, valid an hour, and a refresh token, valid 90 days from its last use. The member sees the login on My settings on the website, next to the app's name, and can end it there. A password change ends every login.

Two kinds of account

New in version 5.14. A login is either a member of an organization or a personal logbook account: a myWebLog user without an organization, who keeps a personal pilot logbook on the website. "account" in GET /me says which ("member" or "logbook"). A member has the organization's endpoints (objects, bookings, the flight log, transactions, payments, messages); a personal logbook account has the /logbook endpoints and nothing of the organization's. /client, /texts, /me, /me/photo, /me/profiles, /me/devices/{token}, /me/notification-settings and (since 5.23) /airports serve both. A call to the other kind's endpoint gives 403: code 10324 for a personal logbook account on a member's endpoint, 10325 for a member on /logbook.

An app that supports personal logbook accounts has the module logbook; without it the login page refuses such an account. An app's organization limit is about members and does not stop a personal logbook account, which belongs to no organization. A personal logbook account is paid for a period: when it has run out, the login and GET /me still work ("logbook.is_expired" is true, "logbook.valid_until" says since when) but the /logbook endpoints give 403 with code 10326 until the account is renewed on the website. A member whose personal logbook account is connected to their member login on Manage profiles can switch between the two in the app (GET /me/profiles). While this is new, myWebLog opens it to a few accounts at a time; the login page tells the others.

Push notifications

New in version 5.20. myWebLog's own apps get push notifications through APNs (iOS, topic se.myweblog.app) and FCM (Android). The app registers the phone with PUT /me/devices/{token} on every launch and after every profile switch, and removes it with DELETE /me/devices/{token} on logout, before POST /oauth/revoke. The member chooses what they get with /me/notification-settings. Only myWebLog's own apps get pushes; another app may call these endpoints, but its phones get nothing.

A push is sent, by "type":

message: a new message is in the member's inbox. Title "Nytt meddelande från [organization]", the body is the subject. Android channel "messages".

booking_cancelled: someone else cancelled a booking where the member is the booker or the student. Title the organization's name, body "Din bokning av SE-XYZ 2026-10-18 09:00 är avbokad". Android channel "bookings".

booking_changed: someone else moved such a booking (another time or object: "... är ändrad till 2026-10-18 10:00-12:00") or ended it early ("... har avslutats"). Android channel "bookings".

badge: the number of unread messages changed (a message read, archived or acknowledged, here or on the website) in the phone's profile or one of its other profiles. A silent push that only sets the badge; after it, fetch GET /messages to refresh the list, and GET /me/profiles for the profile menu's numbers. "profile_id" says whose number changed.

Nothing is pushed for what the member did themselves, in the app or on the website. The texts are in the device's language. Since 5.21 "badge" is the total unread over the profile the phone is logged in on and its other profiles (GET /me/profiles): the current profile's meta.unread from GET /messages plus every unread_messages in GET /me/profiles. Before 5.21 it was the logged-in profile's only. A member with several profiles also gets the pushes of their other profiles; "profile_id" then says which, and the app switches with POST /oauth/token and profile_id. "id" is the message's or the booking's id (for a booking that a change moved to a new row, the new id).

iOS alert: {"aps":{"alert":{"title":"...","body":"..."},"badge":3,"sound":"default","thread-id":"message"},"type":"message","id":4711,"profile_id":66388}
iOS badge (apns-push-type background): {"aps":{"content-available":1,"badge":2}}
Android alert: "notification":{"title":"...","body":"..."}, "data":{"type":"booking_cancelled","id":"812334","profile_id":"66388","badge":"3"}
Android badge: "data":{"type":"badge","badge":"2","profile_id":"66388"}

Live Activity (iOS only): the app starts a Live Activity on the lock screen when the member's booking begins, and registers its push token with PUT /bookings/{id}/live-activity. The server then pushes to that token (apns-push-type liveactivity, topic se.myweblog.app.push-type.liveactivity, apns-priority 10, apns-expiration 0), through the environment of the iPhone the login registered:

update, status "ongoing": someone else moved, extended or shortened the booking, or moved it to another object, and it still goes on. Also when the member changed it on the website, with changed_by_other false and no alert; a change made in the app gets nothing, since the app updates the activity itself.

end: status "cancelled" when the booking was cancelled, and "ended" when it was ended early, a change moved it so that it has already ended, or it reached its end time. When a change put the booking in a new row last in a queue, the activity ends with status "ended" too (the old row is gone, and the member does not have the object). After a cancellation or a move into a queue the activity leaves the lock screen at once (dismissal-date); otherwise iOS keeps it a while.

"content-state" always has all its fields: status, start and end (the booking after the change, ISO 8601 with the organization's offset), changed_by_other, registration and object_type (the object after the change; object_type as object.category.name in GET /bookings/{id}). "timestamp" is when the change was made. "alert" is only there for someone else's change, in the phone's language.

{"aps":{"timestamp":1760772600,"event":"update","content-state":{"status":"ongoing","start":"2026-10-18T09:00:00+02:00","end":"2026-10-18T11:30:00+02:00","changed_by_other":true,"registration":"SE-XYZ","object_type":"Aircraft"},"alert":{"title":"Bokningen är ändrad","body":"SE-XYZ är nu bokad 18.10.2026 09:00-11:30"}}}
{"aps":{"timestamp":1760778000,"event":"end","content-state":{"status":"cancelled","start":"2026-10-18T09:00:00+02:00","end":"2026-10-18T11:30:00+02:00","changed_by_other":true,"registration":"SE-XYZ","object_type":"Aircraft"},"dismissal-date":1760778000,"alert":{"title":"Bokningen är avbokad","body":"Din bokning av SE-XYZ 18.10.2026 09:00 är avbokad"}}}

start (new in 5.31, iOS 17.2 and later): the server starts the activity itself 30 minutes before the booking begins, also when the app is not open, through the phone's push-to-start token (live_activity_start_token in PUT /me/devices/{token}). It is sent when the booking is the member's own, as booker or student, and not in a queue; the phone is logged in on that profile (not on a connected one) and has a start token; no activity is registered for the booking with PUT /bookings/{id}/live-activity; and the member has not turned off booking_changed in /me/notification-settings. A booking that is made or moved so that it begins within 30 minutes gets it within a minute. At most one start push per booking. iOS then wakes the app with the activity's own token, and the app registers it with PUT /bookings/{id}/live-activity as when it starts one itself; the pushes above follow from there.

The start push has status "scheduled", the "attributes" of the activity (bookingID, the organization's name in club, and the widget's texts in labels, in the phone's language) and always an alert. object_type is the category's name as above: Aircraft, Equipment, Premises or Simulator.

{"aps":{"timestamp":1760770800,"event":"start","attributes-type":"BookingActivityAttributes","attributes":{"bookingID":812334,"club":"Test FK","labels":{"scheduled":"Startar [[TIME]]","ongoing":"Pågår","ended":"Avslutad","cancelled":"Avbokad","moved":"Flyttad till kö","changedByOther":"Ändrad av någon annan","remaining":"kvar"}},"content-state":{"status":"scheduled","start":"2026-10-18T09:00:00+02:00","end":"2026-10-18T11:00:00+02:00","changed_by_other":false,"registration":"SE-XYZ","object_type":"Aircraft"},"alert":{"title":"Snart dags","body":"Din bokning av SE-XYZ börjar 09:00"}}}

Logging in (OAuth 2.1: the authorization code flow with PKCE)

This is the standard flow that AppAuth (iOS and Android), flutter_appauth, react-native-app-auth and every OAuth client library implement: give the library the authorization URL, the token URL, the client id, the redirect address and (for a client with a key) the client secret, and it does the steps below.

  1. The app makes a random code_verifier (43 to 128 characters of A-Z, a-z, 0-9, - . _ ~) and its code_challenge = BASE64URL(SHA-256(code_verifier)).
  2. The app opens GET /oauth/authorize?response_type=code&client_id=…&redirect_uri=…&code_challenge=…&code_challenge_method=S256&state=… in the system browser (ASWebAuthenticationSession on iOS, Custom Tabs on Android; never an embedded WebView). The API sends the browser to the login page on www.myweblog.se.
  3. The member logs in there and allows the app. The page sends the browser to redirect_uri?code=…&state=… (or error=access_denied if the member cancels). The app checks that state is its own.
  4. The app posts the code to /oauth/token with grant_type=authorization_code, redirect_uri, code_verifier and the client's credentials, within two minutes, and gets the tokens. A code works once.

POST /oauth/token takes the body as form data (application/x-www-form-urlencoded). A client with a key sends it in a Basic Authorization header (client_id:key) or as the fields client_id and client_secret; a public client sends client_id alone.

grant_type Fields Reply
authorization_code code, redirect_uri, code_verifier, and if you like device_name (what the member sees on My settings, such as the phone model) access_token, token_type, expires_in (3600), scope, refresh_token
refresh_token refresh_token A new access_token and a new refresh_token. The old refresh token is dead at once. Only the client that made the login can renew it.
refresh_token (switch profile) refresh_token, profile_id (from GET /me/profiles) An access_token and a refresh_token for the chosen profile. The login the refresh token stood for ends.
client_credentials none An access_token for the app alone, good for GET /client ("does my key work") and GET /texts only. Not for a public client, which has no key.

Every other call carries the access token: Authorization: Bearer [access token]. When it has expired the API answers 401 with WWW-Authenticate: Bearer error="invalid_token"; renew with the refresh token and retry. Renew when a call says so, not before every call.

Logging out: POST /oauth/revoke with the form field token = the refresh token (and the client's credentials). The refresh token and the access tokens fetched with it stop working. The reply is 200 also for a token that is already gone, so a logout never fails.

A code that is not valid, expired or already used gives 400 with error invalid_grant; so does a refresh token that is no longer valid, with an error_description meant for the app's user. Treat invalid_grant on a refresh as "logged out" and open the login again. The website's limits on failed logins apply on the login page. There is no password grant: OAuth 2.1 removed it, and no app, myWebLog's own included, ever handles a member's password. The replies of the /oauth endpoints follow the OAuth standard, not the Problem Details form of the other endpoints.

Redirect addresses: an https address the app has claimed (a universal link or Android app link) is safest; the app's own scheme in reverse-domain form (se.flygklubben.app:/oauth) also works. They are registered by myWebLog and compared exactly. For Postman, register https://oauth.pstmn.io/v1/callback.

In Postman: Authorization type OAuth 2.0, grant type Authorization Code (With PKCE), auth URL https://api.myweblog.se/mobile/v5/oauth/authorize, access token URL https://api.myweblog.se/mobile/v5/oauth/token, callback URL https://oauth.pstmn.io/v1/callback with "Authorize using browser" off, client ID (and client secret, for a client with a key; "Send as Basic Auth header"), code challenge method SHA-256. Get New Access Token opens the login page.

Sending data

POST and PATCH take a JSON object as the request body. The exceptions are the two /oauth endpoints, which take form data as the OAuth standard says. The id of the item is never in the body: it is in the address.

A value in the body has the same type as in a reply. Text is text: a member number is sent as "007", not as 7. An id is a number, yes or no is true or false, an amount is a number, a date is written "2026-09-30", and a point in time "2026-09-30T08:00:00Z" or with an offset, "2026-09-30T10:00:00+02:00". A value of another type gives 400. A field the endpoint does not know gives 400.

Headers

Header In Description
Authorization Request Required: Bearer [access token]. For the two /oauth endpoints: Basic [client_id:key in base64].
WWW-Authenticate Reply With 401: Bearer, and error="invalid_token" when the access token has expired or is not accepted (renew).
Request-Id Request and reply Optional. Your own id for the request, at most 64 characters. It is returned with the reply, and in the body of an error reply. If you send none, one is made for you. Quote it when you contact support.
RateLimit-Limit
RateLimit-Remaining
RateLimit-Reset
Reply Calls allowed per minute, calls left in the current minute, and seconds until the count starts over. For a member's token the member's figures (120 a minute); for a client's own token the client's (600 a minute over all its members, unless the client has a limit of its own). Both limits apply to every call.
Retry-After Reply With 429: seconds to wait before the next call. With 503: seconds until myWebLog is expected to be open again, at least 60.
Allow Reply With 405: the methods the address accepts.
ETag
If-None-Match
Reply
Request
GET /texts: the ETag is a fingerprint of the texts. Send it back as If-None-Match, and the reply is 304 with no body when nothing has changed.

Replies

A successful reply has the result under "data". An error reply follows the standard "Problem Details" (RFC 9457) and has the content type application/problem+json. "code" is the number in the error code table at the end of this page. "errors" is only present when the error is about named parameters or fields, about booking rules (then without "field"), about what Swish refused (then with "swish_code"), or about what Nets refused (then with the field Nets objects to):

{
  "type": "https://api.myweblog.se/errors/validation",
  "title": "The request has invalid parameters",
  "status": 400,
  "code": 10005,
  "request_id": "b7e2c41a9d0f3e55",
  "errors": [
    { "field": "verbose", "code": 10007, "message": "Unknown parameter" }
  ]
}

While myWebLog is closed for maintenance, every call gets 503 with code 10060, the /oauth endpoints too (since 5.14.1). Nothing is done and nothing is saved. Tell the member that myWebLog is closed for maintenance and try again after Retry-After seconds:

HTTP/1.1 503 Service Unavailable
Retry-After: 1800
Content-Type: application/problem+json; charset=utf-8

{
  "type": "https://api.myweblog.se/errors/service-unavailable",
  "title": "myWebLog is closed for maintenance",
  "status": 503,
  "code": 10060,
  "request_id": "70ff6f93b908417d"
}

Lists

A list has its items under "data", and says where the page is in the list. limit says how many items to return (100 unless the endpoint says otherwise, at most 500), offset how many to skip. "has_more" says whether there are more items after the page, and "links.next" is the address of the next page. include_total=true also counts all the items that match, as "meta.total". The order of a list is fixed and given with each endpoint.

{
  "data": [ ... ],
  "meta": { "count": 20, "limit": 20, "offset": 0, "has_more": true },
  "links": { "next": "https://api.myweblog.se/mobile/v5/transactions?offset=20" }
}

include adds optional blocks to each item, separated by commas, where the endpoint has blocks (objects). exclude leaves out fields that an item always has, also separated by commas. A block or a field the endpoint does not have gives 400.

Endpoints

Click on an endpoint to see its details. "Right" is the module right the app's client needs for it; the member's token carries the client's rights.

token

GET
/oauth/authorize Sends the member's browser to myWebLog's login page, where the member logs in and allows the app (the authorization code flow).
Information Parameters Response

Opened in the system browser by the app (its OAuth library does it), not called from code. Answers 302 to the login page on www.myweblog.se with the same query string. The member logs in and allows the app there; the page then sends the browser to redirect_uri with code and state, or with error=access_denied when the member cancels.

The code is exchanged at POST /oauth/token with grant_type=authorization_code within two minutes, together with the code_verifier (PKCE) and the same redirect_uri. A code works once.

An unknown client id, or a redirect_uri that is not registered for the client, shows an error page on the website and never redirects.

response_type: code.
client_id: the app's client id.
redirect_uri: one of the app's registered redirect addresses, exactly as registered.
code_challenge: BASE64URL(SHA-256(code_verifier)). code_challenge_method: S256.
state: optional, returned unchanged; the app checks it is its own.
cl: optional, the language of the login page: se, gb, no or dk.
theme: optional, the colour theme of the login page so it matches the app: light, dark or system (since 5.25). Without it the page follows the member's own theme choice on the website in that browser.

302 Found
POST
/oauth/token Exchanges the code for the member's tokens, renews a login, or gives the app a token of its own (OAuth 2.1).
Information Body Response

Called without a Bearer token. A client with a key sends its id and key in a Basic Authorization header (client_id:key in base64), which is what an OAuth client library does by itself, or as the form fields client_id and client_secret. A public client (no key) sends client_id alone.

grant_type=authorization_code logs the member in with the code from GET /oauth/authorize: the reply has access_token, token_type (Bearer), expires_in (3600), scope (the client's rights) and refresh_token. The code works once, within two minutes, for the client and redirect_uri it was made for, and only with the code_verifier its challenge was made from.

grant_type=refresh_token gives a new access token and a new refresh token; the old refresh token is dead at once. Renew when a call answers 401 with error="invalid_token", not before every call. Only the client that made the login can renew it.

grant_type=refresh_token with profile_id switches profile, as the profile menu on the website does: the reply has tokens for that profile (one of GET /me/profiles) on the same device, and the refresh token sent ends with its access tokens. Keep the new tokens in place of the old ones and fetch GET /me again. A profile_id that is not in GET /me/profiles gives 400 invalid_request, and the refresh token sent is still valid then.

grant_type=client_credentials gives an access token for the app alone, good for GET /client and GET /texts only. Not for a public client.

There is no grant_type=password (OAuth 2.1 removed it): it gets 400 unsupported_grant_type. A member's password is typed on myWebLog's login page only.

A code or refresh token that is not valid gives 400 with error invalid_grant and an error_description meant for the app's user, in the language of Accept-Language. The reply follows the OAuth 2.0 standard, not the Problem Details form of the other endpoints.

Form data (application/x-www-form-urlencoded), not JSON:

grant_type: authorization_code, refresh_token or client_credentials.
code, redirect_uri, code_verifier: with authorization_code. device_name is optional: what the member sees on My settings, such as the phone model.
refresh_token: with refresh_token. profile_id is optional: the id of a profile in GET /me/profiles to switch to.
client_id, client_secret: only when they are not sent in the Basic Authorization header. A public client sends client_id alone.

200 OK
POST
/oauth/revoke Logs the member out: the refresh token and the access tokens fetched with it stop working.
Information Body Response

Called with the client's credentials, as /oauth/token. The reply is 200 also for a token that is already gone, so a logout never fails. The login disappears from the member's My settings on the website.

Form data: token = the refresh token.

200 OK

client

GET
/client The app the access token belongs to: its rights and the organizations it is limited to. Also the way to test that a key works.
Information Parameters Response

With GET /texts, the one endpoint that takes the app's own access token (grant_type=client_credentials) as well as a member's.

Returned: id, name (the developer), app_name (what members see on My settings), rights, organizations and rate_limit_per_minute. "rights" has one entry per module: "r" (read), "w" (write) or "rw". The modules are those of the Main API v5: organization, objects, bookings, flightlogs, transactions; and payments, messages, logbook, expiry_dates and roster, which only the Mobile API has (payments by the member: Swish, Nets Easy, bank; the member's messages from the organization; a personal logbook account's own logbook; the member's own expiry dates, new in 5.16; a personal logbook account's roster duties, new in 5.39). A module the app has not been given is not in the list. "organizations" is null when the app may be used for every organization, otherwise a list of organization ids.

None
200 OK

me

GET
/me The user who is logged in: who they are, their roles, their organization and their balance, or their personal logbook.
Information Parameters Response

What version 3 gave as GetUserdata and GetBalance. Any user's token can call this.

Returned: id, username, account ("member" or "logbook", new in 5.14), member_number (text, since it can have leading zeros), name (first, prefix, last, full), user_category, locked, roles, has_photo, organization (id, name, homepage), balance (in the organization's currency), currency (code, symbol) and logbook (new in 5.14).

"locked" true means the member may read but not book or change anything; such a call gives 403 with code 10302.

"roles" lists the member's roles in the organization, as the member card on the website sets them: "admin", "instructor", "student", "board_member" and "maintenance", the same names as in the Main API v5. It is empty when the member has none. Any member can be the scout on a flight, so that is no role.

"has_photo" says whether GET /me/photo has a photo. The photo is not in this reply, so that /me stays small.

For a personal logbook account (see "Two kinds of account") the same object comes with member_number, organization, balance and currency null, roles empty, has_photo false, and "logbook": valid_until (the date the account is paid to), is_expired (true when that has passed: the /logbook endpoints then give 403 with code 10326), time_format ("hhmm" when the pilot shows flight time as hours and minutes, "decimal" for decimal hours: the "text" of every flight time follows it) and flight_count (the flights GET /logbook/flightlogs lists). For a member "logbook" is null.

New in 5.40: "logbook" also has clock_times, how the pilot logs clock times ("utc", or "local" for local time at each airport, a setting on the website), and home_time_zone, with "local" the pilot's home zone (an IANA name such as Europe/Stockholm, used where an airport has no zone and for a simulator session), null with "utc". The flights are given in UTC either way (GET /logbook/flightlogs); an app sends clock_times "local" in POST and PATCH /logbook/flightlogs only when this says "local".

None
200 OK
GET
/me/photo The member's photo as a JPEG.
Information Parameters Response

Any member's token can call this. 200 by 240 pixels, the photo the website shows on the member card. The reply body is the picture itself (Content-Type: image/jpeg), not JSON. The reply may be kept for a day (Cache-Control: private, max-age=86400) and carries an ETag. 404 with code 10306 when the member has no photo; "has_photo" in GET /me says so beforehand. A personal logbook account has no member card, so it always gets the 404.

None
200 OK
GET
/me/profiles The user's other profiles, which the app can switch to.
Information Parameters Response

Any user's token can call this. The user's logins in other organizations, as the profile menu on the website offers them: the profiles connected on Manage profiles, and for NLF connected organizations the same NLF person. Left out: a profile that is hidden or login-locked, and one in an organization that is not active or that the app may not be used for. The current profile is not in the list. Sorted by the organization's name; empty when there are none.

Since 5.14 a connected personal logbook account is in the list too (last, "account": "logbook", organization null), when the app has the logbook module and the account is one the feature is open to; and a personal logbook account sees its connected member logins. Before 5.14 a personal logbook was always left out.

Returned: id, name (the user's full name in that profile), account ("member" or "logbook"), organization (id, name; null for a personal logbook account) and, since 5.21, unread_messages: the unread messages in the profile's inbox, counted as "unread" in the meta of GET /messages (0 for a personal logbook account).

The badges (since 5.21): show unread_messages on each profile in the app's profile menu; the messages icon shows the current profile's meta.unread from GET /messages; the app's icon shows the total, meta.unread plus every unread_messages here. The push notifications carry the same total in "badge" (see "Push notifications" above).

To switch, send the refresh token with profile_id to POST /oauth/token (grant_type=refresh_token): the reply has tokens for the chosen profile, and the current login ends.

None
200 OK
PUT
/me/devices/{token} Registers the phone for push notifications (see "Push notifications" above).
Information Body Response

New in version 5.20. Any user's token can call this, also a locked member's and a personal logbook account's (which gets no pushes today).

{token} is the push token APNs or FCM gave the phone: 1 to 255 letters, digits, ":", "_" and "-". A ":" may be sent as it is or as %3A. Anything else gives 404.

Call it on every launch and after every profile switch. A token already registered, also under another login, moves to this login, so only the phone's current login gets pushes. The registration ends with the login (POST /oauth/revoke, "Log out" on My settings, a password change, 90 days without use) and moves with a profile switch.

400 with code 10006 and the field: environment missing for ios, or sent for android; a platform, environment or language that is not one of those below; an app_version longer than 30 characters; a live_activity_start_token sent for android, or not in hexadecimal.

platform (required): "ios" or "android".

environment: "sandbox" (a build from Xcode) or "production" (TestFlight and the App Store). Required for ios, left out or null for android. A wrong one makes APNs refuse the token, and the registration is removed.

app_version: at most 30 characters, e.g. "1.0 (3)".

language (required): "se", "gb", "no" or "dk", the language of the pushes' texts.

live_activity_start_token (new in 5.31): the phone's push-to-start token from ActivityKit (iOS 17.2 and later), in hexadecimal, at most 255 characters. Send it again when iOS changes it. Left out or null: the phone has none, and a token sent before is removed. Only for ios.

204 No Content
DELETE
/me/devices/{token} The phone gets no more push notifications.
Information Body Response

New in version 5.20. Call it on logout, before POST /oauth/revoke, while the access token is still valid. Also 204 when the token is not registered, so that a logout never fails.

None
204 No Content
GET
/me/notification-settings Which push notifications the member gets.
Information Parameters Response

New in version 5.20. Any user's token can call this.

Returned: message, booking_cancelled and booking_changed, each true (on) or false (off). Everything is on until the member turns something off. The settings belong to the person: the same in every profile of theirs, for all their phones. The silent badge update cannot be turned off.

None
200 OK
PATCH
/me/notification-settings Turns kinds of push notification on or off.
Information Body Response

New in version 5.20. Any user's token can call this, also a locked member's. A kind that is not sent keeps its value. The change is made in every profile of the member's (GET /me/profiles), so they see the same settings whichever profile they are in.

200 with the settings afterwards, as GET gives them. 400 with code 10105 for an empty body, with code 10007 for a kind that does not exist, with code 10006 for a value that is not true or false.

message, booking_cancelled, booking_changed: true or false, at least one of them.

200 OK
GET
/me/expiry-dates The member's expiry dates, such as a medical or a licence, as My settings shows them.
Information Parameters Response

New in version 5.16. Right: expiry_dates:r. A member's token only (a personal logbook account gets 403 with code 10324). A locked member may call it.

Every expiry date type of the organization with the member's own date of it, in the order of the names, as My settings on the website shows them. Returned per type: id (the type's id, the same as in the Main API v5), name, expiry_date (null when the member has none; 2999-12-31 means valid without date), expired, may_never_expire (whether the type accepts 2999-12-31), reminder_days_before, image_required, has_image, submission, members_can_change and members_can_upload.

"expired" is true when the date is before today, and also when the type requires a copy of the document ("image_required") and the member's date has none ("has_image" false), as My settings and the booking rules count it. It is null when the member has no date. A copy the member has sent in that waits for an administrator does not make the date valid. The website reminds the member "reminder_days_before" days before the date, which is a good time for the app to warn too.

"submission" is the newest copy of the document the member has sent in, while it waits for approval ("status": "pending") or after it was rejected ("rejected", with "rejected_at" and the administrator's "reason"), with the date the member gave ("expiry_date") and "submitted_at". It is null when there is none, or when the newest was approved (the date and the copy are then the member's) or withdrawn.

"members_can_change" says whether the member may change the date themselves; "members_can_upload" whether they send in a copy with the date on it instead, for an administrator to approve (the date then changes when the copy is approved, and members_can_change is false). Since 5.17 the member does either through the API (the four endpoints below, right expiry_dates:w); the copy itself cannot be fetched.

New in 5.41: a type that does not apply to the member is left out, also when the member has a date of it, as on My settings. An organization can limit a type to some of its members, by user group and membership. The total counts the types that apply, and the four endpoints below answer 404 for a type that does not, as for a type the organization does not have.

limit, offset, include_total, exclude
200 OK
PUT
/me/expiry-dates/{type_id} The member sets their date of a type, as on My settings.
Information Body Response

New in version 5.17. Right: expiry_dates:w. Not for a locked member (403 with code 10302).

Creates or changes the member's date of the type, as saving My settings does. Only for a type with "members_can_change": otherwise 403 with code 10327, either because the organization's administrators set the date, or because members send in a copy of the document with the date instead (POST .../submission below).

A changed date gets its reminder mails again, and its copy of the document is removed, since it proved the old date. The same date again saves nothing. A date that has passed is accepted, as on My settings. Each change is written to the organization's log, with the member as the one who made it.

200 with the member's date of the type (the fields of GET /me/expiry-dates); 404 when the organization has no such type.

expiry_date (date, required): 2999-12-31 means valid without date, accepted only when the type has "may_never_expire". null is not accepted: to remove the date, use DELETE.

Query: exclude, as in GET /me/expiry-dates.

200 OK
DELETE
/me/expiry-dates/{type_id} The member removes their date of a type.
Information Body Response

New in version 5.17. Right: expiry_dates:w. Removes the date and its copy of the document, as emptying the date on My settings does. The same rule as PUT: only for a type with "members_can_change" (403 with code 10327). 404 when the member has no date of the type. Written to the organization's log.

None
204 No Content
POST
/me/expiry-dates/{type_id}/submission The member sends in a copy of the document (a photo or a scan) with the date on it, for an administrator to approve.
Information Body Response

New in version 5.17. Right: expiry_dates:w. As on the website's page for sending in a copy, reached from My settings. Only for a type with "members_can_upload" (403 with code 10328).

The copy waits for an administrator, who approves or rejects it on the website. Until it is approved, the member's current date and copy stay as they are, and a date that has run out still counts as expired. A copy that already waits is replaced. The reply is the member's date of the type with "submission" (status "pending"); GET /me/expiry-dates shows later whether it was approved (the date and has_image change, submission becomes null) or rejected (status "rejected" with the reason). Written to the organization's log.

The file must be a JPG, PNG or PDF, by its name (.jpg, .jpeg, .png, .pdf) and by its content, and at most 5 MB. Otherwise 400 with a field error on "file": code 10329 for a file that is too big, 10330 for another kind of file. The date must not have passed.

The only body in this API that is not JSON: multipart/form-data, as phones' upload libraries send a file, with two parts:

file (the copy, with its file name) and expiry_date (the date shown on the document, YYYY-MM-DD; 2999-12-31 only when the type has "may_never_expire").

A body of another kind gives 400 with code 10004; a part with another name gives 10007 on that part.

Query: exclude, as in GET /me/expiry-dates.

200 OK
DELETE
/me/expiry-dates/{type_id}/submission The member takes back the copy that waits for approval.
Information Body Response

New in version 5.17. Right: expiry_dates:w. As on the website, also allowed when the organization has since stopped members sending in copies of the type. 404 when no copy of the type waits (also when an administrator decided on it a moment ago). Written to the organization's log.

None
204 No Content

organization

GET
/organization The member's organization: what an app needs to show times, money and bookings right.
Information Parameters Response

Right: organization:r. What version 3 sent as orgData with every reply; fetch it once per session.

Returned: id, name, homepage, has_logo, location (reference_icao, latitude, longitude, country, country_code, timezone, utc_offset), date_format (as the website shows dates, in PHP's date() form), locale, currency (code, symbol) and booking (enabled, cancel_reason_required, standard_length_hours, use_expected_airborne).

New in 5.43: location.country_code, the country as its ISO 3166-1 two-letter code ("SE"). country is still the name in capitals ("SWEDEN"); compare with the code.

New in 5.42: logbook, how the organization logs the clock times of its flights, so that the app can mark its time fields "LCL" or "UTC" as the website does: clock_times ("local" = local time at each airport, or "utc"), home_time_zone (with "local", the zone used for a place without a time zone of its own; null with "utc") and answered (false while no administrator has confirmed the rule on the website; clock_times is what applies until then). logbook is left out for an organization that does not have the logbook's clock yet: until the website opens it to every organization, only its test organizations have it.

"booking.enabled" is false when the organization has switched booking off; the booking endpoints then give 403 with code 10301, while everything else works. "utc_offset" is the offset right now; use "timezone" to work with other dates.

"has_logo" says whether GET /organization/logo has a logo. The logo is not in this reply.

None
200 OK
GET
/organization/logo The organization's logo as a GIF or PNG.
Information Parameters Response

Right: organization:r. The logo the organization uploaded on the website, as it was uploaded: a GIF or a PNG of at most 50 kB, not resized (the website shows it in a frame of about 173 by 60 pixels). The reply body is the picture itself, not JSON; Content-Type (image/gif or image/png) says which. The reply may be kept for a day (Cache-Control: private, max-age=86400) and carries an ETag. 404 with code 10307 when the organization has no logo; "has_logo" in GET /organization says so beforehand.

None
200 OK
GET
/organization/settings The settings the organization has marked "show in the app" on the website.
Information Parameters Response

Right: organization:r. What version 3 gave as GetOrgSettings. A list, each setting with "id" (the setting type), "value", "value_type" and the website's own fields for it, such as its description. The ids are the website's setting types, for example 1000 (hide the balance in the app's lobby) and 1001 (hide the transactions).

None
200 OK
GET
/sun-times Dawn, sunrise, sunset and dusk at the organization's reference airport, one item per date.
Information Parameters Response

Right: organization:r. Returned: airport (icao, latitude, longitude), timezone and days, one per date with date, utc_offset, dawn, sunrise, sunset and dusk. Each time is given in UTC ("at") and in the organization's time zone with its offset ("local"). Dawn and dusk are civil twilight. A time is null where the sun does not rise or set that day. "days" is empty when the organization has no coordinates.

date_from, date_to: the dates, inclusive. Today for a month when left out; at most 62 days.
200 OK

texts

GET
/texts The texts of myWebLog's own apps in one language, so that a changed text reaches the apps without a new release.
Information Parameters Response

New in version 5.11. Any member's token, or the app's own (as for GET /client); a public client calls it after the login. Returned under "data": a flat object of key and text, the same for every organization, with the same keys, placeholders and HTML as the text files the apps bundle. A key missing from the reply has no text on our side any more; keep showing the bundled one.

The reply has an ETag, which changes when a text in that language changes. Keep it with the texts and send it as If-None-Match on the next call (on every launch, for example): when nothing has changed the reply is 304 with no body. An ETag belongs to one language; send it only with the lang it came with.

lang (required): se, gb, no or dk.
If-None-Match (header): the ETag of the texts you have.
200 OK
304 Not Modified

objects

GET
/objects What the member can book: aircraft, equipment and premises, the organization's own and the ones shared with it.
Information Parameters Blocks (include) Response

Right: objects:r. The objects as the booking calendar on the website shows them to this member, in the same order. What version 3 gave as GetObjects.

Always returned: id, registration, category (id and name: 0 Aircraft, 1 Equipment, 2 Premises, 3 Simulator), model (designator and name: an aircraft's type, or the type a simulator simulates; both null when no type is set, which the website stores as "x"), simulator_class, comment, organization (id and name of the owner) and has_thumbnail.

New in 5.30: simulators, category 3, as an organization sets them up on the website. simulator_class is the simulator's class (BITD, FNPT I, FNPT II, FNPT III, FTD, FFS or Other), null when not set and for every other object. Give a simulator its own icon in the app.

status: the object's status ids (0 OK, 1 yellow, 2 red) for the whole (total_id), for maintenance and for remarks, and remaining_time until maintenance is due ("soft") and until the object is grounded ("hard"), for each counter: airborne, days, tachometer (the meter), tach (tacho time), hobbsmeter (with formatted texts), landings and (new in 5.29) cycles (the engine cycles of an aircraft that logs them), null without a limit and negative when passed. active_remarks: the open remarks on the object, each with id (GET /remarks/{id} gives the whole remark), created_date, created_by, description and category_id. time_summary: the object's total airborne, block and tach time (as numbers and formatted), landings and (new in 5.29) engine_cycles, the engine's total cycles for an aircraft that logs them, otherwise null. disclaimer: a text the organization wants shown before the object is booked, { headline, text }, or null. settings: use_expected_airborne, force_expected_time and max_booking_length (minutes, or null).

status, active_remarks and time_summary are worked out the same way as on the website and take the longest to fetch, so ask only for the blocks you need.

limit, offset, include_total, exclude status
active_remarks
time_summary
disclaimer
settings
200 OK
GET
/objects/{id} One object.
Information Parameters Response

Right: objects:r. The same fields and blocks as in the list. 404 when the object is not one the member may see.

include, exclude
200 OK
GET
/objects/{id}/thumbnail The object's picture as a JPEG.
Information Parameters Response

Right: objects:r. 150 by 100 pixels, the reply body being the picture itself (Content-Type: image/jpeg), not JSON. The reply may be kept for a day (Cache-Control: private, max-age=86400) and carries an ETag. 404 with code 10304 when the object has no picture; "has_thumbnail" in the object says so beforehand.

None
200 OK

remarks

New in version 5.18. A remark is a fault or a note a member writes on an object, as on the website's Technical status page, where every member may write one. A remark written together with a flight is part of POST /flightlogs. Writing goes through the website's own remark class as the member, so what follows is the website's: the mail and SMS to the organization's recipients for remarks, the outgoing webhook remark.create, and the organization's automatic acknowledgement. Since 5.19 a remark can also be acknowledged, commented and closed, as on the website: a mechanic or an administrator does that (the "maintenance" and "admin" roles in GET /me), and the member who wrote the remark may also comment.

An organization can switch the remark function off (the same setting hides the remark on Log flight). GET /remark-options and POST /remarks then give 403 with code 10331, and the app should not offer remarks; the remarks that exist can still be read.

GET
/remark-options The categories a new remark can have, and the organization's disclaimer.
Information Parameters Response

Right: objects:r. Returned: categories, each with id, name (in the language of Accept-Language) and blocks_flying (true for a category that stops the object from flying, the red one), and disclaimer: the text the website shows above the form when the organization has switched it on, as plain text, or null. Show it the same way.

As on the website's page, every category may be chosen, also one that stops flying. (The organization's setting against red remarks applies to the remark of a logged flight only, see GET /flightlog-form.)

With object_id: 404 unless the member may write a remark on that object, so the app can check before it shows the form.

object_id (int, optional)
200 OK
POST
/remarks The member writes a remark on an object.
Information Body Response

Right: objects:w. Not for a locked member (403 with code 10302).

The object must be one the website's page lists for the member: not hidden from maintenance, and not denied to the member. Otherwise 404. The category must be one of GET /remark-options.

201 with the remark, as GET /remarks/{id} gives it, and its address in Location. When the organization acknowledges remarks automatically, "items" already has the acknowledgement and "status" is "acknowledged".

object_id (int, required)
category_id (int, required)
text (text, required): what the member writes.

201 Created
GET
/remarks/{id} One remark, with everything that has happened to it.
Information Parameters Response

Right: objects:r. A remark on an object the member sees in GET /objects; its id is in the active_remarks block there. 404 for any other remark.

The same form as the Main API's GET /remarks/{id}: id, object (id, registration, organization), category (id, name: yellow or red, blocks_flying), ata (chapter and section, or null), flight_id (the flight it was written with, or null), status (open, acknowledged, closed or rejected), created_at (UTC), created_by, description, and items: everything that has happened, oldest first, each with type (created, acknowledged, commented, closed, rejected), at (UTC), by (null for an automatic acknowledgement) and text.

New in version 5.37: images, the remark's own images (up to two, showing the fault), each with id, width and height; and on each item its id and image, the picture a comment or the closing can have (what was found or done; id, width and height, or null). The bytes of an image are GET /remarks/{id}/images/{image_id}.

exclude
200 OK
POST
/remarks/{id}/acknowledge A mechanic or an administrator acknowledges a remark.
Information Body Response

New in version 5.19. Right: objects:w. Not for a locked member (403 with code 10302). A remark on an object the member sees, as for GET /remarks/{id}; 404 otherwise.

As on the website: only a mechanic or an administrator may (403 with code 10332), and only an open remark that is not yet acknowledged (409 with code 10333). The webhook remark.update follows. 200 with the remark as it is afterwards.

None
200 OK
POST
/remarks/{id}/comment A comment on a remark.
Information Body Response

New in version 5.19. Right: objects:w. As on the website: a mechanic, an administrator or the member who wrote the remark may (403 with code 10332), once the remark is acknowledged and until it is closed (409 with code 10333). The webhook remark.update follows. 200 with the remark as it is afterwards.

text (text, required)
200 OK
POST
/remarks/{id}/close A mechanic or an administrator closes a remark.
Information Body Response

New in version 5.19. Right: objects:w. As on the website: only a mechanic or an administrator may (403 with code 10332), once the remark is acknowledged and only once (409 with code 10333). The organization's recipients for remarks get the website's mail, and the webhook remark.update follows. 200 with the remark as it is afterwards.

A remark can be handled also when the organization has switched the remark function off; only new remarks are stopped then.

text (text, optional): a closing text. The body may be left out.
200 OK
POST
/remarks/{id}/images Add an image to a remark, or to one of its comments.
Information Body Response

New in version 5.37. Right: objects:w. One more image on the remark, as the website's Technical status page keeps them: the body is multipart/form-data with the part file (a JPEG, PNG, GIF or WebP of at most 20 MB and 25 million pixels), which the server scales to 1600 pixels on the long side and keeps as a JPEG.

Without item_id the image is one of the remark's own, up to two, showing the fault: the member who wrote the remark, a mechanic or an administrator may add it (403 with code 10337), until the remark is closed (409 with code 10338). With item_id, the id of a comment or of the closing in the remark's items, the image is that item's, one each, showing what was found or done: the one who wrote the item, a mechanic or an administrator may add it (403 with code 10337). A comment's image can be added only until the remark is closed; the closing text's image for 24 hours after the closing. Otherwise 409 with code 10338.

Returned: 201 with the remark as it is afterwards (the new image in images, or in image of the item), a Location header with the image's address and "meta.image_id". 409 with code 10339 when the remark has two images or the item has one, 409 with code 10340 for the same picture again on the remark, 400 with code 10341 for a file that is no image. The webhook remark.update with change "images" follows.

multipart/form-data: the part file (required); the field item_id (int, optional): the comment or the closing the image is for
201 Created
GET
/remarks/{id}/images/{image_id} An image of a remark.
Information Parameters Response

New in version 5.37. Right: objects:r. The image, a JPEG (the large copy, at most 1600 pixels on the long side), with an ETag: one of the remark's own images or the image of one of its items, by the id the remark gives. 404 for a remark you do not see or an image that is not on this remark.

None
200 OK
DELETE
/remarks/{id}/images/{image_id} Remove an image of a remark.
Information Body Response

New in version 5.37. Right: objects:w. Removes the image from the remark; the website keeps it, marked deleted, as part of the aircraft's technical record, so it no longer appears in the remark and GET of it answers 404. Who may is the same as for adding it: 403 with code 10337, and 409 with code 10338 once the remark is closed, except for the closing text's image within 24 hours after the closing. The webhook remark.update with change "images" follows.

204, also when the image is gone already or is not on this remark.

None
204 No Content

bookings

GET
/bookings The bookings the booking calendar on the website shows this member.
Information Filters Response

Right: bookings:r. In the website's order, with the bookings in the queue last. What version 3 gave as GetBookings.

Returned: id, start_at, end_at (UTC), start_local, end_local (the organization's time zone with its offset), timezone, object (id, registration, category, organization), user and student (id, name, member_number, email, mobile; student is null when the booking has none), calendar_name, type, booking_type (new in 5.24, see below), is_primary, is_queue, is_own, is_student, is_active_now, is_passed, details_hidden, permissions (can_edit, can_cancel, can_cut, queue_allowed), expected_airborne, seats_left, comment, reminders (email, sms), created_at and created_by.

"booking_type" (new in 5.24) is the organization's booking type the booking is shown with: id, name, description, is_standard, color, color_light and color_dark. An organization names its own booking types on the website ("Fire watch", "Glider tow"), each built on one of the types in "type", which keeps its rules; every organization starts with one standard type of each. A standard type the organization has not renamed gets the website's name and description in the language of Accept-Language. "color" is the palette colour the organization chose (teal, sky, indigo, lavender, pink, coral, amber, lime, olive, brown, slate, cyan, blue, green, red, orange or purple), with its hex value for a light and for a dark background in color_light and color_dark, dark enough for white text; null when the type has the standard colours of its type, which a client then draws as before. The colour is the same for the booker and for other members: mark the member's own bookings as today. The booking's own type, or the organization's standard type of its "type" when it has none.

"reminders" are the booking page's two boxes: a reminder by email and by SMS the day before. They are the member's own business, so they are given on the bookings the member may change ("permissions.can_edit") and are null on the others.

The email and mobile number of the booker and the student follow each member's own settings on the website: null when hidden. "is_own" is true when the member is the booker or the student, "is_student" when the member is the student. "details_hidden" is true when the organization hides who has booked from other members; the names and contact details of such a booking are null, as in the booking calendar. "calendar_name" is the booker's name as the website's booking calendar writes it on the booking ("M.Winsth"): null when the organization has not chosen to show names in the booking calendar, and when the details are hidden. An app that draws a calendar shows it on the booking, and so follows the organization's choice without reading any setting."permissions" says what the member may do with the booking by the website's rules: change it, cancel it, cut it (end it now), and whether a queue booking on the object is allowed. "type" is the booking type as the website names it, such as PRIV or SKOL. Version 3 gave the times as Unix timestamps.

403 with code 10301 when the organization has switched booking off.

object_id (int): only bookings of this object
mine (bool): true gives only the member's own bookings, as booker or as student
date_from (date): bookings that end on or after this date; today when left out
date_to (date): bookings that start on or before this date

limit, offset, include_total, exclude
200 OK
GET
/bookings/{id} One booking, also one in the queue.
Information Parameters Response

Right: bookings:r. The same fields as in the list. 404 when it is not one the member may see.

exclude
200 OK
GET
/booking-options What the member may choose when booking: for whom, which types, which students and instructors.
Information Parameters Response

Right: bookings:r. The choices the booking page offers this member, by the website's booking rules. Use them to fill the choices for POST /bookings.

Returned: may_book_for_others (true for administrators and on-call bookers), owners (who the member may book for: only themselves unless may_book_for_others), types (each with type, name, needs: the body field the type needs, and booking_types), students (who can be the student of a SCHOOL booking, and "not in the list" as id -1 with "special": "not_listed"), instructors (who can be the instructor of a SCHOOL_L booking) and reminders. A member is { "id", "name", "member_number" }; the lists are by last name.

"reminders" is how to draw the two reminder boxes: "email" and "sms" are ticked as the booking page ticks them for a booking of the member's own (the member's settings in My settings), "sms_available" says whether the organization offers SMS reminders (show the SMS box greyed out when it does not), and "sms_price" is what the member pays per SMS, { "amount": 1.5, "currency": "SEK" }, or null when the organization pays.

The types are PRIV, SCHOOL and SCHOOL_L, those the member may use outside an instructor duty, named as on the booking page in the language of Accept-Language. Inside an instructor duty other types apply, and an object can lock a type; POST /bookings then answers 409 with the rule's text. 403 with code 10301 when the organization has switched booking off.

Each type lists in "booking_types" (new in 5.24) the organization's booking types built on it that the member may use, in the organization's order, each as a booking's "booking_type" in GET /bookings (id, name, description, is_standard, color, color_light, color_dark); SCHOOL and SCHOOL_L list the same ones. Offer them in the booking form and send the chosen one as booking_type_id in POST /bookings. They are the member's organization's: a booking on an object another organization shares gets that organization's standard type, so leave booking_type_id out for such an object. Each one also has "is_default" (since 5.26): true for the organization's default type for new bookings, which the booking page on the website selects from the start; select it in the booking form when it is in the list. At most one type is the default, and it is only listed when the member may use it. A type of which the organization has archived every booking type (for example an organization that does not use instructor duty) is left out of "types", and POST /bookings refuses it with 409.

None

Header Accept-Language: sv, en, nb or da (English when left out)
200 OK
GET
/non-bookable-times The times the objects cannot be booked, for the hatched "Not bookable" bands of a booking calendar.
Information Parameters Response

New in version 5.45. Right: bookings:r. An organization can keep an object free of members' bookings at certain times, e.g. Saturdays and Sundays 10:00-16:00. The website's booking calendar draws such a time as a hatched band marked "Not bookable" (Swedish "Ej bokningsbar", Norwegian "Ikke bookbar", Danish "Kan ikke bookes"), behind the bookings; this endpoint gives an app the same bands.

Returned: timezone (the organization's) and times, one item per time and day it occurs, in time order, for the objects of GET /objects (also the ones another organization shares). Each item has rule_id (the organization's non-bookable time it comes from, the same on every day it occurs), object_id, start_at and end_at (UTC), start_local and end_local (the organization's time zone with its offset, as on a booking), reason (the organization's own note, or null), text and can_book. A time that passes midnight is one item. A time that began the day before date_from, or ends the day after date_to, is given whole. Two times of the same object can overlap.

"text" is the sentence the website shows on the band, in the language of Accept-Language, e.g. "SE-ABC cannot be booked Sat, Sun 10:00-16:00 (Flights on the airfield).": show it when the member taps the band. The weekdays and clock times in it are the owning organization's local time.

"can_book" is false for a member: POST and PATCH /bookings refuse a booking that touches the time with 409, code 10300 and the same sentence, so do not open the booking form from the band. It is true for an administrator of the organization, whose booking is made with a warning in "messages"; text then has a second line (after a line break) that says so. A booking that only meets a time (ends when it starts, or starts when it ends) is not refused.

403 with code 10301 when the organization has switched booking off.

object_id: only this object's times (an object that is not one of the member's gives an empty list).
date_from, date_to: the dates, inclusive, in the organization's time zone. Today for a month when left out; at most 62 days.

Header Accept-Language: sv, en, nb or da (English when left out)
200 OK
POST
/bookings A booking: private, a school booking, or for another member, by the website's booking rules.
Information Body Response

Right: bookings:w. Made through the website's booking class: the same rules as the booking calendar (who may book what, overlaps, the queue, lengths, balance) and the same messages. What version 3 did as CreateBooking. A private booking for the member when type and owner_id are left out. GET /booking-options says beforehand what the member may choose; the booking class checks it again, and a choice it does not allow gives 409 with the rule's text. Service bookings and instructor duties are made on the website.

The reply is 201 with the booking as GET gives it under "data", a Location header with its address, and "messages": what the website would show the member after the booking, each as { "kind": "info", "text": "..." }, in the language of the Accept-Language header (sv, en, nb or da; English when left out).

When a booking rule stops it, the reply is 409 with code 10300 and the rule's text for the member in "errors" (see the examples). A locked member gets 403 with code 10302; an organization with booking switched off 403 with code 10301.

object_id (int), start_at, end_at: required. The times are points in time with their offset or Z, as the API gives them; the booking is made in the organization's time zone.

comment (text), expected_airborne (hours as a number, where the organization uses it) and seats_left (int, free seats offered to others): optional.

type (text): PRIV (the default), SCHOOL (the member is the instructor; student_id is required) or SCHOOL_L (the member is the student; instructor_id is required). student_id: a member's id, or -1 for a student who is not in the list (write the name in the comment). owner_id (int): the member the booking is for; only administrators and on-call bookers may give another member. Take the ids from GET /booking-options.

booking_type_id (int, new in 5.24): one of the booking_types GET /booking-options lists under the chosen type. Left out, the booking gets the organization's standard type of its type. One that is not built on the type, is not offered to the member or belongs to another organization gives 409 with the rule's text; 0 or null gives 400.

reminders: optional, { "email": true, "sms": false }. A box that is left out is ticked as the owner has it in My settings, as the booking page does (SMS only when the organization offers SMS reminders). "sms": true when the organization does not offer them gives 400. When the owner has SMS reminders off in My settings, the box is stored but no SMS is sent until they switch them on; "messages" then says so.

201 Created
PATCH
/bookings/{id} Changes the times, the object, the comment or the reminders of a booking.
Information Body Response

Right: bookings:w. New in version 5. Changed through the website's booking class: the same rules as when the booking is changed on the booking page, and the members get the website's "booking changed" mail. A field that is not sent keeps its value. The type and the people of a booking cannot be changed (cancel it and book again), but its booking type can (booking_type_id, new in 5.24).

The booking's "permissions.can_edit" says beforehand whether the member may: the booker, the student, an administrator or an on-call booker, and after its end only an administrator. Otherwise 403 with code 10309. Only private and school bookings can be changed here: 409 with code 10320 for a service booking or an instructor duty.

A change that puts the booking last in a queue behind another booking gives 409 with code 10303, with the bookings ahead in "errors". Send the same change again with "queue_confirmed": true to go ahead, as the booking page asks the member to confirm. The booking then moves to a new row, last in the queue, and gets a new id: use "data.id" of the reply, as the old id is gone.

200 with the booking as it is afterwards and "messages"; 409 with code 10300 when a rule stops it; 404 when the booking is not one the member may see; 400 with code 10105 for an empty body.

object_id (int), start_at, end_at: as in POST /bookings.

comment (text), expected_airborne (hours), seats_left (int): null empties them.

reminders: { "email": true, "sms": true }; a box that is left out keeps its value. "sms" follows the same rules as in POST /bookings.

booking_type_id (int, new in 5.24): one of the booking_types GET /booking-options lists under the booking's type; left out, the booking keeps its own.

queue_confirmed (bool): the member agrees to be placed last in the queue.

200 OK
POST
/bookings/{id}/cut Ends a booking that is going on, now.
Information Body Response

Right: bookings:w. What version 3 did as CutBooking. The booking's "permissions.can_cut" says beforehand whether the member may. 200 with the booking as it is afterwards and "messages"; 409 with code 10300 when a rule stops it (for one, a booking that has not started); 404 when the booking is not one the member may see; 403 with code 10308 for a booking that is going on but is not the member's (only the booker, the student, an administrator or an on-call booker may end it).

None
200 OK
POST
/bookings/{id}/cancel Cancels the booking, which also sends the website's cancellation mails.
Information Body Response

Right: bookings:w. What version 3 did as DeleteBooking. "permissions.can_cancel" says beforehand whether the member may. 200 with the booking as it was, since it is gone afterwards, and "messages"; 409 with code 10300 when a rule stops it, also when a required reason is missing; 404 when the booking is not one the member may see.

reason (text): optional, { "reason": "Weather" }. Required when "booking.cancel_reason_required" on /organization is true.

200 OK
PUT
/bookings/{id}/live-activity Follows the booking in a Live Activity on the iPhone's lock screen (see "Live Activity" under "Push notifications" above).
Information Body Response

New in version 5.20. Right: bookings:r. Call it when the app has started the activity, and again when iOS gives the activity a new token; the latest one counts.

Only for a booking where the member is the booker or the student (403 with code 10334), and not after it has ended (409 with code 10336). The iPhone must be registered first with PUT /me/devices/{token} on this login (409 with code 10335): the pushes go through its environment, and the activity goes when the phone's registration does. 403 with code 10301 when the organization has switched booking off; 404 when the booking is not one the member may see.

400 with code 10006: push_token missing, or not 1 to 255 hexadecimal characters.

push_token (required): the activity's own APNs token from ActivityKit (pushTokenUpdates) in hexadecimal. Not the phone's token.

204 No Content
DELETE
/bookings/{id}/live-activity The Live Activity gets nothing more from the server.
Information Body Response

New in version 5.20. Right: bookings:r. Call it when the app has ended the activity itself. Also 204 when no activity is registered, and for a booking that no longer exists, so that it never fails.

None
204 No Content

flightlogs

GET
/flightlogs The flights logged on the organization's objects and on the objects shared with it.
Information Filters Response

Right: flightlogs:r. Oldest first. What version 3 gave as GetFlightLog and, with order=desc, GetFlightLogReversed. The fields and their names are those of the Main API v5's flight log: id, date, object (id, registration, organization), flight_type (id, name, or null), departure and arrival (airport, blockoff_at, takeoff_at, landing_at, blockon_at, tachometer, hobbs), via_route, crew_hidden, pilot, instructor, scout (id, name, member_number, organization, or null), is_solo_instruction, uplift (fuel, oil), fuel_onboard, totals (block, airborne, tach, hobbs, as hours and as minutes), number_of_flights, engine_cycles, daily_check, comment, remark_id and created_at (UTC).

New in version 5.12: the readings (tachometer, hobbs), uplift, fuel_onboard, the Hobbs total, daily_check, remark_id and created_at, so every value POST /flightlogs takes can be read back. The Main API's transaction_id is not given: the transaction is the paying member's (the reply of POST /flightlogs has it in "meta"). New in 5.29: engine_cycles, the engine cycles of the flight for an aircraft that logs them (null when not logged); the form of POST /flightlogs says whether the aircraft logs them and whether they must be stated.

New in 5.30: object.category (id and name, as in GET /objects) and is_simulator, true for a session on a simulator. A session has its start, end and session time in departure.blockoff_at, arrival.blockon_at and totals.block, and no airports, take-off, landing, meter readings or uplift. The filter simulator=true gives only the sessions, simulator=false only the other flights. remark_id is the flight's first remark; since 5.30 a flight with several remarks is given once (before, once per remark).

Clock times: date, blockoff_at, takeoff_at, landing_at and blockon_at are the logbook's own clock times written with a Z. For most organizations that is local time at each airport, not UTC; the Z is only part of the format, so show them as they are and do not move them to the phone's time zone. A clock time that is earlier than the one before it is on the day after the date. Earlier versions of this page said "The clock times are points in time in UTC": the text was wrong and is corrected in 5.42. The values are as they have always been.

New in 5.42: clock_times, the rule of the logbook the flight is in ("local" = local time at each airport, or "utc"; the logbook is that of the organization that owns the object). In departure and in arrival: time_zone (a logbook in local time: the IANA zone the end's clock times are in, the airport's, else the organization's home zone; a logbook in UTC: the airport's own zone, null when it is not known, as on a personal flight of a pilot on UTC) and utc_offset (that zone's minutes east of UTC at the end's first clock time, 120 for UTC+2; null without a clock time or a zone). The true points in time in UTC are departure.blockoff_utc, departure.takeoff_utc, arrival.landing_utc and arrival.blockon_utc, null where the flight has no such time (also for a stored 00:00 that is not a time: off block and on block both 00:00, or take-off and landing both 00:00). Use them where a real point in time is needed: "landed 20 minutes ago", one time line for several logbooks, a comparison with a booking, and the total of a flight between two time zones.

Example: a flight logged 14:00 at Stockholm Bromma and 16:30 at Mariehamn on 2026-07-01, in a logbook in local time, has blockoff_at "2026-07-01T14:00:00Z" with time_zone "Europe/Stockholm", utc_offset 120 and blockoff_utc "2026-07-01T12:00:00Z", and blockon_at "2026-07-01T16:30:00Z" with time_zone "Europe/Mariehamn", utc_offset 180 and blockon_utc "2026-07-01T13:30:00Z". The block time is 1:30. In a logbook in UTC the same flight has clock_times "utc", the ..._at fields equal to the ..._utc fields, and the same zones and offsets.

The four ..._at fields are deprecated in favour of the ..._utc fields with time_zone. They keep their meaning for all of version 5. Until the website opens the logbook's clock to every organization, only its test organizations have the new fields; the flights of every other organization are given exactly as before. clock_times cannot be named in exclude.

When the organization hides the pilot in its log, "crew_hidden" is true and "pilot", "instructor" and "scout" are null, as on the website; version 3 showed the names anyway. Since 5.23.1 this follows the member's organization also on the shared objects (on a shared object the crew is also hidden when the object's owner hides it), and an object whose share hides its log from the organization is left out, as on the website. Since 5.23.2 the journey log's empty rows (blank lines in an object's log) are not given either, as the website's journey log does not list them; GET /flightlogs/{id} gives 404 for one. "is_solo_instruction" is true for a student's solo flight, false for a flight with an instructor, null when not filled in. A total is null when one of its two readings is missing. Version 3's "distance" is not given.

403 (code 11005, since 5.27) for GET /flightlogs and GET /flightlogs/{id} when the website closes the journey logs to the member: the organization has switched the flight log off, or closed the logbooks to members who may not log for others. Since 5.29.1 the Log flight lock alone no longer closes them: such a member reads the flights but cannot log one (GET /flightlog-options and POST /flightlogs still give 11005). Leave the journey log out of the app for that member, as with Log flight.

object_id (int): only flights on this object
mine (bool): true gives only the member's own flights, as pilot or as instructor
date_from, date_to (date): flights on these dates, inclusive
order: asc (oldest first, the default) or desc (newest first)

limit, offset, include_total, exclude
200 OK
GET
/flightlogs/{id} One logged flight.
Information Parameters Response

Right: flightlogs:r. The same fields as in the list. 404 when the flight is not on an object the member may see.

exclude
200 OK
GET
/flightlog-options For logging a flight: who the member may log for, the objects they may log on, and the flight types the pilot may use.
Information Parameters Response

Right: flightlogs:r. New in version 5: the four endpoints below log a flight through the website's own engine, so the rules, the checks and the price are those of the Log flight page.

Returned: pilot (id, name, member_number), may_log_for_others (true when the member may log for other members, as on the website), pilots (the members the member may log for: themselves, or every member), objects (id, registration, model (null when no type is set, which the website stores as "x"), shared, organization, and flight_types: the types the pilot may use on it, each with id, name and admin_only), instructors and scouts (the members that can be given as instructor_id and scout_id). The two choices that are not members, "no scout" (999999999) and "not in the list" (999999998), have "special" set and no name.

New in 5.23.1 (Main) and 5.42.1 (Mobile): each object has clock_times, "local" or "utc": the clock rule of the organization that owns the object, which is the rule a flight on it is stored in (for a shared object the owner's, not the caller's). null when the owner does not have the clock feature yet. Read it before the flight is logged to mark the time fields "LCL" or "UTC" and to know whether a total is to be calculated across zones; see clock_times in POST /flightlogs.

403 (code 11005) when the organization has switched the flight log off, or locked it for members who may not log for others. 400 (code 11003 at pilot_id) for a pilot the member may not log for.

pilot_id (int): the member the flight is for; the member themselves when left out
200 OK
GET
/flightlog-form Which fields of the POST /flightlogs body are used and required for one object, flight type and pilot.
Information Parameters Response

Right: flightlogs:r.

Returned: object (id, registration, model (null when no type is set, which the website stores as "x")), flight_type (id, name), flight_types (the types the pilot may use on the object), fields, required_one_of, charge_visible and instructions (the organization's own text on the Log flight page).

"fields" has one entry for every field the POST /flightlogs body takes, by its name, always with "used" and "required". A field with used=false is ignored if sent. Where it applies there is also: type ("decimal" with "decimals" 1 or 2, "hh:mm", or "hours" for a typed total), unit, suggested (a value to fill in; with locked=true the value must be the suggested one, e.g. tach out = the object's last tach in), max (number_of_flights: the organization's maximum, null when it has set none), max_items (via), max_length (comment), choices (tow_object_id, tow_height_id; departure_icao, arrival_icao and via, see below), categories and blocking_allowed (remark; the names in the language of Accept-Language), and booking (cut_booking_id: the member's booking of the object that is going on, which must be kept or ended).

New in version 5.22: departure_icao, arrival_icao and via have "choices", the same list on all three, at most 10, each with icao and name (null for a suggested airport that is not in the airport table): the object's suggested airport first, when it has one (it is also "suggested" on departure_icao; the website fills it into both From and To), then the airports the organization has logged most in the last three years. Show them while the field has fewer than 2 characters, and the hits of GET /airports from 2 characters on. The fields stay free text: any ICAO code, or a place in words, at most 50 characters.

"required_one_of" lists the rules where one of several groups of fields must be complete, each with the code POST /flightlogs answers when none is: the block or airborne time as two clock times or a typed total (11030), and towing by time or by height (11044).

"No tow": where the object's tow price list offers it, the choices of tow_object_id end with one that has none = true (registration null), for a glider that launches by itself. Sent as tow_object_id, no tow time or tow height is needed and no towing is charged. The towing rule is then left out of required_one_of.

What the form cannot tell: rules that depend on the values (a reading lower than the last, the lock dates, a flight logged already, the price) are only found by POST /flightlogs/preview. The usual flow in an app is: read the form, let the member fill it in, preview, confirm, save.

404 when the organization does not log flights on the object. 400 with code 11002 for a flight type the organization does not have, and 11003 for a pilot the member may not log for.

object_id (int, required)
flight_type_id (int, required)
pilot_id (int): the member themselves when left out

Header Accept-Language: sv, en, nb or da (English when left out)
200 OK
POST
/flightlogs/preview Checks a flight and gives its price, without saving it.
Information Body Response

Right: flightlogs:w. The same body and the same checks as POST /flightlogs; nothing is saved. Call it when the member has filled in the form, and again after a change, to show the price as the Log flight page does.

Returned: object, flight_type, pilot, charged_member (the member who pays: the pilot, or the member the flight type is charged to), date, totals (block, airborne, tach, hobbs and tow in hours, as the engine worked them out), charge_visible and charge. "charge" is the receipt: currency, charged_member, transaction_date, rows (kind: time, tow, correction, rounding or floor; text, quantity, unit, unit_price, percent, amount), subtotal, rounding, zero_floor, total and vat. It is null when the organization hides the amounts from the member. "meta.warnings" is empty for a member (every rule is an error for a member); it has the rules an administrator may break when the member is an administrator.

Show the member the total and send it as confirmed_total with POST /flightlogs: the flight is then only saved when the price is still the same.

The errors are those of POST /flightlogs: 400 (code 11000) with every problem, 409 (code 11050) for a flight that is logged already, when that is the only problem.

See POST /flightlogs.
200 OK
POST
/flightlogs Logs a flight and charges the member, as the Log flight page does.
Information Body Response

Right: flightlogs:w. The member logs their own flight (pilot_id defaults to the member); a flight for another pilot needs the right to log for others, as on the website. The same rules, checks and price as the Log flight page, the same transaction and the same mail. A member who is an administrator may break some rules (more flights than the maximum, an unreasonable ratio, a flight that looks logged already); they are then reported in "meta.warnings". For every other member they are errors.

Which fields are used and required depends on the object, the flight type and the pilot: ask GET /flightlog-form first. The clock times are written as points in time with Z, on the flight's date (or the day after, for a flight that passes midnight); they are the logbook's own clock times unless clock_times says otherwise (see below). The block and airborne times can be given as two clock times or as a typed total in hours. A meter reading (tach, hobbs) is a number with the object's decimals, or hours and minutes as text ("1234:30") for an object that counts them so. "remark" makes a remark on the object with the flight, "remarks" (new in 5.30) several, at most the form's fields.remark.max_count; "cut_booking_id" ends the member's booking that is going on (0 keeps it); "pfly" is for organizations in Norway. Accept-Language picks the language of the transaction's rows and the mail.

New in 5.30: a simulator (object category 3; is_simulator in GET /flightlog-options and in the form's object) is logged here too, as a session. Its form uses only date, the crew (no solo, no scout), blockoff_at (the session's start), blockon_at (its end) or total_block (the session time, with "label" in the form: show it instead of "Block time"), comment, remark or remarks and cut_booking_id; the airport fields are not used and have no choices. An app that follows "used" in the form needs nothing else to log a session.

Clock times: without clock_times, date and the clock times are the logbook's own clock times, local time at each airport unless the organization logs in UTC (GET /organization, logbook.clock_times). They are stored as sent, which is what the member typed: the hour and the minute count, the Z is only part of the format. Earlier versions of this page said "in UTC": the text is corrected in 5.42, and nothing in how a body is read or stored has changed.

New in 5.42: clock_times says how date and the clock times of the body are to be read. "local": local time at each airport, and date is the local date of the block off; stored as sent in a logbook in local time, converted to UTC in a logbook in UTC (the Z is ignored). "utc": true points in time in UTC, and date is the UTC date; stored as sent in a logbook in UTC, converted to the local time at each airport, on the local date of the block off, in a logbook in local time (the Z is meant). The rule is that of the organization that owns the object. An app that sends what the member typed sends the same value as logbook.clock_times, or leaves clock_times out: both store what the member typed. clock_times is never saved with the flight. Any other value gives 400 (code 10006, "Must be utc or local"). "local" into a logbook in UTC is converted, where the personal logbook refuses it (409, code 11171). A local time that has to be converted and does not exist on that date at its airport (the hour skipped when summer time starts) gives 400 with code 11000 and the error 11090 at the field; a time the clock shows twice is the first of the two. Until the website opens the logbook's clock to every organization, only its test organizations can send clock_times: 400 (code 10006, "Not open to this organization yet") for an object of another 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 (before, it was the difference between the two clock times), and "A flight can not be logged in the future" (11013) compares the landing and the block on as points in time in the logbook's rule, with two hours of slack.

Returned: 201 with the flight as GET /flightlogs/{id} gives it, a Location header, and "meta": transaction_id, balance_after (the member's balance after the charge; null when the amounts are hidden), charge (as the preview gives it), warnings and remark_ids.

New in version 5.38: remark_ids, the id of each remark sent with the flight (remarks, or remark), in the order sent; null for a remark that could not be saved, which also gives the warning 11064; empty when no remark was sent. To add photos to a remark written with the flight, log the flight first, then call POST /remarks/{id}/images once per photo with these ids.

400 with code 11000 when the engine finds problems: "errors" has every problem with its field, its own code (11001-11049) and a message. 409 with code 11050 when a flight with the same object, date and times is logged already, 409 with code 11051 when the price has changed since confirmed_total was shown (the new price in "charge"). A 409 is only given when that is the only problem; with other problems the code is one of the errors of a 400. 403 with code 11005 when the organization has switched the flight log off, 403 with code 10302 for a locked member. 500 with code 11060 when the flight could not be saved; nothing is saved then.

object_id (int, required)
flight_type_id (int, required)
pilot_id (int): the member when left out
instructor_id (int), is_solo_instruction (bool), scout_id (int)
date (YYYY-MM-DD, required)
clock_times ("utc" or "local", new in 5.42)
departure_icao, arrival_icao (text: an ICAO code or a place in words, at most 50), via (list of such texts, at most 5)
number_of_flights (int), distance (number)
blockoff_at, blockon_at (datetime), total_block (hours)
takeoff_at, landing_at (datetime), total_airborne (hours)
tach_out, tach_in, hobbs_out, hobbs_in (reading)
tow_object_id (int), tow_landing_at (datetime), total_tow (hours), tow_height_id (int), tow_height_value (number)
fuel_uplift, oil_uplift, fuel_onboard (number), engine_cycles (int, 0-99, new in 5.29; for an aircraft that logs engine cycles, required when the form says so, never suggested: the pilot states it, usually 1), daily_check (bool)
comment (text, at most 200)
remark {text, category_id, ata_main_code_id, ata_sub_code_id}
remarks [{text, category_id, ata_main_code_id, ata_sub_code_id}, ...] (new in 5.30; used instead of remark when both are sent)
cut_booking_id (int)
pfly {used, blind_transmission, overfly, closed_flight_plan}
confirmed_total (decimal)

Header Accept-Language: sv, en, nb or da
201 Created

airports

New in version 5.22. The airport search behind the airport fields when a flight is logged, as the website's airport picker on the Log flight page searches. New in version 5.23: a personal logbook account can call it too, and gets the pilot's airport categories on every hit (read only).

GET
/airports Airports whose code or name contains the text, the most likely first.
Information Parameters Response

Right: flightlogs:r for a member, logbook:r for a personal logbook account (since 5.23; an expired account gets 403 with code 10326). The website's own search, so the hits and their order are those of the Log flight page. For a member: an exact ICAO or IATA code first, then the airports the organization has logged most in the last three years, then a name that starts with the text, then the organization's country, the Nordic countries, Europe and the rest. For a personal logbook account: its own airports from Airports > Own airports first, then the airports of its own logbook. At most 20.

Returned: a list of airports, each with icao, name, country (as the website writes it: "Sweden", "Isle of Man", "USA"), latitude, longitude and own. name and country can be null. own is true for a personal logbook account's own airport (icao is then its own code); always false for a member.

New in 5.43: latitude and longitude, the airport's position in decimal degrees (WGS 84; north and east positive), for example to look up the weather there. Both are null when the position is not known.

A personal logbook account also gets, on every airport (since 5.23):

  • category: A, B or C on the date (the date parameter, else today): the highest category among the rules that apply then, A (a normal airport) when none does. B means self-study or other actions decided by the company, C further training according to the company's regulations.
  • category_rules: the pilot's rules for the airport (an empty list for none), each with category, period ({from, to} as "MM-DD", to before from over the new year; null for all year), applies_on_date, valid_months (the time limit from the last flight), simulator_counts, note (the company's requirements as the pilot wrote them), last_flight and last_flight_was_simulator, valid_until, status (current, soon, not_current, lapsed_off_season or never_flown), days_left (for soon) and warning_ignored. The status is always from today and the pilot's warning window.

Read only: the pilot makes, changes and ignores the rules on the website's Airports page. A member's reply has neither field.

In an app: show the choices of GET /flightlog-form while the field has fewer than 2 characters, and this search from 2 characters on, after a short pause in the typing (the website waits 200 ms). Whatever the member types may be sent, also when it is no hit.

400 with code 10005 at q when q is missing, or shorter than 2 or longer than 50 characters (spaces around it do not count), and at date when it is not a date written as YYYY-MM-DD.

q (text, required): 2 to 50 characters, matched against the ICAO code, the IATA code and the name
date (YYYY-MM-DD, personal logbook account): the date the category is for, today when left out
200 OK

logbook

New in version 5.14. The personal logbook of a personal logbook account (see "Two kinds of account" above): the flights the pilot has logged on the website's Log flight page, as the website's Logbook page shows them. Only a personal logbook account can call these endpoints (a member gets 403 with code 10325; the organization's flight log is /flightlogs), and an expired account gets 403 with code 10326. Right: logbook:r for reading, logbook:w for the writes.

New in version 5.39: GET /logbook/roster, the pilot's roster duties (the flights and simulator sessions their roster app writes into the myWebLog calendar) as the website's logbook shows them in amber, with POST .../ignore and .../restore, and roster_item_id in POST /logbook/flightlogs for a flight logged from a duty; the roster is a module of its own (roster, read and write), which an app has only when it has been given it. Also new in 5.39: GET /logbook/summary, the pilot's totals as the website's Summary page computes them (the hours before myWebLog included), for an app to show as of its last sync. Signing (on the device, with a drawing, and by an email request) and the flight's images, see the endpoints below and the fields signatures, signature_request and images. And an app logs, changes, strikes and restores flights (POST, PATCH, DELETE and POST .../restore below), through the website's own engine for the personal logbook, the same checks and the same row as the Log flight page; the pilot's lists behind the form (aircraft and simulators, types of flight, people, tags, own airports) and the form's settings are read from the same classes the page's pickers read, and an aircraft can be added. For an app that works offline, the logbook is a sync: every change of a flight (on the website, through the API, by the import, a signature or an image) stamps its updated_at; GET /logbook/flightlogs?updated_since= gives every flight changed since a point in time, struck flights included (deleted_at), oldest change first, and every list reply says the server's clock in "meta.server_time", which the app sends as updated_since next time. A flight the app logged offline carries the app's own client_reference, so a second send after a lost reply logs nothing twice; a change may carry expected_updated_at, so a flight changed on the website meanwhile is not overwritten unseen (409 with code 11170 and the flight as it is now). The lists carry an ETag: a request with If-None-Match naming it is answered 304 without a body.

GET
/logbook/flightlogs The flights in the personal logbook, newest first.
Information Filters Response

Newest first unless order=asc, in the website's order: by date, time of departure and row. Struck flights and the empty lines the website keeps for a paper page are left out; simulator sessions are in ("is_simulator" true). This is another logbook than /flightlogs, with a shape of its own.

A trial account (never paid) gets only its 10 most recent flights, the same as the website's exports (since 5.28); "logbook.flight_count" in GET /me still counts them all.

New in 5.39: the pilot's simulator is an individual in the pilot's aircraft list (as an aircraft, with the FSTD qualification number where an aircraft has its registration), and a session points at it. simulator gets fstd_type (the class: BITD, FNPT I, FNPT II, FNPT III, FTD, FFS or Other, or null), location (an airport or a city as typed, or null) and type ({designator, name} of the aircraft type it simulates, or null). A session logged with session time only and no simulator gives every field of simulator null.

New in 5.39, the sync: updated_since gives every flight changed at or after that point in time, struck flights included (deleted_at set), in the order of the changes (updated_at, then id), so a page can be applied as it comes; "meta.server_time" is the server's clock in UTC, to send as updated_since next time (a few seconds of overlap do no harm: merge by id). Without updated_since, deleted=true gives the struck flights only, and the default list none. New fields: simulator_airports (the airports trained on a session, as codes), is_locked (signed, or waiting for a signature by email: only the tags can change), client_reference (the app's own reference for a flight it logged, or null), source (who wrote the row last: "web", "Mobile v5", "import", "crosslog" or null), updated_at, deleted_at, and times.iri.

New in 5.39, signing and images: signatures (the flight's signatures, oldest first, each {id, signer_name, signer_licence, role, endorsement, method "device" or "email", signed_at in UTC, status, has_drawing}; status is the website's check of the signature against the flight as it is now: "valid", "changed" when the flight differs from what was signed, "altered" when the signature record itself was changed, "cannot_be_checked" when the server lacks the signing key; in a list the drawing is left out of the check, GET /logbook/flightlogs/{id} checks it too), signature_request (the latest request by email to sign the flight, {id, status waiting | expired | signed | declined | cancelled | withdrawn, signer_email, role, sent_at, expires_at}, or null), images (the flight's images, up to three, {id, width, height}; the bytes are GET .../images/{image_id}). is_locked is true for a signed flight and for one with a waiting request.

New in 5.44, the people behind the names: crew also has pic_id, sic_id, p3_id, p4_id and instructor_id, the person each name stands for (an id of GET /logbook/people; null for "SELF" and for a name that is not logged), and student_ids, the students' people in the order of students (0 for a student without a person). Two people can have the same name, so the id, not the name, says who it is.

Returned per flight: id, date, is_simulator, aircraft (registration, type {designator, name}, is_sea; null for a simulator session), simulator (id, name, identifier, fstd_type, location, type; null for a flight), flight_number, departure and arrival (airport {code, name, country}, time; since 5.40 also time_zone and utc_offset, for a pilot on local time and later for every pilot, see below), via (a list of codes), flight_type (id, name, or null), crew (pic, sic, p3, p4, instructor: the names as typed, "SELF" being the pilot, null when not logged; students: a list of names in the order logged, at most 3, empty when none; pic_id, sic_id, p3_id, p4_id, instructor_id and student_ids: the people behind the names, see above), is_spic, is_picus, times, simulator_times, takeoffs and landings (day, night, sea), touch_and_go, approaches (ils_cat1, ils_cat2, ils_cat3, localizer, vor, ndb, rnp, rnp_ar, visual), distance_nm, remarks, comments, organization_flight_id (set when the flight was copied from an organization's log), tags (id, name, color), simulator_airports, images, is_signed (a signed flight is locked on the website), is_locked, signatures, signature_request, client_reference, source, created_at, updated_at and deleted_at.

A flight time (times: total, pic, sic, dual, multi_pilot, solo, instructor, iri, lifus_given, night, ifr, instrument_actual, instrument_hood, cross_country, pilot_flying, aerobatics; simulator_times: total, pic, sic, instructor) is {"hours": the decimal hours as logged, "text": the time as the pilot shows it, "1:24" or "1.4" after "logbook.time_format" in GET /me}, or null when not logged: show "text", count with "hours". The places' codes are what the pilot typed (an ICAO code, an own airport's code or a word); name and country are given when the code is known. Clock times are UTC unless clock_times is local: in this reply date is always the UTC date of the off block, and departure.time and arrival.time are "HH:MM" in UTC (the arrival on the day after when it is the earlier of the two). Counts are 0 when not logged. The aircraft type's designator is the pilot's own code for the type; the name is given when it is a known type.

New in 5.40, local time: a pilot can log in local time at each airport (a setting on the website; GET /me says logbook.clock_times "local"). What is stored, and this reply, stay UTC. For such a pilot departure and arrival also have time_zone, the zone that end's local time is read in (an IANA name: the airport's, else the pilot's home zone, as for a simulator session), and utc_offset, that zone's minutes east of UTC at that moment (120 for UTC+2; null when the flight has no times): the local time is the UTC time plus utc_offset, and the logbook's date is the local date of the off block. Once the website opens the setting to every pilot, a pilot on UTC has the two fields too (until then only a pilot on local time has them): time_zone is then the airport's own zone, null for an airport without a known zone and for a simulator session, and utc_offset is null where time_zone is. A switch of the setting, or a corrected airport zone, does not stamp updated_at, so the sync does not give the flights again: keep the UTC values, work the local ones out when they are shown, and read the list again from the start when logbook.clock_times or logbook.home_time_zone in GET /me has changed. The filters (date_from, date_to), the order and updated_since work on the UTC values.

date_from, date_to (date): flights on these dates, inclusive
aircraft (text): only this registration, or a simulator's identifier
flight_type_id (int): only this own type of flight
simulator (bool): true gives only simulator sessions, false only flights
order: desc (newest first, the default) or asc
updated_since (date-time with its offset, or Z; new in 5.39): the sync, see above
deleted (bool, new in 5.39): true gives the struck flights only

limit, offset, include_total, exclude
200 OK
GET
/logbook/flightlogs/{id} One flight in the personal logbook.
Information Parameters Response

The same fields as in the list. 404 for a flight that is not the pilot's, is struck, or is a paper page's empty line, and (since 5.28) for a trial account's flight that is not one of its 10 most recent.

exclude
200 OK
POST
/logbook/flightlogs Logs a flight in the personal logbook, as the Log flight page does.
Information Body Response

New in version 5.39. Right: logbook:w. The flight goes through the website's own engine for the personal logbook: the same checks and the same row as the Log flight page. The body is the flight's own shape, the writable parts, nested as GET gives them. A flight has an aircraft (aircraft.registration, one of the pilot's, GET /logbook/aircraft; case does not matter) or is a simulator session (simulator.id, one of the pilot's simulators). A flight time is a number of hours (1.4167), the text the pilot types ("1:25" in hhmm, "1.4" in decimal) or the reply's own {"hours": n}; a crew name is the name as typed, "SELF" the pilot, or one of the pilot's short codes (GET /logbook/people), which is expanded to the name. Since 5.44 a name can come with its person, crew.pic_id, sic_id, p3_id, p4_id, instructor_id and student_ids (ids of GET /logbook/people; student_ids in the order of students, 0 for none): two people can have the same name, and the id says which of them is meant. An id is used when that person has the name sent with it; otherwise, and without an id, the name alone decides (the oldest person with that name, a new person when there is none). A PATCH that sends a name the flight already has, without an id, keeps the flight's person. An airport code is an ICAO code, an IATA code (turned into ICAO unless the pilot logs in IATA), an own airport's code or a word, at most 5 characters.

The checks are the engine's, the same the page makes: a date in the future (11102), an aircraft not in the list (11103) or inactive (11104), a flight and a session at once (11105), an unknown simulator (11106) or type of flight (11107), an airport text over 5 characters (11109), a time of day not HH:MM (11111), a flight time that is not a number of hours or over 24 (11112), a function time over the total (11113), a count over 999 (11114), a text too long (11115), an unknown tag (11116), simulator airports on a flight (11117), a roster duty that does not exist (11118), no PIC (11119), more than 3 students (11120): 400 with code 11100, "errors" with every problem, its field (the body's, "times.pic"), its code and a message. An unknown airport is a warning (11110): the flight is saved with the code as typed, and the warning is in "meta.warnings". A flight with the same date, aircraft, departure time and arrival time as a logged one is refused with 409 (code 11150), the same question the page asks: send it again with allow_duplicate true to log it anyway.

For an app that works offline: client_reference is a reference the app made for the flight (a UUID). The server keeps it with the row (it comes back as client_reference), and a second POST with the same reference, after a lost reply, logs nothing and answers 200 with the flight that exists. The tags, the students, the simulator airports and the roster link are saved after the row; a step that fails is a warning (11161) on a flight that is saved.

New in 5.40, clock_times: how date, departure.time and arrival.time of the body are to be read. "utc" (also when it is left out), or "local": the local date of the off block and the local time at each airport, as the pilot's logbook shows them. An app sends "local" only when GET /me says logbook.clock_times "local"; for a pilot on UTC it is refused with 409 (code 11171), and the app reads GET /me again. The server turns the local values into UTC before the checks (the arrival is the first time the arrival airport's clock shows arrival.time, from the off block and less than 24 hours on), so the checks and the reply are in UTC. A time that does not exist on that date (the hour skipped when summer time starts) is an error at departure.time or arrival.time (11121, in a 400 with code 11100); a time the clock shows twice (when summer time ends) is the first of the two. A flight without departure.time, or with both times 00:00, has no times and its date is kept as sent.

Returned: 201 with the flight as GET /logbook/flightlogs/{id} gives it, a Location header, and "meta.warnings". 500 with code 11160 when the row could not be saved.

client_reference (text, at most 36: letters, digits, dots, colons, underscores, hyphens)
date (YYYY-MM-DD, required)
aircraft {registration} or simulator {id}
flight_number (text, at most 8)
departure {airport {code}, time "HH:MM"}, via (list of codes, at most 5), arrival {airport {code}, time}
flight_type {id}
crew {pic, sic, p3, p4, instructor (text, at most 50 each), students (list of at most 3 names), pic_id, sic_id, p3_id, p4_id, instructor_id (int), student_ids (list of int)}
is_spic, is_picus (bool)
times {total, pic, sic, dual, multi_pilot, solo, instructor, iri, lifus_given, night, ifr, instrument_actual, instrument_hood, cross_country, pilot_flying, aerobatics} (each hours: a number, text, or {hours})
simulator_times {total, pic, sic, instructor} (hours)
takeoffs {day, night, sea}, landings {day, night, sea} (int, 0-999), touch_and_go (int)
approaches {ils_cat1, ils_cat2, ils_cat3, localizer, vor, ndb, rnp, rnp_ar, visual} (int)
distance_nm (int)
remarks (text, at most 100), comments (text, at most 1024)
tags (list of tag ids: the whole set), new_tags (list of names, at most 32 each)
simulator_airports (list of codes, a session only)
roster_item_id (int, since 5.39: the roster duty the flight is logged from, GET /logbook/roster; needs the right roster:w)
allow_duplicate (bool)
clock_times ("utc" or "local", since 5.40: how date and the two clock times are to be read; "utc" when left out)
201 Created
POST
/logbook/flightlogs/preview Checks a flight without saving it.
Information Body Response

New in version 5.39. Right: logbook:w. The same body and the same checks as POST /logbook/flightlogs, but nothing is saved. An app checks with it while the pilot types, when it has a connection; offline it checks with the limits of GET /logbook/flightlog-form, and the server has the last word.

Returned: "flight", the flight as the engine would save it, in the body's shape, with only the fields that were sent, as normalized (times as decimal hours, codes in capitals, a typed IATA code turned into ICAO, a crew short code expanded); "suggested", what the engine would fill in from the rest, in the same shape (times.total from the clock times, takeoffs.day and landings.day when a pilot flying time is given, distance_nm over known airports; empty when nothing); and "meta.warnings". A duplicate (11150) is a warning here, since there is nothing to confirm. 400 with the same problems POST would answer. With clock_times "local" (since 5.40, see POST /logbook/flightlogs) "flight" has the date and the clock times in UTC, as they would be saved; 409 (code 11171) for a pilot on UTC.

As POST /logbook/flightlogs (client_reference is ignored)
200 OK
PATCH
/logbook/flightlogs/{id} Changes a flight in the personal logbook.
Information Body Response

New in version 5.39. Right: logbook:w. Changes the fields that are sent, through the engine: a field left out stays as it is, a field sent as null is emptied ({"flight_type": {"id": null}} takes the type away; tags is the whole set, so [] takes every tag away). The same checks and codes as POST. A locked flight (is_locked: signed, or waiting for a signature by email) takes a change of its tags only; anything else is refused with 409 (code 11151).

For an app that works offline: send expected_updated_at, the flight's updated_at as the app last read it. When the flight has changed since (on the website, say), the change is refused with 409 (code 11170) and the flight as it is now in "flight", so the app can let the pilot choose; without it the last write wins, as the website has always worked. A flight that makes a duplicate of another is refused with 409 (code 11150) until allow_duplicate is sent.

With clock_times "local" (since 5.40, see POST /logbook/flightlogs) the date, clock times and airports that are sent are laid on the flight as the pilot sees it in local time, and the result is turned into UTC: a body with only departure.time changes the off block's local time (the stored UTC date follows when it has to), and a body with only a new airport keeps the local clock time, read at the new airport. A value that is not sent and comes out as it is stored is not touched; a body without date, clock times and airports is not affected. 409 (code 11171) for a pilot on UTC.

Returned: 200 with the flight as GET gives it and "meta.warnings". 404 for a flight that is not the pilot's, is struck or is a paper page's empty line.

Any of the fields of POST /logbook/flightlogs, and
expected_updated_at (date-time with its offset, or Z)
200 OK
DELETE
/logbook/flightlogs/{id} Strikes a flight; it can be restored.
Information Parameters Response

New in version 5.39. Right: logbook:w. Strikes the flight, as the Log flight page's delete does: the row is kept (its tags too), GET /logbook/flightlogs/{id} still gives it with deleted_at set, the sync gives it as a change, and POST .../restore brings it back. A signed flight may be struck; an open signature request by email is withdrawn. 204 also for a flight that is struck already; 404 for a flight that is not the pilot's or is a paper page's empty line.

None
204 No Content
POST
/logbook/flightlogs/{id}/restore Restores a struck flight.
Information Body Response

New in version 5.39. Right: logbook:w. A struck flight comes back as it was (a withdrawn signature request stays withdrawn: the pilot asks again). 200 with the flight, also for a flight that is not struck; 404 for a flight that is not the pilot's or is a paper page's empty line.

None
200 OK
POST
/logbook/flightlogs/{id}/signatures Signs the flight on the pilot's device.
Information Body Response

New in version 5.39. Right: logbook:w. The signer (an instructor, an examiner, a commander, or someone else) signs on the pilot's phone, as on the website's "Sign on this device" page: name, licence number, role, an optional endorsement in their own words, an optional drawing, and the confirmation that the entries are correct. The server stores a copy of the flight and a keyed hash over it with the signer's data (the website's class), so the flight is locked (is_locked) and a later change shows as status "changed" on the signature. A signature cannot be withdrawn: to correct a signed flight the pilot strikes it and logs it again. A flight may carry several signatures. When the signer gives an email address they get a receipt by mail.

For an app that was offline when the signer signed: send the flight first (its server id is needed), then the signature, with signed_at as the device's clock, between the flight's date and now; the hash covers signed_at, so what is stored is what was attested. Lock the flight in the app the moment it is signed, as the website does.

Returned: 201 with the flight as GET /logbook/flightlogs/{id} gives it (the new signature in signatures) and "meta.signature_id". 409 with code 11181 while a request by email is open on the flight (cancel it first); 400 with code 11182 for a drawing that is no PNG or too large; 500 with code 11183 when the server lacks the signing key; 404 for a flight that is not the pilot's, is struck or is a paper page's empty line.

signer {name (text, at most 100, required), licence (text, at most 50, required), role (instructor, examiner, commander or other, required), endorsement (text, at most 300), email}
drawing_png (text: a PNG as base64, at most 300 KB and 2000 by 1000 pixels)
signed_at (date-time with its offset, or Z)
confirmed (bool, must be true)
201 Created
GET
/logbook/flightlogs/{id}/signatures/{sid}/drawing A signature's drawing, a PNG.
Information Parameters Response

New in version 5.39. Right: logbook:r. The signer's drawing for a signature with has_drawing, as the bytes of a PNG (Content-Type image/png), with an ETag and Cache-Control for a day. 404 for a signature without a drawing, or one that is not on this flight.

None
200 OK
POST
/logbook/flightlogs/{id}/signature-request Asks someone to sign the flight by email.
Information Body Response

New in version 5.39. Right: logbook:w. As the website's "Ask someone to sign by email": the signer gets a fixed English mail with a personal link to the website's attest page, where they sign (or decline) without a login; the link works once and for seven days. While the request is open the flight is locked (is_locked true, signature_request.status "waiting"); the sync shows the change. The pilot may send at most 20 requests in 24 hours.

Returned: 201 with the flight. 409 with code 11185 when a request is open on the flight already (renew or cancel it), 409 with code 11184 when the day's requests are used; 404 for a flight that is not the pilot's, is struck or is a paper page's empty line.

signer_email (text, required)
role (instructor, examiner, commander or other, required)
201 Created
POST
/logbook/flightlogs/{id}/signature-request/renew Sends the open request again.
Information Body Response

New in version 5.39. Right: logbook:w. A new link is mailed to the same address (the old one stops working) and the request is good for seven more days. 200 with the flight; 404 when no request is open; 409 with code 11184 when the day's requests are used.

None
200 OK
DELETE
/logbook/flightlogs/{id}/signature-request Cancels the open request.
Information Parameters Response

New in version 5.39. Right: logbook:w. The pilot cancels the open request: the link stops working and the flight is unlocked. 204, also when no request is open; 404 for a flight that is not the pilot's.

None
204 No Content
GET
/logbook/flightlogs/{id}/images/{image_id} An image of the flight, a JPEG.
Information Parameters Response

New in version 5.39. Right: logbook:r. The image's bytes (Content-Type image/jpeg): the large copy the website keeps, at most 1600 pixels on the long side, with an ETag and Cache-Control for a day. The ids are in the flight's images. 404 for an image that is not on this flight.

None
200 OK
POST
/logbook/flightlogs/{id}/images Adds an image to the flight.
Information Body Response

New in version 5.39. Right: logbook:w. One more image of the flight, up to three, as the website's Log flight page keeps them: the body is multipart/form-data with one part, file (a JPEG, PNG, GIF or WebP of at most 20 MB and 25 million pixels), which the server scales to 1600 pixels on the long side and keeps as a JPEG. The same picture is refused on the same flight. Allowed on a locked flight too, as on the website: the images are not covered by a signature. An app queues images after the flight, as it queues signatures.

Returned: 201 with the flight (the new image in images), a Location header with the image's address and "meta.image_id". 409 with code 11186 when the flight has three images, 409 with code 11187 for the same picture again, 400 with code 11188 for a file that is no image or too large; 404 for a flight that is not the pilot's, is struck or is a paper page's empty line.

multipart/form-data: the part file (required), nothing else
201 Created
DELETE
/logbook/flightlogs/{id}/images/{image_id} Removes an image.
Information Parameters Response

New in version 5.39. Right: logbook:w. Removes the image and its files, as the website's page does. 204, also when the image is gone already or is not on this flight (nothing is removed then).

None
204 No Content
GET
/logbook/aircraft The pilot's aircraft and simulators.
Information Filters Response

New in version 5.39. Right: logbook:r. The pilot's own list of individuals (the website's Individuals page), as the Log flight page's pickers offer them, active ones first: the aircraft (kind "aircraft") and the simulators (kind "simulator"). Not paged: {"data": [...]}.

Returned per individual: id, kind, registration (for a simulator its FSTD qualification number, what a flight's simulator.identifier gives), type ({designator, name}, or null for a simulator without one), variant, is_sea, name (a simulator's name as the pilot calls it; null for an aircraft), fstd_type (a simulator's class), location (where a simulator stands), comment (an aircraft's) and is_active (an inactive individual is kept for old flights and refused on new ones).

The reply carries an ETag, a fingerprint of the list; a request with If-None-Match naming it (or "*") is answered 304 without a body, so an app refreshes its copy cheaply. The same holds for the other lists of /logbook and for /logbook/flightlog-form.

kind: aircraft or simulator; both when left out

Header If-None-Match
200 OK
POST
/logbook/aircraft Adds an aircraft or a simulator to the pilot's list.
Information Body Response

New in version 5.39. Right: logbook:w. Adds an individual as the Log flight page's "Add individual" dialog does, so a pilot can log on an aircraft they have not flown before. An aircraft needs a type: type.designator is an ICAO type designator, which GET /logbook/aircraft-types finds; a type the pilot does not have in their own type list yet (the website's Tools > Types) is added there first. A simulator (kind "simulator") may do without a type; it takes name, fstd_type and location.

Returned: 201 with the individual as GET /logbook/aircraft gives it. 409 with code 11190 when the registration is in the list already; 400 with code 11191 for an unknown type designator, 11192 for an aircraft without a type.

kind (aircraft, the default, or simulator)
registration (text, required; at most 8, a simulator's qualification number at most 40)
type {designator} (required for an aircraft)
variant (text, at most 10), is_sea (bool), comment (text, at most 50): an aircraft's
name (text, at most 50), fstd_type (BITD, FNPT I, FNPT II, FNPT III, FTD, FFS or Other), location (text, at most 32): a simulator's
is_active (bool, true when left out)
201 Created
GET
/logbook/aircraft-types The shared aircraft types, searched.
Information Filters Response

New in version 5.39. Right: logbook:r. The ICAO aircraft types myWebLog knows (the website's type search): the 25 best matches of the text in the designator or the name, designators that start with the text first. For POST /logbook/aircraft. Returned per type: designator, name, category (the ICAO category letter, such as L for a landplane), engines and licence_class (the class the type counts under on the website's Summary, such as "SEP (Land)").

q (text, required): 2 to 50 characters
200 OK
GET
/logbook/flight-types The pilot's types of flight.
Information Filters Response

New in version 5.39. Right: logbook:r. The pilot's own types of flight (Private, School, ...), by name, for flight_type.id: id, name and is_active. With an ETag, see GET /logbook/aircraft.

Header If-None-Match
200 OK
GET
/logbook/people The pilot's people, what the crew fields complete with.
Information Filters Response

New in version 5.39. Right: logbook:r. The people of the website's People tool, by name: id, name, short_code and, since 5.44, employee_number, nationality_code (the country as its ISO 3166-1 two-letter code, "SE"), notes, has_photo and has_same_name (each null when not given; the two flags true or false). Two people can have the same name (since 5.44): has_same_name is then true for both, and the short code, the employee number and the nationality tell them apart, so show those beside the name and send the chosen person's id with the name when a flight is logged (crew.pic_id ...). A crew field takes a name as typed; a short code typed instead is expanded to the name when the flight is saved. "SELF" is the pilot and is not a person. With an ETag, see GET /logbook/aircraft.

Header If-None-Match
200 OK
POST
/logbook/people Adds a person to the pilot's people.
Information Body Response

New in version 5.44. Right: logbook:w. Adds a person as the Log flight page's "Add person" dialog does, with the same rules. It is always a new person, also when the pilot has one with the same name already: it could be another person (both then have has_same_name true). To use an existing person, pick it from GET /logbook/people instead. A name typed in a crew field needs no person first: a flight saved with a new name makes the person by itself; this endpoint is for adding one with its details. The photo cannot be sent yet.

Returned: 201 with the person as GET /logbook/people gives it. 409 with code 11193 when the short code is another person's; 400 with code 11194 for an unknown country code.

name (text, required, at most 50; not "SELF")
short_code (text, at most 10, one per person)
employee_number (text, at most 20)
nationality_code (ISO 3166-1, two letters, "SE")
notes (text, at most 1000)
201 Created
GET
/logbook/tags The pilot's tags.
Information Filters Response

New in version 5.39. Right: logbook:r. The pilot's own tags: id, name and color, for the tags of a flight (ids) and new_tags (names). With an ETag, see GET /logbook/aircraft.

Header If-None-Match
200 OK
GET
/logbook/own-airports The pilot's own airports.
Information Filters Response

New in version 5.39. Right: logbook:r. The places the pilot has added under Airports > Own airports, which an airport field accepts besides the shared airports of GET /airports (an offline form needs them): code, name, country, latitude and longitude. With an ETag, see GET /logbook/aircraft.

Header If-None-Match
200 OK
GET
/logbook/flightlog-form What the Log flight form shows for this pilot.
Information Parameters Response

New in version 5.39. Right: logbook:r. The pilot's settings for the Log flight form, so an app builds the same form: time_format ("hhmm" or "decimal"), uses_iata (a typed IATA code is kept; otherwise it becomes ICAO), fields (the pilot's field choices as the website's fields panel has them, column name => on or off: the group switches cgrp_ifr, cgrp_fi and cgrp_sim, and the fields such as show_night, show_sic_name, show_tags, show_typeOfFlight, show_spicpicus, show_distance, and nova_30 to nova_33 for the crew roles P3, P4, instructor and students), defaults for a new flight (pic, from the "name or SELF" setting; aircraft_registration and departure_code from the pilot's latest flight, its aircraft and its arrival; flight_type_id from the default type setting or the latest flight; flight_number_prefix), limits (the longest texts and the largest values the body takes, by name) and problem_texts (the problem codes with their text in the language of Accept-Language, for an app that checks offline; a code without a text is left out). With an ETag, see GET /logbook/aircraft.

Header Accept-Language: sv, en, nb or da
Header If-None-Match
200 OK
GET
/logbook/summary The pilot's totals, as the website's Summary page.
Information Filters Response

New in version 5.39. Right: logbook:r. The personal logbook's totals from the same class the website's Summary page uses, so the app and the page show the same figures: the hours before myWebLog (the pilot's initial values, each type's and each simulator's) are in, the licence class of each type comes from the pilot's own type list, and the class split is the page's. An app computes no total of its own from its cached flights: it keeps this reply from its last sync and shows it "as of" then (as_of is the server's date).

totals is the page's "Total summary", all time with the initial values: flight_time, flights (every flight in an aircraft with a flight time; simulator sessions and the flights before myWebLog are not counted), landings and takeoffs {day, night, sea} (the page's landings: day for every class, night for the normal classes, sea its own count; the page's TOTAL is day + night), times (pic with spic and picus, sic, dual, multi_pilot, solo, night, ifr, cross_country, pilot_flying, instructor_se and instructor_me (FI SE, FI ME), iri_se, iri_me, multi_engine, simulator (instruction received), simulator_instructor, unidentified: the hours on registrations whose type the class split cannot place), approaches (as the flight's shape names them, with total) and by_class (the page's hours by class: sep_land, sep_sea, mep_land, mep_sea, setp, metp, sej, mej, normal_total, ul_a, ul_b, ul_total).

periods: 28_days, 90_days, 6_months and 12_months (the page's four, back from today with the page's own arithmetic), this_year and last_year (calendar years), each with from and to (the dates included) and the sums of the flights logged in it, as logged, no initial values: flight_time, flights, landings, takeoffs, times (pic, sic, dual, multi_pilot, solo, night, ifr, cross_country, pilot_flying, instructor, iri, simulator, simulator_instructor) and approaches. classes: the page's "Type/class" report, the licence classes by hours (most first), each with its types; a type's initial values (the hours and landings before myWebLog under Tools > Types) are inside flight_time and landings and also given apart as initial (null when none); periods on a class and a type are the four page periods, logged only. A flight whose type has no class, or no type at all, is under the class with name null (the type with designator null). years: one entry per calendar year with flights, latest first, with the same sums as a period.

Every time is {hours, text} as a flight's times are, but never null: nothing logged is {"hours": 0, "text": "0:00"} ("0.0" with decimal hours); the text is what the page prints after the pilot's time_format. Every count is a whole number. The reply carries an ETag; the figures change with every flight logged, so an app refreshes the summary after every sync (If-None-Match gives 304 when nothing changed).

Header If-None-Match
200 OK
304 Not Modified
GET
/logbook/roster The pilot's roster duties: coming flights and simulator sessions, and flown ones waiting to be logged.
Information Filters Response

New in version 5.39. Right: roster:r. The roster is a module of its own, which an app has only when myWebLog has given it to the app; an app without it gets 403 with code 10002 (GET /client says which modules the app has). The pilot's roster app (SAS Airside) writes the roster into the myWebLog calendar on their iPhone or iPad, and myWebLog reads the flights and the simulator sessions out of it. The website shows them in amber at the top of the logbook; they are read here through the same class, so the app and the website show the same duties.

scope=open (when left out) gives what the logbook shows: the duties that are not logged and not ignored, from 7 days back (flown, waiting to be logged) to the pilot's own number of hours ahead (meta.hours_ahead: 12, 24, 48, 72 or 168, from My settings on the website). scope=all gives what the website's Roster calendar page lists: every duty from 7 days back and every coming one, the logged and the ignored ones too. Oldest first, not paged.

A duty: id, kind ("flight" or "simulator"), status ("logged" when a flight in the logbook is linked to it, else "ignored", else "flown" when its scheduled start has passed, else "coming"), date (the UTC date of the scheduled start), scheduled_start and scheduled_end (UTC; the roster has scheduled times only), flight_number, departure_airport and arrival_airport {code, iata} (code is the ICAO code when the roster's IATA code is one known airport's, else the IATA code; both null on a simulator session), session_name (a session's name in the roster, "C224"), title (the calendar event's title as the roster app wrote it), flightlog_id (the linked flight) and ignored_at.

To log a flight from a duty, send the duty's id as roster_item_id in POST /logbook/flightlogs: the duty is linked to the flight and is no longer open. The link is a change of the roster, so the app needs roster:w for it besides logbook:w (403 with code 10002 without). The scheduled times are for showing next to the time fields; the website never fills them in as the flight's times. A flight the pilot logged by hand is linked to its duty when the duties are read (same day and flight number, or the same route within 30 minutes of the scheduled time; a simulator session with a session logged the same day).

meta: hours_ahead, connected_devices (how many of the pilot's devices are connected to the roster calendar; 0 means the roster is not set up, which is done on the website under Tools > Roster calendar) and last_contact_at (when a device was last in touch; over a week ago, the website warns that the roster app may have stopped writing). The reply carries an ETag; a duty's status changes as time passes, so the ETag does too.

scope (open or all)
Header If-None-Match
200 OK
304 Not Modified
POST
/logbook/roster/{id}/ignore Ignores a roster duty.
Information Body Response

New in version 5.39. Right: roster:w. The duty is no longer one of the open duties (the cross on an amber row of the website's logbook): for a duty the pilot will not log. 200 with the duty, also for a duty that is ignored already; 404 for a duty that is not the pilot's or is no longer in the roster.

None
200 OK
POST
/logbook/roster/{id}/restore Shows an ignored roster duty again.
Information Body Response

New in version 5.39. Right: roster:w. An ignored duty is open again ("Show again" on the website's Roster calendar page). 200 with the duty, also for a duty that is not ignored; 404 for a duty that is not the pilot's or is no longer in the roster.

None
200 OK

messages

New in version 5.13. The messages the organization's administrators have sent the member, as on the website's Messages page: the inbox, the archive, the whole message with its files, marking a message as read, and (new in 5.15) moving a read message to the archive and back. An important or urgent message can require that the member acknowledges it ("acknowledgement_required"); until they have, the website's booking rules stop them from booking (POST /bookings then answers 409 with code 10300 and the rule's text). Such a message is acknowledged with POST /messages/{id}/read and its "acknowledgement_key", which only GET /messages/{id} gives.

GET
/messages The member's messages, newest first: the inbox, the archive or both.
Information Filters Response

Right: messages:r. 20 per page unless limit says otherwise. Reading the list marks nothing as read.

Returned: id, subject, preview (the start of the text on one line), priority (normal, important or urgent), sent_at, sender {id, name}, read_at (null while unread), archived_at (null while in the inbox), acknowledgement_required, acknowledged_at and file_count. The whole text, the files and the acknowledgement key are only in GET /messages/{id}.

The list's "meta" also has "unread", the number of unread messages in the inbox (the number the website's menu shows), and "acknowledgement_pending", the number of messages in the inbox or the archive that wait for the member's acknowledgement.

folder (text): inbox when left out, archive, or all
unread (true/false): only the unread, or only the read messages
acknowledgement_pending (true/false): only the messages that wait for the member's acknowledgement, or only the others

limit, offset, include_total, exclude
200 OK
GET
/messages/{id} One message, whole, with its files and the acknowledgement key.
Information Parameters Response

Right: messages:r. The fields of the list, and also:

"body": the whole text as plain text, line breaks as \n. Show it as text, not as HTML (web addresses in it may be made links).
"sms_text": the SMS text when the message was also sent as SMS, otherwise null.
"files": the attached files, each with id, name, size_bytes and content_type; fetch one with GET /messages/{id}/files/{file_id}.
"acknowledgement_key": while the message waits for the member's acknowledgement, the key for POST /messages/{id}/read; null otherwise.

It does not mark the message as read: call POST /messages/{id}/read when the member has seen it. 404 when the member is not one of the message's recipients.

None
200 OK
POST
/messages/{id}/read Marks the message as read; acknowledges a message that must be acknowledged.
Information Body Response

Right: messages:w. A locked member may call it too, as they may acknowledge on the website.

A message with "acknowledgement_required" true that is not yet acknowledged is only marked as read together with the acknowledgement, and that needs its "acknowledgement_key" from GET /messages/{id}. So the app must have fetched the whole message, shown it to the member, and let the member confirm that they have read and understood it, as the website's "I have read and understood" does. Without the key: 409 with code 10321. With a key that is not this message's: 400 with code 10322 on the field "acknowledgement_key". The key belongs to the member and the message and does not change.

Any other message is simply marked as read; a key sent with it is ignored. Calling it again changes nothing. 200 with the message as it is afterwards, in the form of GET /messages/{id}; 404 when the member is not one of its recipients.

acknowledgement_key (text): only for a message that waits for the member's acknowledgement, { "acknowledgement_key": "5f0c4e1a…" }. Otherwise no body is needed.

200 OK
POST
/messages/{id}/archive Moves a read message from the inbox to the archive.
Information Body Response

New in version 5.15. Right: messages:w. A locked member may call it too, as they may archive on the website.

Only a read message can be archived: an unread one ("read_at" null) gives 409 with code 10323, so mark it as read first with POST /messages/{id}/read. A message that waits for the member's acknowledgement is unread until it is acknowledged, so it cannot be archived before that.

Calling it again on a message in the archive changes nothing. 200 with the message as it is afterwards, in the form of GET /messages/{id}, with "archived_at" set; 404 when the member is not one of its recipients. The archived messages are listed with GET /messages?folder=archive.

No body.

200 OK
POST
/messages/{id}/restore Moves a message from the archive back to the inbox.
Information Body Response

New in version 5.15. Right: messages:w. A locked member may call it too, as they may move messages back on the website.

A message in the inbox already is left as it is. 200 with the message as it is afterwards, in the form of GET /messages/{id}, with "archived_at" null; 404 when the member is not one of its recipients.

No body.

200 OK
GET
/messages/{id}/files/{file_id} A file attached to the message.
Information Parameters Response

Right: messages:r. The reply body is the file itself, not JSON, with its own Content-Type and its name in Content-Disposition (also for names with letters outside ASCII, RFC 6266). Not to be kept (Cache-Control: private, no-store). 404 when the member is not one of the message's recipients, or the file is not the message's or no longer exists.

None
200 OK

transactions

GET
/transactions Charges to and payments into the member's account, newest first.
Information Filters Response

Right: transactions:r. 20 per page unless limit says otherwise. What version 3 gave as GetTransactions.

Returned: id, date, amount, comment, booked_by, balance_after and created_at. "balance_after" is the member's balance after the transaction. The list's "meta" also has "balance", the balance now over all transactions, and "opening_balance", the balance before the oldest transaction on the page. A "#" and what follows it in a comment is left out of "comment", as in version 3.

With include=details each transaction also has "details": first the transaction itself (its comment up to the "#", and what is left of its amount after the parts), then each part, such as towing, a landing fee or rounding, each with "description" and "amount", as the website's transaction details show them. The amounts have the transaction's sign, so a charge's rows are negative, and they add up to the transaction's amount. An empty list when the transaction has no parts.

date_from (date): a year back when left out
date_to (date)

limit, offset, include_total, include (details), exclude
200 OK
GET
/transactions/{id} One transaction of the member.
Information Parameters Response

Right: transactions:r. The same fields and block as in the list. 404 when the transaction is not the member's.

include, exclude
200 OK

payments

The member pays into their own account, or pays the annual fee, the ways the website's "Payment to member account" offers: with Swish, by card on Nets Easy's payment page, or in their own bank (bankgiro or plusgiro). GET /payments/methods says which of them the organization has; each way has its own options endpoint with the details. The website's older Netaxept is not offered here.

Swish, as on the website's Swish page. A payment goes like this (see the example "A Swish payment, step by step"): 1. POST /payments/swish starts it. 2. The member approves it in the Swish app: on the same phone through "app_url", on a computer by scanning GET /payments/swish/{uuid}/qr, or Swish sends it to "payer_phone". 3. The app asks GET /payments/swish/{uuid} every 2 seconds until "status" is not "waiting" (Swish gives up after 3 minutes). 4. A paid payment is a transaction on the member's account: "transaction_id". A payment's id is 32 hexadecimal characters (Swish's own id), not a number. Swish is Swedish only: the currency is always SEK.

Nets Easy (card), as on the website's Nets page (see the example "A Nets card payment, step by step"): 1. POST /payments/nets creates the payment and gives "checkout_url", Nets' payment page, which the app opens in the browser. 2. The member pays there; Nets sends the browser to the app's "return_url" (with paymentid added) or "cancel_url". 3. The app calls POST /payments/nets/{uuid}/complete, which reads the payment from Nets and books it on the member's account. Nothing is booked until then. The id is Nets' payment id, also 32 hexadecimal characters.

Bank, as on the website's bank payment page: GET /payments/bank/options gives the giro number and the OCR reference, and GET /payments/bank/qr the same as a QR code for a Swedish bank app. The member makes the payment in their bank; the organization's bank file books it later. Nothing is started or booked through the API.

GET
/payments/swish/options Whether the member can pay with Swish, and what.
Information Parameters Response

Right: payments:r. "active" is false when the organization has no Swish integration; then "payee", the amounts and "annual_fee" are null, and the app hides Swish.

"payee" is the organization's name and Swish number. "min_amount" and "max_amount" are the organization's limits for a payment into the account.

"annual_fee" is { "year", "membership", "amount", "paid" }: the membership's fee for the year it is due (next year from November), "paid" true when it is paid already. null when the membership has no fee, and in a Norwegian organization (as the website).

None
200 OK
POST
/payments/swish Starts a Swish payment.
Information Body Response

Right: payments:w. Asks Swish for a payment request, through the website's Swish class. The reply is 201 with the payment (as GET /payments/swish/{uuid} gives it, "status": "waiting") and a Location header with its address.

Without "payer_phone" the reply has "app_url": open it on the same phone to approve the payment in the Swish app. To come back to your app afterwards, add &callbackurl= and your app's address, URL-encoded. On a computer, show GET /payments/swish/{uuid}/qr instead. With "payer_phone", Swish sends the request to that number and "app_url" is null.

The message the payer sees in Swish is the website's ("Payment to member account: Anna Andersson", or "Annual fee Senior Test FK 2027"), in the language of the Accept-Language header (sv, en, nb or da; English when left out).

409 with code 10310 when the organization has no Swish integration; 10311 when there is no annual fee to pay. 502 with code 10313 when Swish refuses: "errors" has Swish's own code in "swish_code", e.g. RP06 (another request is waiting for the payer) or ACMT03 (the number has no Swish).

purpose: required, "account" (into the member's account) or "annual_fee".

amount (number, at most two decimals): required for "account", from min_amount to max_amount. Not sent for "annual_fee": it is the membership's fee.

payer_phone (text): optional, the payer's mobile number with the country code first, digits only, e.g. "46701234567".

201 Created
GET
/payments/swish/{uuid} The payment now.
Information Parameters Response

Right: payments:r. What Swish has reported for the payment is booked first, so the status is the latest. "status" is "waiting", "paid", "declined" (the payer refused, or did not answer in time), "cancelled" or "error"; "error" then has Swish's "swish_code" and "message".

Also: "purpose", "annual_fee_year", "amount", "paid_amount" (once paid), "currency", "payer_phone" (once Swish has answered), "app_url" (while waiting), "transaction_id" (once paid: GET /transactions/{id}), "created_at", "completed_at".

404 when the payment is not the member's. Small letters in the id are taken too.

None
200 OK
POST
/payments/swish/{uuid}/cancel Cancels a payment that is still waiting.
Information Body Response

Right: payments:w. Cancels the payment request at Swish. The reply is the payment once Swish has confirmed the cancel, usually within a few seconds ("status": "cancelled"); if that takes longer it is still "waiting", and GET shows it later.

409 with code 10312 when the payment is no longer waiting (paid or declined in the meantime); 502 with code 10313 when Swish refuses.

None
200 OK
GET
/payments/swish/{uuid}/qr The QR code to scan with the Swish app, for a member on a computer.
Information Parameters Response

Right: payments:r. An SVG picture, 300 by 300 pixels, made by Swish (Content-Type: image/svg+xml), not JSON. Not to be kept (Cache-Control: no-store).

Only for a waiting payment started without "payer_phone"; 409 with code 10312 otherwise. 502 with code 10313 when Swish gives none.

None
200 OK
GET
/payments/methods The ways the organization takes a payment.
Information Parameters Response

Right: payments:r. A list of the ways the member can pay into their account, in the order the website shows them: "nets" (card, on Nets Easy's payment page), "swish", "bank" (bankgiro or plusgiro, in the member's own bank). Only those the organization has; an empty list when it has none.

"purposes" says what each way is for: "account", and "annual_fee" where the annual fee can be paid that way (never through nets; not in a Norwegian organization). "bank" also has "giro": "bankgiro" or "plusgiro".

None
200 OK
GET
/payments/bank/options What the member pays to in their bank.
Information Parameters Response

Right: payments:r. The details of a bankgiro or plusgiro payment, as the website's bank payment page shows them. "active" is false when the organization has no giro number; then the other fields are null.

"giro" is "bankgiro" or "plusgiro"; "payee" the organization's name and giro number, as the organization has written it. "reference" is the OCR reference the member writes on the payment, null when the organization does not use OCR; "reference_soft" is true when the bank is told to accept a reference that does not check out (the website then says "OCR/Reference").

"annual_fee" is the fee the member can pay this way, as in GET /payments/swish/options, with "number" (the organization's giro number for the fee, or the ordinary one) and "reference" (the fee's own OCR reference); null when there is none. "qr" is true when GET /payments/bank/qr gives a QR code (a Swedish organization).

Nothing is booked through the API: the organization's bank file books the payment later, on the reference.

None
200 OK
GET
/payments/bank/qr The bank payment as a QR code for a Swedish bank app.
Information Parameters Response

Right: payments:r. A PNG picture (Content-Type: image/png), not JSON: the payment in the "uqr" format Swedish bank apps read, with the giro number, the organization's name and number, the reference and, for the annual fee, the amount. As on the website, meant for a member on a computer, who scans it with the bank app on the phone. Not to be kept (Cache-Control: no-store).

409 with code 10314 when the organization has no giro number or is not Swedish; 10311 for an annual fee there is none to pay.

purpose: "account" (left out) or "annual_fee".

200 OK
GET
/payments/nets/options Whether the member can pay by card through Nets, and what.
Information Parameters Response

Right: payments:r. "active" is false when the organization has no Nets Easy integration; then the other fields are null and the app hides the card payment.

"currency" is the organization's. "suggested_amount" is what the website's page fills in: what the member owes, or the organization's standard amount. "terms_url" is the organization's terms and conditions for the payment (a PDF, no login needed), which Nets' payment page links to; null when the organization has not given myWebLog any, and then no payment can be started.

None
200 OK
POST
/payments/nets Starts a card payment through Nets.
Information Body Response

Right: payments:w. Creates the payment at Nets Easy, through the website's Nets class, and gives "checkout_url": Nets' hosted payment page, in the language of the Accept-Language header, which the app opens in the browser. The member pays there. The reply is 201 with the payment ("status": "waiting") and a Location header with its address.

When the member has paid, Nets sends the browser to "return_url" with paymentid added (?paymentid=... or &paymentid=...); when the member gives up, to "cancel_url". The app then calls POST /payments/nets/{uuid}/complete, which books the payment: nothing is booked until then.

409 with code 10315 when the organization has no Nets Easy integration; 10316 when it has no terms and conditions. 502 with code 10317 when Nets refuses: "errors" names the field Nets objects to (e.g. "checkout.Consumer.PhoneNumber.Number" when the member has no mobile number) with the website's text for it, or Nets' own.

amount (number): required, more than 0, at most two decimals, in the organization's currency.

return_url (text): required, your app's own address with its scheme ("https://..." or the app's own scheme), where Nets sends the browser when the member has paid.

cancel_url (text): optional, where Nets sends the browser when the member gives up. return_url when left out.

201 Created
GET
/payments/nets/{uuid} The payment as it is stored.
Information Parameters Response

Right: payments:r. "status" is "waiting" until POST /payments/nets/{uuid}/complete has booked the payment, then "paid", with "paid_amount", "payment_method" (as Nets names it, e.g. "Visa"), "card_number" (masked) and "transaction_id" (GET /transactions/{id}). "checkout_url" is only given in the reply that creates the payment. Also "amount", "currency", "created_at", "completed_at".

404 when the payment is not the member's. The id is as Nets writes it, in small letters; capitals are taken too.

None
200 OK
POST
/payments/nets/{uuid}/complete Books the payment the member has made on Nets' page.
Information Parameters Response

Right: payments:w. Called when the browser has come back to "return_url". The payment is read from Nets and booked on the member's account, as the website does when the member comes back from Nets' page; the member gets the website's receipt by e-mail. The reply is the payment, "status": "paid". A payment booked already is given as it is.

409 with code 10318 when Nets has charged nothing (the member did not pay). 502 with code 10317 when Nets could not be read: try again. 500 with code 10319 when the member was charged but the payment could not be booked: myWebLog's support has been notified and books it by hand.

None
200 OK

Examples

Login (cURL)

## 1. Open the login page in the browser (the app's library does this). {client_id} is the app's; the member logs in and allows the app there.
https://api.myweblog.se/mobile/v5/oauth/authorize?response_type=code&client_id={client_id}&redirect_uri={redirect_uri}&code_challenge={challenge}&code_challenge_method=S256&state={state}

## 2. The page sends the browser to {redirect_uri}?code={code}&state={state}. Exchange the code within two minutes. {key} only for a client that has one.
curl -u "{client_id}:{key}" \
  -d "grant_type=authorization_code" -d "code={code}" -d "redirect_uri={redirect_uri}" -d "code_verifier={verifier}" -d "device_name=iPhone 15" \
  https://api.myweblog.se/mobile/v5/oauth/token

## Then every call carries the access token.
curl -H "Authorization: Bearer {access_token}" https://api.myweblog.se/mobile/v5/me

## When a call answers 401 with error="invalid_token": renew. The old refresh token is dead afterwards.
curl -u "{client_id}:{key}" -d "grant_type=refresh_token" -d "refresh_token={refresh_token}" https://api.myweblog.se/mobile/v5/oauth/token

## Log out.
curl -u "{client_id}:{key}" -d "token={refresh_token}" https://api.myweblog.se/mobile/v5/oauth/revoke

Login reply

{
  "access_token": "mwlat_...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "organization:r objects:r bookings:rw flightlogs:r transactions:r",
  "refresh_token": "mwlrt_..."
}

GET me reply

{
  "data": {
    "id": 66311,
    "username": "3-anna",
    "account": "member",
    "member_number": "007",
    "name": { "first": "Anna", "prefix": "von", "last": "Berg", "full": "Anna von Berg" },
    "user_category": 2,
    "locked": false,
    "roles": [ "instructor" ],
    "has_photo": true,
    "organization": { "id": 3, "name": "Svanshalls FK", "homepage": "https://www.svanshallsfk.se" },
    "balance": 150.5,
    "currency": { "code": "SEK", "symbol": "kr" },
    "logbook": null
  }
}

GET me reply for a personal logbook account

{
  "data": {
    "id": 34278,
    "username": "pia",
    "account": "logbook",
    "member_number": null,
    "name": { "first": "Pia", "prefix": null, "last": "Lund", "full": "Pia Lund" },
    "user_category": null,
    "locked": false,
    "roles": [],
    "has_photo": false,
    "organization": null,
    "balance": null,
    "currency": null,
    "logbook": { "valid_until": "2027-03-31", "is_expired": false, "time_format": "hhmm", "flight_count": 412, "clock_times": "utc", "home_time_zone": null }
  }
}

GET logbook/flightlogs reply (one flight shown)

{
  "data": [
    {
      "id": 412233,
      "date": "2026-09-14",
      "is_simulator": false,
      "aircraft": { "registration": "SE-KGF", "type": { "designator": "C172", "name": "Cessna 172" }, "is_sea": false },
      "simulator": null,
      "flight_number": null,
      "departure": { "airport": { "code": "ESSB", "name": "Stockholm/Bromma", "country": "SWEDEN" }, "time": "09:10" },
      "via": [ "ESKN" ],
      "arrival": { "airport": { "code": "ESSB", "name": "Stockholm/Bromma", "country": "SWEDEN" }, "time": "10:35" },
      "flight_type": { "id": 3, "name": "Private" },
      "crew": { "pic": "SELF", "sic": null, "p3": null, "p4": null, "instructor": null, "students": [], "pic_id": null, "sic_id": null, "p3_id": null, "p4_id": null, "instructor_id": null, "student_ids": [] },
      "is_spic": false,
      "is_picus": false,
      "times": { "total": { "hours": 1.4, "text": "1:24" }, "pic": { "hours": 1.4, "text": "1:24" }, "sic": null, "dual": null, "multi_pilot": null, "solo": null, "instructor": null, "lifus_given": null, "night": null, "ifr": null, "instrument_actual": null, "instrument_hood": null, "cross_country": { "hours": 1.4, "text": "1:24" }, "pilot_flying": null, "aerobatics": null },
      "simulator_times": { "total": null, "pic": null, "sic": null, "instructor": null },
      "takeoffs": { "day": 1, "night": 0, "sea": 0 },
      "landings": { "day": 1, "night": 0, "sea": 0 },
      "touch_and_go": 0,
      "approaches": { "ils_cat1": 0, "ils_cat2": 0, "ils_cat3": 0, "localizer": 0, "vor": 0, "ndb": 0, "rnp": 0, "rnp_ar": 0, "visual": 0 },
      "distance_nm": 190,
      "remarks": "Nav exercise",
      "comments": null,
      "organization_flight_id": null,
      "tags": [ { "id": 5, "name": "Checkride prep", "color": "#2a7f62" } ],
      "is_signed": false,
      "created_at": "2026-09-14T11:02:13Z"
    }
  ],
  "meta": { "count": 1, "limit": 100, "offset": 0, "has_more": true },
  "links": { "next": "https://api.myweblog.se/mobile/v5/logbook/flightlogs?limit=100&offset=100" }
}

GET client reply

{
  "data": {
    "id": 4,
    "name": "Example Apps AB",
    "app_name": "Flyklubben",
    "rights": { "organization": "r", "objects": "r", "bookings": "rw", "flightlogs": "r", "transactions": "r" },
    "organizations": null,
    "rate_limit_per_minute": 600
  }
}

GET organization reply

{
  "data": {
    "id": 3,
    "name": "Svanshalls FK",
    "homepage": "https://www.svanshallsfk.se",
    "location": { "reference_icao": "ESMS", "latitude": 55.5363, "longitude": 13.3762, "country": "SWEDEN", "country_code": "SE", "timezone": "Europe/Stockholm", "utc_offset": "+02:00" },
    "date_format": "Y-m-d",
    "locale": "sv_SE",
    "currency": { "code": "SEK", "symbol": "kr" },
    "booking": { "enabled": true, "cancel_reason_required": true, "standard_length_hours": 3.5, "use_expected_airborne": true }
  }
}

GET sun-times reply

{
  "data": {
    "airport": { "icao": "ESMS", "latitude": 55.5363, "longitude": 13.3762 },
    "timezone": "Europe/Stockholm",
    "days": [
      { "date": "2026-06-21", "utc_offset": "+02:00",
        "dawn": { "at": "2026-06-21T01:22:50Z", "local": "2026-06-21T03:22:50+02:00" },
        "sunrise": { "at": "2026-06-21T02:23:14Z", "local": "2026-06-21T04:23:14+02:00" },
        "sunset": { "at": "2026-06-21T19:53:36Z", "local": "2026-06-21T21:53:36+02:00" },
        "dusk": { "at": "2026-06-21T20:54:00Z", "local": "2026-06-21T22:54:00+02:00" } }
    ]
  }
}

GET texts?lang=se reply (shortened)

ETag: "5d41402abc4b2a76b9719d911017c592"

{
  "data": {
    "about": "Om",
    "bookings": "Bokningar",
    "lby_welcomeText": "[[NAME]]! Välkommen till [[CLUBNAME]] och lobbyn.",
    "youHaveXBookingsToday": "Du har [x] bokning(ar) idag"
  }
}

The next launch sends If-None-Match: "5d41402abc4b2a76b9719d911017c592" and gets 304 Not Modified, with no body, until a text changes.

GET objects request

https://api.myweblog.se/mobile/v5/objects?include=status,settings

GET objects reply

{
  "data": [
    { "id": 710, "registration": "SE-ABC", "category": { "id": 0, "name": "Aircraft" }, "model": { "designator": "C172", "name": "Cessna 172" },
      "comment": "Club aircraft", "organization": { "id": 3, "name": "Svanshalls FK" }, "has_thumbnail": true,
      "status": { "total_id": 1, "maintenance_id": 1, "remarks_id": 0,
        "remaining_time": { "soft_airborne": 12.5, "soft_airborne_formatted": "12:30", "hard_airborne": 22.5, "hard_airborne_formatted": "22:30", "soft_days": 45, "hard_days": 60, "soft_tachometer": null, "soft_tachometer_formatted": null, "hard_tachometer": null, "hard_tachometer_formatted": null, "soft_tach": null, "soft_tach_formatted": null, "hard_tach": null, "hard_tach_formatted": null, "soft_hobbsmeter": null, "soft_hobbsmeter_formatted": null, "hard_hobbsmeter": null, "hard_hobbsmeter_formatted": null, "soft_landings": null, "hard_landings": null, "soft_cycles": null, "hard_cycles": null } },
      "settings": { "use_expected_airborne": true, "force_expected_time": false, "max_booking_length": null } }
  ],
  "meta": { "count": 1, "limit": 100, "offset": 0, "has_more": false },
  "links": { "next": null }
}

GET bookings request

https://api.myweblog.se/mobile/v5/bookings?date_from=2026-10-04&date_to=2026-10-04

GET bookings reply

{
  "data": [
    { "id": 4711, "start_at": "2026-10-04T08:00:00Z", "end_at": "2026-10-04T10:00:00Z",
      "start_local": "2026-10-04T10:00:00+02:00", "end_local": "2026-10-04T12:00:00+02:00", "timezone": "Europe/Stockholm",
      "object": { "id": 710, "registration": "SE-ABC", "category": { "id": 0, "name": "Aircraft" }, "organization": { "id": 3 } },
      "user": { "id": 66311, "name": "Anna von Berg", "member_number": "007", "email": "anna@example.com", "mobile": "+46 70 123 45 67" },
      "student": null, "calendar_name": "A.Berg",
      "type": "PRIV", "is_primary": true, "is_queue": false, "is_own": true, "is_student": false, "is_active_now": false, "is_passed": false, "details_hidden": false,
      "permissions": { "can_edit": true, "can_cancel": true, "can_cut": false, "queue_allowed": true },
      "expected_airborne": 1.5, "seats_left": 2, "comment": "Local flight", "reminders": { "email": true, "sms": false },
      "created_at": "2026-10-01T09:00:00Z", "created_by": "Anna von Berg" }
  ],
  "meta": { "count": 1, "limit": 100, "offset": 0, "has_more": false },
  "links": { "next": null }
}

GET non-bookable-times request

https://api.myweblog.se/mobile/v5/non-bookable-times?date_from=2026-06-20&date_to=2026-06-21

GET non-bookable-times reply

{
  "data": {
    "timezone": "Europe/Stockholm",
    "times": [
      { "rule_id": 12, "object_id": 710,
        "start_at": "2026-06-20T08:00:00Z", "end_at": "2026-06-20T14:00:00Z",
        "start_local": "2026-06-20T10:00:00+02:00", "end_local": "2026-06-20T16:00:00+02:00",
        "reason": "Flights on the airfield",
        "text": "SE-ABC cannot be booked Sat, Sun 10:00-16:00 (Flights on the airfield).",
        "can_book": false },
      { "rule_id": 12, "object_id": 710,
        "start_at": "2026-06-21T08:00:00Z", "end_at": "2026-06-21T14:00:00Z",
        "start_local": "2026-06-21T10:00:00+02:00", "end_local": "2026-06-21T16:00:00+02:00",
        "reason": "Flights on the airfield",
        "text": "SE-ABC cannot be booked Sat, Sun 10:00-16:00 (Flights on the airfield).",
        "can_book": false }
    ]
  }
}

POST bookings request

{
  "object_id": 710,
  "start_at": "2026-10-10T08:00:00Z",
  "end_at": "2026-10-10T12:00:00+02:00",
  "comment": "Local flight",
  "expected_airborne": 1.5,
  "seats_left": 2,
  "reminders": { "email": true, "sms": false }
}

POST bookings reply (201)

{
  "data": { "id": 4712, "start_at": "2026-10-10T08:00:00Z", "end_at": "2026-10-10T10:00:00Z", ... },
  "messages": [ { "kind": "info", "text": "Remember to fill in the expected airborne time." } ]
}

Reply when a booking rule stops the action

{
  "type": "https://api.myweblog.se/errors/conflict",
  "title": "A booking rule stopped the action",
  "status": 409,
  "code": 10300,
  "request_id": "b7e2c41a9d0f3e55",
  "errors": [ { "code": 10300, "message": "The object is already booked at that time." } ]
}

A Swish payment, step by step

## 1. Start it. Accept-Language: sv gives the payer's message in Swedish.
POST /payments/swish
{ "purpose": "account", "amount": 500 }

## 201, and Location: https://api.myweblog.se/mobile/v5/payments/swish/D4AF7584864341DDABDA864B4BA03897
{
  "data": {
    "id": "D4AF7584864341DDABDA864B4BA03897",
    "status": "waiting",
    "purpose": "account",
    "annual_fee_year": null,
    "amount": 500,
    "paid_amount": null,
    "currency": "SEK",
    "payer_phone": null,
    "app_url": "swish://paymentrequest?token=c28a4061470f4af48973bd2a4642b4fa",
    "error": null,
    "transaction_id": null,
    "created_at": "2026-10-10T07:56:46Z",
    "completed_at": null
  }
}

## 2. Open app_url, with your own address to come back to:
swish://paymentrequest?token=c28a4061470f4af48973bd2a4642b4fa&callbackurl=se.example.app%3A%2F%2Fswish-done

## 3. Ask every 2 seconds until status is not "waiting"
GET /payments/swish/D4AF7584864341DDABDA864B4BA03897

## 200, once the member has paid
{ "data": { "id": "D4AF7584864341DDABDA864B4BA03897", "status": "paid", ..., "paid_amount": 500, "payer_phone": "46701234567", "app_url": null, "transaction_id": 2459371, "completed_at": "2026-10-10T07:57:06Z" } }

Reply when Swish refuses a payment

{
  "type": "https://api.myweblog.se/errors/bad-gateway",
  "title": "Swish refused the payment request",
  "status": 502,
  "code": 10313,
  "request_id": "b7e2c41a9d0f3e55",
  "errors": [ { "code": 10313, "swish_code": "RP06", "message": "A payment request already exists for that payer" } ]
}

GET payments/methods reply

{ "data": [ { "method": "nets", "purposes": ["account"] }, { "method": "swish", "purposes": ["account", "annual_fee"] }, { "method": "bank", "purposes": ["account", "annual_fee"], "giro": "bankgiro" } ] }

GET payments/bank/options reply

{
  "data": {
    "active": true,
    "giro": "bankgiro",
    "currency": "SEK",
    "payee": { "name": "Test FK", "number": "123-4567" },
    "reference": "97001584313",
    "reference_soft": false,
    "annual_fee": { "year": 2027, "membership": "Senior", "amount": 1200, "paid": false, "number": "987-6543", "reference": "99970015843" },
    "qr": true
  }
}

A Nets card payment, step by step

## 1. Start it. Accept-Language: sv gives Nets' payment page in Swedish.
POST /payments/nets
{ "amount": 250, "return_url": "se.example.app://nets-done", "cancel_url": "se.example.app://nets-cancelled" }

## 201, and Location: https://api.myweblog.se/mobile/v5/payments/nets/025400006091b1ef6937598058c4e487
{
  "data": {
    "id": "025400006091b1ef6937598058c4e487",
    "status": "waiting",
    "amount": 250,
    "paid_amount": null,
    "currency": "SEK",
    "payment_method": null,
    "card_number": null,
    "checkout_url": "https://checkout.dibspayment.eu/hostedpaymentpage/?checkoutKey=...&pid=025400006091b1ef6937598058c4e487&language=sv-SE",
    "transaction_id": null,
    "created_at": "2026-10-13T07:56:46Z",
    "completed_at": null
  }
}

## 2. Open checkout_url in the browser. The member pays; Nets sends the browser to
se.example.app://nets-done?paymentid=025400006091b1ef6937598058c4e487

## 3. Book it
POST /payments/nets/025400006091b1ef6937598058c4e487/complete

## 200
{ "data": { "id": "025400006091b1ef6937598058c4e487", "status": "paid", "amount": 250, "paid_amount": 250, "currency": "SEK", "payment_method": "Visa", "card_number": "492500******0004", "checkout_url": null, "transaction_id": 2459380, "created_at": "2026-10-13T07:56:46Z", "completed_at": "2026-10-13T07:58:02Z" } }

Reply when Nets refuses a payment

{
  "type": "https://api.myweblog.se/errors/bad-gateway",
  "title": "Nets refused the payment",
  "status": 502,
  "code": 10317,
  "request_id": "b7e2c41a9d0f3e55",
  "errors": [ { "code": 10317, "field": "checkout.Consumer.PhoneNumber.Number", "message": "Mobile phone number is missing. Please check your member details." } ]
}

GET flightlogs reply

{
  "data": [
    { "id": 88, "date": "2026-10-03", "object": { "id": 710, "registration": "SE-ABC", "organization": { "id": 3, "name": "Svanshalls FK" } },
      "flight_type": { "id": 2, "name": "School" },
      "departure": { "airport": { "icao": "ESMS", "name": "Malmö" }, "blockoff_at": "2026-10-03T09:10:00Z", "takeoff_at": "2026-10-03T09:20:00Z", "tachometer": 1234.5, "hobbs": null },
      "via_route": null,
      "arrival": { "airport": { "icao": "ESSA", "name": "Arlanda" }, "landing_at": "2026-10-03T11:10:00Z", "blockon_at": "2026-10-03T11:20:00Z", "tachometer": 1236.4, "hobbs": null },
      "crew_hidden": false,
      "pilot": { "id": 66311, "name": "Anna von Berg", "member_number": "007", "organization": { "id": 3, "name": "Svanshalls FK" } },
      "instructor": null, "scout": null, "is_solo_instruction": false,
      "uplift": { "fuel": 42, "oil": 0 }, "fuel_onboard": 60,
      "totals": { "block": 2.17, "block_minutes": 130, "airborne": 1.83, "airborne_minutes": 110, "tach": 1.9, "tach_minutes": 114, "hobbs": null, "hobbs_minutes": null },
      "number_of_flights": 1, "engine_cycles": null, "daily_check": true, "comment": "Night", "remark_id": null, "created_at": "2026-10-03T11:25:31Z" }
  ],
  "meta": { "count": 1, "limit": 100, "offset": 0, "has_more": false },
  "links": { "next": null }
}

A message that must be acknowledged, step by step

## 1. The messages that wait for the member's acknowledgement (for one, after POST /bookings answered 409 because of one)
curl "https://api.myweblog.se/mobile/v5/messages?acknowledgement_pending=true&folder=all" -H "Authorization: Bearer {access_token}"

## 2. The whole message, to show the member. It has the acknowledgement_key.
curl "https://api.myweblog.se/mobile/v5/messages/302" -H "Authorization: Bearer {access_token}"

## 3. The member confirms they have read and understood it: acknowledged and read. Without the key: 409 (10321).
curl -X POST "https://api.myweblog.se/mobile/v5/messages/302/read" -H "Content-Type: application/json" -H "Authorization: Bearer {access_token}" \
  -d '{ "acknowledgement_key": "5f0c4e1a9b7d3c2e8f6a1b0d4c7e9f2a3b5d8c1e0f4a7b9c2d6e8f1a3b5c7d9e" }'

## Any other message: no body
curl -X POST "https://api.myweblog.se/mobile/v5/messages/301/read" -H "Authorization: Bearer {access_token}"

## 4. Once read, the member can move it to the archive. An unread message: 409 (10323).
curl -X POST "https://api.myweblog.se/mobile/v5/messages/302/archive" -H "Authorization: Bearer {access_token}"

## Back to the inbox
curl -X POST "https://api.myweblog.se/mobile/v5/messages/302/restore" -H "Authorization: Bearer {access_token}"

GET messages/302 reply

{
  "data": {
    "id": 302, "subject": "New fuel routine", "preview": "Read the new fuel routine before your next flight. It applies from Monday.",
    "priority": "important", "sent_at": "2026-10-13T07:30:00Z", "sender": { "id": 7, "name": "Eva Admin" },
    "read_at": null, "archived_at": null, "acknowledgement_required": true, "acknowledged_at": null, "file_count": 1,
    "body": "Read the new fuel routine before your next flight.\nIt applies from Monday.",
    "sms_text": null,
    "files": [ { "id": 41, "name": "Fuel routine.pdf", "size_bytes": 182034, "content_type": "application/pdf" } ],
    "acknowledgement_key": "5f0c4e1a9b7d3c2e8f6a1b0d4c7e9f2a3b5d8c1e0f4a7b9c2d6e8f1a3b5c7d9e"
  }
}

Log a flight: the form, the preview, the entry

## 1. Which fields the body uses and requires for this object and flight type (the pilot is the member)
curl "https://api.myweblog.se/mobile/v5/flightlog-form?object_id=710&flight_type_id=7" -H "Authorization: Bearer {access_token}" -H "Accept-Language: sv"

## 2. The price, without saving (call it again after a change)
curl -X POST "https://api.myweblog.se/mobile/v5/flightlogs/preview" -H "Content-Type: application/json" -H "Authorization: Bearer {access_token}" -H "Accept-Language: sv" \
  -d '{ "object_id": 710, "flight_type_id": 7, "date": "2026-10-08", "departure_icao": "ESSB", "arrival_icao": "ESKN",
      "blockoff_at": "2026-10-08T10:05:00Z", "blockon_at": "2026-10-08T11:20:00Z", "tach_out": 1234.5, "tach_in": 1235.7,
      "number_of_flights": 1, "fuel_uplift": 42, "oil_uplift": 0, "daily_check": true, "comment": "Touch and go x3" }'

## 3. The entry, with the total the member confirmed. 201 with the flight; 409 (11051) if the price has changed since.
curl -X POST "https://api.myweblog.se/mobile/v5/flightlogs" -H "Content-Type: application/json" -H "Authorization: Bearer {access_token}" -H "Accept-Language: sv" \
  -d '{ ...the same body..., "confirmed_total": 1488.00 }'

GET flightlog-form reply (shortened)

{
  "data": {
    "object": { "id": 710, "registration": "SE-ABC", "model": "C172" }, "flight_type": { "id": 7, "name": "PRIVAT" },
    "flight_types": [ { "id": 7, "name": "PRIVAT", "admin_only": false }, { "id": 8, "name": "SKOLA", "admin_only": false } ],
    "fields": {
      "object_id": { "used": true, "required": true }, "flight_type_id": { "used": true, "required": true }, "pilot_id": { "used": true, "required": false },
      "instructor_id": { "used": false, "required": false }, "is_solo_instruction": { "used": false, "required": false }, "scout_id": { "used": false, "required": false },
      "date": { "used": true, "required": true },
      "departure_icao": { "used": true, "required": true, "suggested": "ESSB", "choices": [ { "icao": "ESSB", "name": "STOCKHOLM/BROMMA" }, { "icao": "ESSU", "name": "ESKILSTUNA/KJULA" } ] },
      "arrival_icao": { "used": true, "required": true, "choices": [ the same list ] }, "via": { "used": true, "required": false, "max_items": 5, "choices": [ the same list ] },
      "number_of_flights": { "used": true, "required": true, "max": null, "suggested": 1 }, "distance": { "used": false, "required": false, "unit": "NM" },
      "blockoff_at": { "used": true, "required": false }, "blockon_at": { "used": true, "required": false }, "total_block": { "used": true, "required": false, "type": "hours" },
      "takeoff_at": { "used": true, "required": false }, "landing_at": { "used": true, "required": false }, "total_airborne": { "used": true, "required": false, "type": "hours" },
      "tach_out": { "used": true, "required": true, "type": "decimal", "decimals": 2, "suggested": "1234.50", "locked": true }, "tach_in": { "used": true, "required": true, "type": "decimal", "decimals": 2 },
      "hobbs_out": { "used": false, "required": false, "type": "decimal", "decimals": 1 }, "hobbs_in": { "used": false, "required": false, "type": "decimal", "decimals": 1 },
      "tow_object_id": { "used": false, "required": false, "choices": [] }, "tow_landing_at": { "used": false, "required": false }, "total_tow": { "used": false, "required": false, "type": "hours" },
      "tow_height_id": { "used": false, "required": false, "choices": [] }, "tow_height_value": { "used": false, "required": false },
      "fuel_uplift": { "used": true, "required": true, "unit": "l" }, "oil_uplift": { "used": true, "required": false, "unit": "l" }, "daily_check": { "used": true, "required": true, "suggested": false },
      "comment": { "used": true, "required": false, "max_length": 200 },
      "remark": { "used": true, "required": false, "categories": [ { "id": 1, "name": "Anmärkning", "blocks_object": false }, { "id": 2, "name": "Röd anmärkning", "blocks_object": true } ], "blocking_allowed": true },
      "cut_booking_id": { "used": true, "required": true, "booking": { "id": 99812, "registration": "SE-ABC", "starts_at": "2026-10-08T08:00:00Z", "ends_at": "2026-10-08T10:00:00Z" } },
      "pfly": { "used": false, "required": false }, "confirmed_total": { "used": true, "required": false }
    },
    "required_one_of": [ { "code": 11030, "message": "State the block time: both clock times, or the total", "one_of": [ ["blockoff_at", "blockon_at"], ["total_block"] ] } ],
    "charge_visible": true, "instructions": "Kom ihåg den dagliga tillsynen före dagens första flygning."
  }
}

POST flightlogs/preview reply

{
  "data": {
    "object": { "id": 710, "registration": "SE-ABC" }, "flight_type": { "id": 7, "name": "PRIVAT" },
    "pilot": { "id": 66311, "name": "Anna von Berg" }, "charged_member": { "id": 66311, "name": "Anna von Berg" }, "date": "2026-10-08",
    "totals": { "block": 1.25, "airborne": null, "tach": 1.2, "hobbs": null, "tow": null },
    "charge_visible": true,
    "charge": {
      "currency": "SEK", "charged_member": { "id": 66311, "name": "Anna von Berg" }, "transaction_date": "2026-10-08",
      "rows": [
        { "kind": "time", "text": "Tach (1234.5 - 1235.7)", "quantity": 1.2, "unit": "h", "unit_price": 1200, "percent": false, "amount": 1440 },
        { "kind": "correction", "text": "Medlemsrabatt", "quantity": 1.2, "unit": "h", "unit_price": -60, "percent": false, "amount": -72 },
        { "kind": "correction", "text": "Landningsavgift ESSB", "quantity": 1, "unit": null, "unit_price": 120, "percent": false, "amount": 120 }
      ],
      "subtotal": 1488, "rounding": 0, "zero_floor": 0, "total": 1488, "vat": { "percent": 25, "amount": 297.6, "registration_number": "SE556000000001" }
    }
  },
  "meta": { "warnings": [] }
}

Reply when the engine finds problems (400)

{
  "type": "https://api.myweblog.se/errors/validation", "title": "The flight can not be logged as it was sent", "status": 400, "code": 11000, "request_id": "b7e2c41a9d0f3e55",
  "errors": [
    { "field": "total_tach", "code": 11030, "message": "State the tach time" },
    { "field": "fuel_uplift", "code": 11043, "message": "State the fuel uplift (0 if none)" },
    { "field": "number_of_flights", "code": 11025, "message": "Unreasonable number of flights" }
  ]
}

GET transactions reply

{
  "data": [
    { "id": 903, "date": "2026-10-05", "amount": -0.7, "comment": "Landing", "booked_by": "Eva Admin via API", "balance_after": 170.5, "created_at": "2026-10-05T12:00:00Z" }
  ],
  "meta": { "count": 1, "limit": 20, "offset": 0, "has_more": true, "balance": 150.5, "opening_balance": 171.2 },
  "links": { "next": "https://api.myweblog.se/mobile/v5/transactions?offset=20" }
}

GET logbook/summary reply (shortened: one period, one class, one year shown)

{
  "data": {
    "as_of": "2026-11-04",
    "time_format": "hhmm",
    "totals": {
      "flight_time": { "hours": 1234.5, "text": "1234:30" },
      "flights": 1021,
      "landings": { "day": 980, "night": 61, "sea": 0 },
      "takeoffs": { "day": 975, "night": 60, "sea": 0 },
      "times": { "pic": { "hours": 900, "text": "900:00" }, "spic": { "hours": 0, "text": "0:00" }, "picus": { "hours": 0, "text": "0:00" }, "sic": { "hours": 120, "text": "120:00" }, "dual": { "hours": 95.5, "text": "95:30" }, "multi_pilot": { "hours": 0, "text": "0:00" }, "solo": { "hours": 12, "text": "12:00" }, "night": { "hours": 48.2, "text": "48:12" }, "ifr": { "hours": 210, "text": "210:00" }, "cross_country": { "hours": 600, "text": "600:00" }, "pilot_flying": { "hours": 0, "text": "0:00" }, "instructor_se": { "hours": 80, "text": "80:00" }, "instructor_me": { "hours": 0, "text": "0:00" }, "iri_se": { "hours": 0, "text": "0:00" }, "iri_me": { "hours": 0, "text": "0:00" }, "multi_engine": { "hours": 150, "text": "150:00" }, "simulator": { "hours": 40, "text": "40:00" }, "simulator_instructor": { "hours": 0, "text": "0:00" }, "unidentified": { "hours": 0, "text": "0:00" } },
      "approaches": { "ils_cat1": 12, "ils_cat2": 0, "ils_cat3": 0, "localizer": 2, "vor": 4, "ndb": 1, "rnp": 9, "rnp_ar": 0, "visual": 20, "total": 48 },
      "by_class": { "sep_land": { "hours": 1084.5, "text": "1084:30" }, "sep_sea": { "hours": 0, "text": "0:00" }, "mep_land": { "hours": 150, "text": "150:00" }, "mep_sea": { "hours": 0, "text": "0:00" }, "setp": { "hours": 0, "text": "0:00" }, "metp": { "hours": 0, "text": "0:00" }, "sej": { "hours": 0, "text": "0:00" }, "mej": { "hours": 0, "text": "0:00" }, "normal_total": { "hours": 1234.5, "text": "1234:30" }, "ul_a": { "hours": 0, "text": "0:00" }, "ul_b": { "hours": 0, "text": "0:00" }, "ul_total": { "hours": 0, "text": "0:00" } }
    },
    "periods": {
      "28_days": { "from": "2026-10-07", "to": "2026-11-04", "flight_time": { "hours": 6.5, "text": "6:30" }, "flights": 5, "landings": { "day": 8, "night": 1, "sea": 0 }, "takeoffs": { "day": 8, "night": 1, "sea": 0 }, "times": { "pic": { "hours": 6.5, "text": "6:30" }, "sic": { "hours": 0, "text": "0:00" }, "dual": { "hours": 0, "text": "0:00" }, "multi_pilot": { "hours": 0, "text": "0:00" }, "solo": { "hours": 0, "text": "0:00" }, "night": { "hours": 1, "text": "1:00" }, "ifr": { "hours": 2, "text": "2:00" }, "cross_country": { "hours": 4, "text": "4:00" }, "pilot_flying": { "hours": 0, "text": "0:00" }, "instructor": { "hours": 0, "text": "0:00" }, "iri": { "hours": 0, "text": "0:00" }, "simulator": { "hours": 0, "text": "0:00" }, "simulator_instructor": { "hours": 0, "text": "0:00" } }, "approaches": { "ils_cat1": 1, "ils_cat2": 0, "ils_cat3": 0, "localizer": 0, "vor": 0, "ndb": 0, "rnp": 1, "rnp_ar": 0, "visual": 2, "total": 4 } },
      "90_days": { ... }, "6_months": { ... }, "12_months": { ... }, "this_year": { "from": "2026-01-01", "to": "2026-11-04", ... }, "last_year": { "from": "2025-01-01", "to": "2025-12-31", ... }
    },
    "classes": [
      { "name": "SEP (land)", "flight_time": { "hours": 1084.5, "text": "1084:30" }, "flights": 950, "landings": 1010,
        "periods": { "28_days": { "flight_time": { "hours": 6.5, "text": "6:30" }, "flights": 5, "landings": 9 }, "90_days": { ... }, "6_months": { ... }, "12_months": { ... } },
        "types": [
          { "designator": "C172", "name": "Cessna 172", "flight_time": { "hours": 820, "text": "820:00" }, "flights": 700, "landings": 760, "initial": { "flight_time": { "hours": 120, "text": "120:00" }, "landings": 130 }, "periods": { "28_days": { ... }, "90_days": { ... }, "6_months": { ... }, "12_months": { ... } } },
          { "designator": "PA28", "name": "Piper PA-28", ..., "initial": null, ... }
        ]
      },
      { "name": "MEP (land)", ... }
    ],
    "years": [
      { "year": 2026, "flight_time": { "hours": 88.2, "text": "88:12" }, "flights": 70, "landings": { "day": 75, "night": 6, "sea": 0 }, "takeoffs": { "day": 75, "night": 6, "sea": 0 }, "times": { ... }, "approaches": { ... } },
      { "year": 2025, ... }
    ]
  }
}

GET logbook/roster reply

{
  "data": [
    { "id": 31, "kind": "flight", "status": "flown", "date": "2026-11-05", "scheduled_start": "2026-11-05T06:55:00Z", "scheduled_end": "2026-11-05T08:05:00Z", "flight_number": "SK0552", "departure_airport": { "code": "EKCH", "iata": "CPH" }, "arrival_airport": { "code": "ESSA", "iata": "ARN" }, "session_name": null, "title": "SK0552 CPH-ARN (GO)", "flightlog_id": null, "ignored_at": null },
    { "id": 33, "kind": "simulator", "status": "coming", "date": "2026-11-06", "scheduled_start": "2026-11-06T08:00:00Z", "scheduled_end": "2026-11-06T12:00:00Z", "flight_number": null, "departure_airport": null, "arrival_airport": null, "session_name": "C224", "title": "C224 - Simulator", "flightlog_id": null, "ignored_at": null }
  ],
  "meta": { "hours_ahead": 24, "connected_devices": 1, "last_contact_at": "2026-11-05T05:12:00Z" }
}

GET transactions/184233?include=details reply

{
  "data": {
    "id": 184233, "date": "2026-10-05", "amount": -1450, "comment": "SE-ABC [2026-10-05] 1:12", "booked_by": "Eva Admin via API", "balance_after": 2170.5, "created_at": "2026-10-05T12:04:31Z",
    "details": [
      { "description": "SE-ABC [2026-10-05] 1:12", "amount": -1125 },
      { "description": "Landing fee", "amount": -125 },
      { "description": "Fuel surcharge", "amount": -200 }
    ]
  }
}

Error Codes

"code" in an error reply is one of these numbers. Codes up to 10199 and from 11000 are the same as in the Main API v5; codes from 10300 are the Mobile API's own. The /oauth endpoints answer with the OAuth error form instead, except 429, 500 and 503.

Code Name Comment Response
10000 HTTPS is required A call over plain HTTP is normally redirected to HTTPS by the server before it reaches the API.
403 Forbidden
10001 Unauthorized The access token is missing, not accepted, or has expired (then WWW-Authenticate has error="invalid_token": renew). Also when the login has been ended, the member is no longer active, or the client or its key has been revoked.
401 Unauthorized
10002 No access to the module The client lacks the read or write right the endpoint needs. Ask myWebLog to change the client's rights.
403 Forbidden
10003 The address is blocked The IP address is on myWebLog's block list.
403 Forbidden
10004 The request body must be a JSON object The body of a POST or PATCH could not be read as JSON. For POST /me/expiry-dates/{type_id}/submission: the body is not multipart/form-data.
400 Bad Request
10005 Invalid parameter A query parameter has the wrong form. "errors" names it.
400 Bad Request
10006 Invalid field A field of the body is missing or has the wrong type or form. "errors" names each field.
400 Bad Request
10007 Unknown parameter or field The endpoint does not have the named query parameter or body field. Check the spelling.
400 Bad Request
10010 Internal error A database error on our side. It has been logged. Nothing was saved.
500 Internal Server Error
10012 Too many failed login attempts The username or the IP address has too many failed logins lately, on the website or here. Wait Retry-After seconds.
429 Too Many Requests
10013 Too many requests The member (120 a minute) or the client (600 a minute) has made too many calls. Wait Retry-After seconds.
429 Too Many Requests
10014 Too many failed authorization attempts Too many wrong client credentials from the IP address. Wait Retry-After seconds.
429 Too Many Requests
10020 Internal error Something unexpected on our side. It has been logged; quote the request id to support.
500 Internal Server Error
10050 Method not allowed The address exists but not with this method. The Allow header says which methods it accepts.
405 Method Not Allowed
10060 Closed for maintenance myWebLog is closed while the database or the server is worked on. Every call gets it, the /oauth endpoints too. Nothing was done or saved. Try again after Retry-After seconds.
503 Service Unavailable
10100 Not found The address or the item does not exist.
404 Not Found
10302 The member is locked A locked member may read but not change anything.
403 Forbidden
10300 A booking rule stopped the action The website's booking rules do not allow it. "errors" has the rule's text for the member.
409 Conflict
10301 Booking is switched off The organization has switched booking off; everything but the booking endpoints works.
403 Forbidden
10303 The change puts the booking last in a queue PATCH /bookings/{id}: the new time collides with another booking, and the booking would be placed last in its queue. "errors" names the bookings ahead. Send the change again with "queue_confirmed": true to go ahead.
409 Conflict
10304 The object has no thumbnail "has_thumbnail" in the object says beforehand whether there is one.
404 Not Found
10306 The member has no photo GET /me/photo: "has_photo" in GET /me says beforehand whether there is one.
404 Not Found
10307 The organization has no logo GET /organization/logo: "has_logo" in GET /organization says beforehand whether there is one.
404 Not Found
10308 You may not end this booking POST /bookings/{id}/cut on a booking that is going on but is not the member's. "permissions.can_cut" in the booking says beforehand whether the member may.
403 Forbidden
10309 You may not change this booking PATCH /bookings/{id} on a booking the member may not change. "permissions.can_edit" in the booking says beforehand whether the member may.
403 Forbidden
10310 The organization has no Swish integration POST /payments/swish: "active" in GET /payments/swish/options says beforehand whether it has.
409 Conflict
10311 No annual fee to pay POST /payments/swish with "annual_fee": the fee is paid already, the membership has none, or it is outside the organization's limits. "annual_fee" in GET /payments/swish/options says beforehand.
409 Conflict
10312 The payment is no longer waiting Cancel or QR code of a payment that is paid, declined or cancelled already, or a QR code of a payment sent to a phone number.
409 Conflict
10313 Swish refused, or did not answer "errors" has Swish's own code in "swish_code" (null when Swish did not answer) and its message. Try again later, or show the message to the member.
502 Bad Gateway
10314 No bank QR code GET /payments/bank/qr: the organization has no giro number, or is not Swedish. "qr" in GET /payments/bank/options says beforehand.
409 Conflict
10315 The organization has no Nets Easy integration POST /payments/nets: "active" in GET /payments/nets/options says beforehand whether it has.
409 Conflict
10316 The organization has no terms for Nets Easy payments POST /payments/nets: Nets' payment page must link to the organization's terms and conditions, and the organization has given myWebLog none. "terms_url" in GET /payments/nets/options says beforehand.
409 Conflict
10317 Nets refused, or did not answer "errors" names the field Nets objects to and gives the website's text for it, or Nets' own message. Show the message to the member, or try again later.
502 Bad Gateway
10318 The payment is not paid POST /payments/nets/{uuid}/complete: Nets has charged nothing, the member did not pay on Nets' page.
409 Conflict
10319 The payment could not be booked POST /payments/nets/{uuid}/complete: the member was charged, but the payment could not be booked on the account. myWebLog's support has been notified and books it by hand; tell the member so.
500 Internal Server Error
10320 A booking of this type cannot be changed through the API PATCH /bookings/{id} on a service booking or an instructor duty. They are changed on the website.
409 Conflict
10321 The message must be acknowledged POST /messages/{id}/read on a message that waits for the member's acknowledgement, without "acknowledgement_key". Fetch the message with GET /messages/{id}, show it, and send its key when the member confirms.
409 Conflict
10322 Not this message's acknowledgement key POST /messages/{id}/read: the "acknowledgement_key" sent is not the one GET /messages/{id} gives for this message and member. In "errors", with the field; the reply's own code is 10006.
400 Bad Request
10323 Only a read message can be archived POST /messages/{id}/archive on an unread message. Mark it as read first with POST /messages/{id}/read (a message that must be acknowledged: with its "acknowledgement_key").
409 Conflict
10324 The endpoint is a member's, the account a personal logbook A personal logbook account called an endpoint of the organization's side (objects, bookings, /flightlogs, transactions, payments, messages). It has the /logbook endpoints, /client, /texts, /me and /airports. See "Two kinds of account".
403 Forbidden
10325 The endpoint is a personal logbook account's, the account a member A member called a /logbook endpoint. The member's flights in the organization's log are /flightlogs.
403 Forbidden
10326 The personal logbook account has expired A /logbook endpoint called by a personal logbook account whose paid period has passed ("logbook.is_expired" in GET /me). The account is renewed on the website.
403 Forbidden
10327 The member may not change this date PUT or DELETE /me/expiry-dates/{type_id} on a type without "members_can_change": the organization's administrators set the date, or members send in a copy of the document with the date instead (POST /me/expiry-dates/{type_id}/submission). New in 5.17.
403 Forbidden
10328 Members do not send in a copy of this type POST /me/expiry-dates/{type_id}/submission on a type without "members_can_upload". New in 5.17.
403 Forbidden
10329 The file is too big POST /me/expiry-dates/{type_id}/submission: the copy is larger than 5 MB. In "errors", on the field "file"; the reply's own code is 10006. New in 5.17.
400 Bad Request
10330 Not a JPG, PNG or PDF file POST /me/expiry-dates/{type_id}/submission: the file's name does not end in .jpg, .jpeg, .png or .pdf, or its content is not of that kind. In "errors", on the field "file"; the reply's own code is 10006. New in 5.17.
400 Bad Request
10331 The organization has switched the remark function off GET /remark-options or POST /remarks in an organization that does not use remarks. Do not offer remarks in the app. New in 5.18.
403 Forbidden
10332 The member may not do this to a remark POST /remarks/{id}/acknowledge, /comment or /close: only a mechanic or an administrator acknowledges and closes; the member who wrote the remark may also comment. New in 5.19.
403 Forbidden
10333 The remark's state does not allow this now POST /remarks/{id}/acknowledge on a remark that is already acknowledged or closed; /comment or /close before the acknowledgement, or after the close. GET /remarks/{id} gives the status. New in 5.19.
409 Conflict
10334 Only the booker and the student can follow a booking on the lock screen PUT /bookings/{id}/live-activity on someone else's booking. "is_own" in GET /bookings/{id} says beforehand. New in 5.20.
403 Forbidden
10335 Register the iPhone first PUT /bookings/{id}/live-activity before this login has registered the iPhone with PUT /me/devices/{token}. New in 5.20.
409 Conflict
10336 The booking has ended PUT /bookings/{id}/live-activity after the booking's end ("is_passed" in GET /bookings/{id}). New in 5.20.
409 Conflict
10337 You may not change the images of this remark POST /remarks/{id}/images and DELETE /remarks/{id}/images/{image_id}: the remark's own images are changed by the member who wrote the remark, a mechanic or an administrator; the image of a comment or of the closing by the one who wrote it, a mechanic or an administrator. New in version 5.37.
403 Forbidden
10338 The remark is closed POST or DELETE /remarks/{id}/images on a closed remark: the remark's own images and the images of comments. The closing text's image can still be added and removed for 24 hours after the closing. New in version 5.37.
409 Conflict
10339 No room for one more image POST /remarks/{id}/images: the remark has two images already, or the comment or closing has one. Remove one first. New in version 5.37.
409 Conflict
10340 The remark has this picture already POST /remarks/{id}/images with a picture that is already one of the remark's own images. New in version 5.37.
409 Conflict
10341 The file is not an image that can be saved POST /remarks/{id}/images: in "errors" on the field file. A JPEG, PNG, GIF or WebP of at most 20 MB and 25 million pixels. New in version 5.37.
400 Bad Request
10342 The organization is temporarily closed Every endpoint, for every member of the organization, its administrators too: an administrator has closed the organization temporarily on the website. Closing ends every app login of the organization's members (the access token gives 401 and the refresh token invalid_grant, as after a password change), and new logins are refused on the login page with the organization's message. A call that still gets through gives 403 with this code; "detail" is the organization's message to its members: show it and end the login. The organization's profile is left out of GET /me/profiles and cannot be switched to. New in version 5.46.
403 Forbidden
10305 A member's access token is needed The token is the client's own (grant_type=client_credentials), which only GET /client and GET /texts take. Log a member in.
403 Forbidden
11000 The flight can not be logged as it was sent POST /flightlogs and /flightlogs/preview: the engine found problems. "errors" has each one with its field and its own code, 11001-11049, the same codes as the Main API v5: 11001 object, 11002 flight type, 11003 pilot, 11004 pilot locked, 11006 no debit model, 11007 no member to charge; 11010-11013 the date (invalid, the logbook lock date, the transaction lock date, in the future); 11020-11025 the route (airports, too few flights for the via airports, number of flights, distance, more flights than the maximum); 11030-11036 the times (a time required, the order, the ratio, above the maximum, a reading lower than the last, tach out not the last tach in, invalid time); 11040-11049 the other fields (instructor, scout, daily check, fuel/oil, towing, the remark's text and category, a blocking remark not allowed, the booking choice, PFLY); 11052 the amount above the organization's limit.
400 Bad Request
11005 The flight log is not open for you The organization has switched the flight log off, or locked it for members who may not log for others.
403 Forbidden
11050 The flight is logged already A flight with the same object, date and times exists. For a member who is an administrator this is a warning in "meta.warnings", and the flight is logged. With other problems in the same body it is one of the errors of a 400 (code 11000).
409 Conflict
11051 The price has changed The price is not the confirmed_total that was sent. "charge" has the new price; show it and let the member confirm again. With other problems in the same body it is one of the errors of a 400 (code 11000).
409 Conflict
11060 The flight could not be saved A fault while saving; nothing is saved. Try again, and contact support if it happens again. 11064-11066 are warnings after a successful save: the remark could not be made, the booking could not be ended, the mail could not be sent.
500 Internal Server Error
11090 This time does not exist on that date POST /flightlogs and /flightlogs/preview with clock_times "local" (new in 5.42): a clock time in the hour that is skipped when summer time starts, at its airport. One of the errors of a 400 with code 11000. The personal logbook's code for the same is 11121.
400 Bad Request
11100 The flight can not be saved as it was sent POST, PATCH /logbook/flightlogs and the preview (since 5.39): the personal logbook's engine found problems. "errors" has each one with its field (the body's, "times.pic"), its own code and a message: 11101 the date is missing, 11102 in the future, 11103 the aircraft is not in the list, 11104 inactive, 11105 a flight and a session at once, 11106 the simulator is not in the list, 11107 the type of flight is not in the list, 11108 inactive, 11109 an airport code over 5 characters (or more than 5 via), 11111 a time of day not HH:MM, 11112 a flight time that is not a number of hours or over 24, 11113 a function time over the total, 11114 a count not 0-999, 11115 a text too long, 11116 an unknown tag or a bad tag name, 11117 simulator airports on a flight, 11118 a roster duty that does not exist, 11119 no PIC, 11120 more than 3 students, 11121 (since 5.40, with clock_times "local") a clock time that does not exist on that date, the hour skipped when summer time starts. 11110 (an unknown airport, saved as typed) is a warning in "warnings", as are those of a successful save in "meta.warnings". GET /logbook/flightlog-form gives the texts in the pilot's language.
400 Bad Request
11150 The flight is logged already A flight with the same date, aircraft (or simulator), departure time and arrival time exists in the personal logbook: the question the Log flight page asks. Send the flight again with allow_duplicate true to log it anyway. Only when that is the only problem; with other problems it is one of the errors of a 400 (code 11100). In the preview it is a warning.
409 Conflict
11151 The flight is locked PATCH /logbook/flightlogs/{id}: the flight is signed, or waiting for a signature by email (is_locked), and takes a change of its tags only.
409 Conflict
11160 The flight could not be saved A fault while saving the personal logbook's row; nothing is saved. Try again, and contact support if it happens again. 11161 is a warning after a successful save: the tags, the students, the simulator airports or the roster link could not be saved.
500 Internal Server Error
11170 The flight has changed since it was read PATCH /logbook/flightlogs/{id} with expected_updated_at: the flight's updated_at is not the one sent (it was changed on the website, say). "flight" has the flight as it is now; let the pilot choose, then send the change again with the new updated_at.
409 Conflict
11171 The logbook's clock times are UTC POST, PATCH /logbook/flightlogs and the preview with clock_times "local" (since 5.40) for a pilot whose logbook is on UTC: the app has an old setting. Read GET /me again (logbook.clock_times) and send the flight in UTC.
409 Conflict
11181 The flight waits for a signature by email POST /logbook/flightlogs/{id}/signatures: an open request by email locks the flight for everyone else; cancel the request first (DELETE .../signature-request).
409 Conflict
11182 The drawing is not a PNG POST /logbook/flightlogs/{id}/signatures: drawing_png is not a PNG image as base64, or is larger than 300 KB or 2000 by 1000 pixels.
400 Bad Request
11183 The flight could not be signed POST /logbook/flightlogs/{id}/signatures: the server lacks the signing key, or the signature's row could not be saved. Nothing is saved; contact support.
500 Internal Server Error
11184 Too many signature requests POST /logbook/flightlogs/{id}/signature-request and .../renew: the pilot has sent 20 requests in the last 24 hours, the website's limit.
409 Conflict
11185 A signature request is open already POST /logbook/flightlogs/{id}/signature-request: the flight has a waiting request; send it again with .../renew, or cancel it.
409 Conflict
11186 The flight has three images POST /logbook/flightlogs/{id}/images: remove one first.
409 Conflict
11187 The flight has this picture already POST /logbook/flightlogs/{id}/images: the same picture is on the flight (the same picture on another flight is fine).
409 Conflict
11188 The file is no image POST /logbook/flightlogs/{id}/images: the part file is not a JPEG, PNG, GIF or WebP, is larger than 20 MB or 25 million pixels, or did not arrive whole.
400 Bad Request
11190 The registration is in the list already POST /logbook/aircraft: the pilot has an individual with that registration or qualification number.
409 Conflict
11191 Unknown aircraft type POST /logbook/aircraft: type.designator is no ICAO type myWebLog knows; GET /logbook/aircraft-types searches them.
400 Bad Request
11192 An aircraft needs a type POST /logbook/aircraft: an aircraft (not a simulator) was sent without type.designator.
400 Bad Request
11193 The short code is used by another person POST /logbook/people (new in 5.44): short_code is the short code of another of the pilot's people; a short code belongs to one person.
409 Conflict
11194 Unknown country code POST /logbook/people (new in 5.44): nationality_code is no ISO 3166-1 two-letter country code myWebLog knows.
400 Bad Request